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 Where 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 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 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 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 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 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 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 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 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 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 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