1) Install Intralink 3.3 (2002471 - ilink-033_2002471) fileserver on pdmlink server
(lfpplm.clearpath.lan).

2) Upgrade Intralink fileserver to later datecode (M022 - ilink-033_M022_WIN).

====================================================================

Agron

A simple backup method to restore the blank PDMLink 8.0  (Pro/INTRALINK 8.0)
after having populated it with data from a first migration attempt
(export/import of an oracle dumpfile). 
  
When performing a data migration, you will repeat the migration procedure
a number of times to rehearse the process.  Each migration attempt results
in data being migrated into the target system.  In order to perform
subsequent migrations, this migrated data will need to be removed from the
target system, otherwise duplicate object conflicts would occur for every
object in the system.

The simplest way to reset the system to a pre-migration state, is to import
an Oracle Dumpfile "snapshot".  Creating the snapshot should be done
immediately before a migration attempt begins, at the point where the
Windchill 8.0 system, including the Data Migrator, has been completely
installed, configured, and validated.

This "snapshot" of the Oracle database will act as the waypoint that can be
returned to easily, by importing the dumpfile into Oracle.  The following
procedures should be followed for creation of the shapshot before migration
(Steps 1-3), dropping the PDMLink schema user, recreating the user and
Importing the dumpfile to reset the system (Step 4), and recompiling
packages that might have been invalidated (Step 5). 
  
1. After a successful  Pro/INTRALINK 8.0 and Pro/INTRALINK Data Migrator
installation login to Pro/INTRALINK 8.0 as local admin (wcadmin/wcadmin),
configure and validate the external vaults, create the IBA organizer 
(TestOrganizer) and the libraries and products. 
  
2. Run "ildataloader Mapping" and select option 1 (test connection).
If this test is successful exit out of the dataloader and follow the step
below to create a pdmlink dumpfile. 
  
3. Create a pdmlink dumpfile: 
  
DOS>exp system/manager@wind file=D:\ptc\pdmlink\empty_ilink8_M10_dump.dmp owner=guest log=exp.log 
  
where: "wind" is the Pro/INTRALINK 8.0 service name
and "guest" is the owner of Pro/INTRALINK 8.0 schema. [wcuser]

These names can be different depending on what you chose during the
installation procedure. 
  
4. After the dumpfile is created, proceed with the migration steps and run all
the migration loaders including the filetransfer. When the time comes that you
want to run the migration a second time around, all you need to do is drop the
PDMLink schema user, run the script <pdmlink loadpoint>\db\sql\create_user.sql 
and  import the dumpfile you created in the previous step as illustrated in
the example below: 
  
DOS> sqlplus system/manager@wind
SQL> drop user guest cascade;
SQL>@<pdmlink loadpoint>\db\sql\create_user.sql
Enter username: guest
Enter temporary tablespace: TEMP
Enter users tablespace: USERS
SQL>exit 
  
DOS>imp system/manager@wind file=D:\ptc\pdmlink\empty_ilink8_M10_dump.dmp full=y ignore=y log=import_log.lst 
  
5. Follow instructions of TPI 128926 to identify and re-compile any packages
that might have been invalidated. 

Migration Roadmap 

Migration involves definition, rehearsal, and smooth execution of a solid 
process especially when moving between unknown or dissimilar systems and 
must be executed with minimum impact on users using legacy systems. 

To ensure smooth migration it is important to structure the process as 
follows: 

. Plan 
. Conflict Identification (Metadata Only Migration) 
. Conflict Resolution and Data Cleansing 
. Rehearsal Migration 
. Production Migration 

Plan 

Planning is similar to the planning activity that occurs in other project types. 
The following tasks are an important part of the planning process: 

. Create a project plan for migration 
. Determine the data mappings between the source and target systems and 
document them in a migration specification document. 
. Create a validation plan. A validation plan is a concise documentation of 
test cases and tests, test objects, and expected results. The plan is applied 
during the validation steps that are included in the Rehearsal Migration 
and the Production Migration phases. 


Conflict Identification (Metadata Only Migration) 

The Conflict Identification phase involves an initial migration of metadata 
(data contained in Oracle, but not the file vault data) from the source 
Pro/INTRALINK system to the target system, for the purpose of identifying 
conflicts. The Pro/INTRALINK Data Migrator 8.0 requires that conflicts be 
resolved as they are encountered, so it may be necessary to apply temporary 
artificial conflict resolutions during the Conflict Identification phase, in 
order to complete the metadata-only migration. An artificial resolution might 
consist of generically adding DUPLICATE_ to the names of any objects that 
have duplicate object conflicts. These objects will have real conflict 
resolutions applied during a later phase. 
To perform metadata migration: 

. Run the migration tool on the metadata only (do not run the File Transfer 
data loader in this phase), using data mappings from the migration 
specification document. 
. Conflict logs generated during this process enable you to identify 
conflicts. 


Conflict Resolution and Data Cleansing 

A data migration conflict occurs whenever the process of correctly migrating 
data from the source system to the target system is unclear. In many cases, 
conflicts can be resolved by deciding how best to migrate the data and which 
data must be altered to support that decision. The following steps are an 
important part of this activity: 

. Review conflict logs to determine conflict resolutions and document them 
in the migration specification document. 
. Update the validation plan and project plan, if necessary, based on the 
results of the Metadata Migration and Conflict Resolution. 
. Apply required conflict resolutions and data cleansing to the data in the 
source Pro/INTRALINK system. 


Rehearsal Migration 

The process validation activity is a full rehearsal of the migration process. 
This activity always starts off with some readiness activities, such as the 
setup, installation, configuration of hardware and software, and continues 
with a series of process steps and validations. The following are an important 
part of this activity: 

. Execute a full migration using Data Mappings and Conflict Resolutions 
from the migration specification document. 
. Validate the migration process using the validation plan. 
. Review the rehearsal validation results. Update the migration 
specification, validation plan, and project plan, as necessary, based on 
these results. 
. Perform additional conflict resolution and data cleansing, if necessary, 
prior to Production Migration. 


Production Migration 

This activity is the live performance of the rehearsed migration process. The 
production migration is usually done on the production data or production 
systems. After you begin executing the process steps and the validation steps, 
the goal is to do them for the last time, and to go live with the software. The 
following are the important steps of this activity: 

. Execute Production Migration using Data Mappings and Conflict 
Resolutions from the migration specification documents. 
. Validate the migration process using the validation plan. 
. Review the Production Migration validation results. 
. Make a decision to Go Live with the software. 

====================================================================

Path=
D:\oracle\ora92\jre\1.4.2\bin\client;
D:\oracle\ora92\jre\1.4.2\bin;
D:\OraHome_1\jre\1.4.2\bin\client;
D:\OraHome_1\jre\1.4.2\bin;
D:\OraHome_2\bin;
C:\Program Files\Oracle\jre\1.3.1\bin;
C:\Program Files\Oracle\jre\1.1.8\bin;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
D:\oracle\ora92;
D:\oracle\ora92\bin;
d:\wc_fs\fileserver3.3\bin

====================================================================

1. Copy all files in <mig_home>/ilscript/ to <ProI_home>\tools\bin 

2. 
PROI_SYS_PWD = dschangeme 
ORA_SYS_PWD = manager 

3. <ProI_home>\tools\bin\tclsh healing_before_migration.tcl 

4. To put Pro/INTRALINK in restricted mode, run the following script
from a command window:

<ProI_home>\tools\bin\tclsh pdm_sql_wrapper.tcl restrict_proi_usage.sql

[View these scripts & see if both should be run at same time].

5. Lock Pro/INTRALINK Schema and Unlock the Migration Schema 

<ProI_home>\tools\bin\tclsh disable_il_for_migration.tcl <migration schema password>

<migration schema password> is the ilmigpassword  property value in the
<MIG_HOME>\codebase\com\ptc\migration\migration.properties file
(the default value is migchangeme).

6. <MIG_HOME>\codebase\com\ptc\migration\migration.properties

migration.admin.iba.versionedOrganizer=TestOrganizer
migration.admin.iba.nonversionedOrganizer=TestOrganizer
migration.admin.iba.dependencyOrganizer=TestOrganizer

7. Configure the docrules.properties File 

<MIG_HOME>\loadFiles\ilwcmigration\docrules.properties

EPMDOC_NUMBER=NAME_WITH_EXTENSION 
This rule specifies what value to be assigned as the "CAD Document Number"
NAME_WITH_EXTENSION || AUTO_NUMBERING

WTDOC_NUMBER=AUTO_NUMBERING
This rule specifies the value to be assigned as the "WT Document Number".

NAME_WITH_EXTENSION || AUTO_NUMBERING

The docrules.properties file determines the document numbering scheme for 
both CAD Documents and WT Documents. By default the system will use the
CAD document name with its extension.

8. Configure the partrules.properties File 
<MIG_HOME>\loadFiles\ilwcmigration\partrules.properties

PART_NUMBER=AUTO_NUMBERING

NAME_WITH_EXTENSION || NAME_WITH_NO_EXTENSION 
|| AUTO_NUMBERING || Non-Versioned Attribute Name

PART_VIEW= ???

rules.properties ???

9. Configure external file vault

 1. From the PDMLink browser, select the Site > Utilities tab. 

 2. Select External Storage Administrator. 

 3. Select Vaulting Rules. 

 4. Select the Default Domain that corresponds to the target Product or 
  Library for documents. For example, if the Library is 
  MigrationLibrary, then the domain might be Site, Organization 
  PTC, Library MigrationLibrary /Default. Then pick Update. 
  The Domain Vaulting Rules window will then appear. 
  
 5. From the Domain Vaulting Rules select the Create button. This will 
  launch the Vaulting Rule interface. 

 6. Select the class WTObject, the state All and the intended File Vault and 
  pick OK. 

 7. Pick Close in the Domain Vaulting Rules window. 
 
 8. Pick Close in the Administrative Domains window. 

 9. Make sure that all revaulting schedulers are disabled. Revaulting 
  activities must be suspended while migration is in progress. 
  Note: Consult the target system documentation for more information on 
  setting up external file vaults.

====================================================================
Data Mapping
====================================================================

1.

Ensure that Apache, Tomcat, and Method Server are running on the 
PDMLink system. 
.  Open a command shell window 
.  Change directory to <MIG_HOME>\bin 

Enter:

ildataloader Mapping

Welcome to pre-configuration for Windchill Dataloader. 
--------------------------------------- 
Main Menu 
--------------------------------------- 
1: Test Connections 
*2: Download Admin Data 
3: Reconcile Admin Data 
4: Load Admin Data 
5: Map Admin Data 
6: Create Document Migration Rules 
7: Pre-configuration for Part Creation 
8: Cleanup Mapping 
9: Exit pre-configuration. 
--------------------------------------- 
>>> Choose an option: 

===================

2.

Select option 2, Download Admin Data. The system loads the following menu: 

This step will extract administrative data from  Pro/INTRALINK and output
the file as a text file. You  can perform the following operations. 
--------------------------------------- 
1: Download USER data from Pro/INTRALINK 
2: Download FOLDER and RELEASE SCHEME/RELEASE LEVEL data from Pro/INTRALINK 
3: Download USER DEFINED ATTRIBUTES data from Pro/INTRALINK 
4: Download FILEVAULT data from Pro/INTRALINK 
5: Download PI Type Definition data from Pro/INTRALINK 
*6: Download ALL data 
7: Go back to the main menu 
8: Exit pre-configuration. 
--------------------------------------- 
>>> Choose an option: 

===================

3.

Select option 6 to download all administrative data from  Pro/INTRALINK.

The system creates the:

usermap.properties. 
epm_folder_rsrl_map.properties
filevaults.properties
ibamap.properties files

pitdmapping.properties ??? ( Option 5 below).

in the:

<MIG_HOME>\loadFiles\ilwcmigration

directory.

Option 1: Download USER data from Pro/INTRALINK: 

this option extracts all user account data from Pro/INTRALINK 
and stores the data in the 

*usermap.properties 

file. 

Option 2: Download FOLDER and RELEASE SCHEME/RELEASE LEVEL data from
Pro/INTRALINK

this option extracts all folder and release scheme/level 
information from Pro/INTRALINK and stores it in the 

*epm_folder_rsrl_mapping.properties

file. 

Option 3: Download USER DEFINED ATTRIBUTES data from Pro/INTRALINK

this option extracts all user-defined attributes from Pro/INTRALINK
and stores it in the 

*ibamap.properties

file. 

Option 4: Download FILEVAULT data from  Pro/INTRALINK

this option extracts the Pro/INTRALINK file vault definition information
and stores it in the 

*filevaults.properties

file. 

Option 5: Download PI Type Definition data from Pro/INTRALINK

this option extracts all the product item type definitions from Pro/INTRALINK
and stores this data in the 

*pitdmapping.properties

file. A default mapping is provided for the standard product item type
definitions. If you have additional customized  PI types or you want to change
the defaults then you must edit the  pitdmapping.properties file as described
in the following section. 

4.

Once you have downloaded all of the administrative data,
select option 7 to return to the main menu. 

====================================================================
Editing the properties Files:
====================================================================

Document Data Loader

extracts PI and PIV objects from 
Pro/INTRALINK and creates corresponding CAD documents and WT 
Documents in your target system based on preferences established by the 
pitdmapping.properties file. 

Links Data Loader

Extracts the CAD document relationships from the 
source system and creates "uses" and "reference" links on the target 
system. 

Attributes Data Loader

Extracts UDA values for all Pro/INTRALINK 
objects (PIs, PIVs and dependencies). Loads attributes as IBA values on 
corresponding CAD Documents, CAD Document Masters, documents, 
document master, Doc/WTDOC Relationship. 

Family Table Data Loader

relates documents that represent family table 
generics and instances to build family table structure in the target system. 

As-Stored Data Loader

Extracts As-Stored transaction IDs from 
Pro/INTRALINK and loads this data to the target system. This data allows 
the target system to recreate any As-Stored baselines that you might have. 

Baselines Data Loader

Extracts named baselines from Pro/INTRALINK 
and loads them to the target system as managed baselines. On the target 
system the appropriate objects are added to the baseline. 

File Transfer Data Loader

Copies the file contents for each 
Pro/INTRALINK object and loads the data in to the new file vault location. 
Alternatively, if you have selected the Move file transfer option during 

Rename History Data Loader

Optional loader that extracts the rename 
history for Pro/INTRALINK objects and adds the rename history to the 
migrated objects in the target system. 

RTP Forms Data Loader

Optional loader that extracts completed 

"request to promote" (RTP) forms and check in forms from Pro/INTRALINK 
and loads this data to the target system. Any RTP form that is migrated will 
appear as a promotion notice in the target system. 

installation, then this data loader moves the Pro/INTRALINK file content 
from a local directory on the PDMLink machine in to the PDMLink file vault. 

Note: The following data loaders are to be used only if you are migrating to a 
PDMLink target system 

WTPart Data Loader

Creates WTParts on the target system for all 
migrated CAD Documents. This loader can be configured to allow you to 
specify which CAD documents to make WTParts for. 

Build Process Data Loader

Builds relationships between WTParts based 
on CAD document associations. 

Baselines Data Loader

Adds any WTParts created by the WTPart data 
loader to the managed baselines created during the document data migration 
process.

===========================


Running the Data loaders 

The following section describes all the steps required to run the data loaders 
and begin moving your data from Pro/INTRALINK to the target system. 

Mandatory Loader Execution 

XStep 1: Resume DOCUMENT Migration Command 

By default your migration is in a stopped state. In order to start or resume 
migrating with the data loaders, you must enter the following command: 

Ildataloader DocResume 

To learn more about the Stop/Resume functionality of the Pro/INTRALINK 
Data Loader refer to page 7-8. 

XStep 2: Running the Document Data Loader 

This data loader extracts PI and PIV objects from Pro/INTRALINK and 
creates corresponding CAD documents and WT Documents in your target 
system, based on the mapping information provided by the 
pitdmapping.properties file. 

To run the document data loader, type the following: 

ildataloader Document <numberOfThreads> 

Where <numberOfThreads> indicates the number of threads to be used 
for loading data into PDMLINK. Valid values are 1,2,3,4, or 5. 
Recommended value is 2. For example: 

ildataloader Document 2 

When run, this data loader performs two steps: 

. Migrates objects, which are: 
. Not published through the Pro/INTRALINK Gateway. 
. Not migrated or replicated from another instance of 
Pro/INTRALINK. 
. Fills in any missing versions or iterations in your data caused by 
previously published Pro/INTRALINK Gateway objects or a replicated 
Pro/INTRALINK database that has been previously migrated. The 
missing versions or iterations are migrated from the master 
Pro/INTRALINK database. 

Note: The number of threads to assign to a data loader is something that 
changes from system to system; a larger number does not guarantee greater 
performance. For large migration jobs it may be necessary to determine an 
optimal value through testing within a particular system environment. 

Step 3. Running the Links Data Loader 

This command will migrate Pro/INTRALINK dependencies to PDMLink 
epmmemberlink or reference link. It can be run in parallel to step 3. No 
dependencies from/to the Pro/INTRALINK objects that are migrated as 
WTDocuments are migrated. 

To run the links data loader, type the following: 

ildataloader Link <numberOfThreads> 


Step 4: Running the Family Table Data Loader 

This command will migrate family tables from Pro/INTRALINK to the target 
system. 

To run the family tables data loader, type the following: 

ildataloader FT <numberOfThreads> 

When run, this data loader performs two steps: 

. Migrates the family table without filling in its Pro/ENGINEER Wildfire 
properties 
. Populates the Pro/ENGINEER Wildfire properties for the family table. 

Step 5: Running the Attributes Data Loader 

This command migrates Pro/INTRALINK user defined attribute values to 
PDMLink IBAs. 

To run the attributes data loader, type the following. 

ildataloader UDA <numberOfThreads> 


Step 6: Running the As-Stored Data Loader 

This command migrates the Pro/INTRALINK as-stored configuration to 
PDMLink. 

To run the as-stored data loader, type the following: 

ildataloader AsStored <numberOfThreads> 


Step 7: Running the Baselines Data Loader 

This command migrates your Pro/INTRALINK baselines to PDMLink 
managed baseline. 
To run the baselines data loader, type the following: 

ildataloader Baseline <numberOfThreads> 

Note: Baselines that contain data that is not on the "main" branch or 
baselines that contain data types that are not defined in the 
pitdmapping.properties file will not be migrated. 

Step 8: Running the Rename History Data Loader 

This command will migrate the Pro/INTRALINK rename history for each 
migrated object into the rename history for the corresponding CAD document 
in PDMLink. 

To run the rename history data loader, type the following: 

ildataloader RenameHistory <numberOfThreads> 

Step 9: Running the RTP Forms Data Loader 

This command extracts completed "request to promote" (RTP) forms and 
check in forms from Pro/INTRALINK and loads this data to the target 
system. Any RTP form that is migrated will appear as a promotion notice in 
the target system. 

To run the forms data loader, type the following: 

Ildataloader RTPForm <numberOfThreads> 


Step 10: Running the File Transfer Data Loader 

This command transfers file content from Pro/INTRALINK to the target 
system. 

To run the file transfer data loader, type the following: 

ildataloader FileTransfer <numberOfThread> 

Note: 

. If you have selected Copy as your file transfer option (specified during 
installation and can be found in migration.properties as 
"FileTransferOption"), make sure that the NFS servers are running on 
both the Pro/INTRALINK and the PDMLink servers. Additionally, all 
Pro/INTRALINK fileservers must be running (even if some of the file 
servers do not contain valid files for migration). 
. If you have selected Move as your file transfer option, make sure that the 
contents of the Pro/INTRALINK file vault is accessible on the machine 
that contains the PDMLink file vault and that the correct location is 
specified in the filevaults.properties file. 

Optional Loader Execution 

The following loaders create WTParts and product structure for the migrated 
data in the database on the target system. These loaders are only applicable 
when migrating to a PDMLink target system. 


Step 11: Resume Part Migration Command 

By default your migration is in a stopped state. In order to start or resume 
migrating with the WTPart data loaders, you must enter the following 
command: 

Ildataloader PartResume 

To learn more about the Stop/Resume functionality of the Pro/INTRALINK 
Data Loader refer to page 7-8. 

Step 12: Running the WTPart Data Loader 

Creates WTParts on the target system for all migrated CAD Documents. This 
loader can be configured to allow you to specify which CAD documents to 
make WTParts for. 

To run the WTPart data loader, type the following: 

ildataloader WTPart <numberOfThreads> 

When run, this data loader performs two steps: 

. Creates WTParts for objects, which are: 
. Not published through the Pro/INTRALINK Gateway. 
. Not migrated or replicated from another instance of 
Pro/INTRALINK. 
. Creates WTParts for any missing versions or iterations in your data 
caused by previously published Pro/INTRALINK Gateway objects or a 
replicated Pro/INTRALINK database that has been previously migrated. 


Step 13: Running the Build Process Data Loader 

This command builds product structure for those WTParts created in step 12 
based on the build rules established between the WTParts and CAD 
documents created during the migration. 

To run the build process data loader, type the following: 

ildataloader BuildProcess <numberOfThreads> 

When run, this data loader performs three steps: 

. Creates product structure for WTParts that are associated with CAD 
documents, which were: 
. Not published through the Pro/INTRALINK Gateway. 
. Not migrated or replicated from another instance of 
Pro/INTRALINK. not published through the Pro/INTRALINK 
Gateway. 
. Creates product structure for any missing versions or iterations in your 
data caused by previously published Pro/INTRALINK Gateway objects or 
a replicated Pro/INTRALINK database that has been previously 
migrated. 
. Creates WTPartUsageLinks between WTParts, at least one of which is 
associated with a WTDocument. 

Step 14: Running the Baselines Data Loader 

At this point in the migration you can rerun the baseline loader so that any 
corresponding WTParts created in step 12 will be added to the managed 
baselines created in step 7 (this loader is optional). 

ildataloader Baseline <numberOfThreads> 

 