Data Migration : Pre/ Post migration functions

Major part of Data Migration is handled via the DCA Engine and its corresponding loader. There are additional operations which user needs to perform in the target application.

Export Tables and Domain Definitions

Use this option to export the tables and enumerated domains information of the customized application to the target.

This information is used for defining the list types mapping information for the new/customized list type and for defining the provisional tables mapping information for the customized tables/fields into the target application.

Data is exported to these files:

  • custom.target.table.fields.xml
  • custom.target.used.domains.xml

Export Descriptive Names Information

Use this option to export the descriptive names of the field. This information is used in migrating the Mapping Rules (pdcad102) table.

Data is exported to this file:

  • custom.target.table.fields.descriptive.names.xml

(Pre-Load) Delete Standard Vaults/Areas (pdadm110-112)

For tables related to Vaults and Areas, master data is shipped along with the standard application. This intervenes (in terms of data duplication/case-sensitive issues/preferred vault indicator etc.) with the data been migrated from source application. To ensure consistency, it is required to delete the master data of these tables prior to loading the data (using DCA Tool) into the target application:

  • Vaults (pdadm110)
  • Areas (pdadm111)
  • Areas by Vault (pdadm112)

(Pre-Load) Delete Units Management (pdadm510-512)

For tables related to Units Management, master data is shipped along with the standard application. This intervenes (in terms of data duplication) with the Data been migrated from source application. To ensure consistency, it is required to delete the data of these tables prior to loading the data (using DCA Tool) into the target application:

  • Unit Groups (pdadm510)
  • Units (pdadm511)
  • Unit Conversion Class (pdadm512)

(Pre-Load) Delete Standard Category Data (pdadm500)

For tables related to Category Management, master data is shipped along with the standard application. This intervenes (in terms of data duplication) with the Data been migrated from source application. To ensure consistency, it is required to delete the data of this table prior to loading the data (using DCA Tool) into the target application:

  • Category Tree (pdadm500)

(Pre-Load) Delete All Users Preferences (pdadm002, pdcad001-011)

Preferences for “pdadm002, “pdcad001 to pdcad011” are shipped as part of master data. However, the data of these tables is also migrated from source application as well.

Use this to delete the existing data (if any) in these tables.

(Pre-Load) Delete Projects (pdadm300-001)

Projects (pdadm300) and Project configuration (pdadm301) data is shipped as part of master data. In certain cases, it can clash with the data migrated from source application.

Use this to delete the existing data (if any) from these tables.

(Post-Load) Update Permissions for Preferences (pdadm001)

The Data for “Preferences Metadata” table (pdadm001) is shipped as master data. The value of the “Permission” column needs to be updated to match the settings as per source application.

When user clicks on this button:

  • User is prompted to select this file (exported using “DCA Utility for PLM”) : preferences.premissions.xml
  • Permission flag for preferences is updated in the “Preferences Metadata” table (pdadm001).

(Post-Load) Update Preferred Masks Information (pdadm601)

Masks are shipped along with the master data, which are already marked as preferred. Use this option to set the preferred masks information matching to the source application.

When user clicks on this button:

  • User is prompted to select following file (exported using “DCA Utility for PLM”) : preferred.masks.xml
  • Preferred flag value for masks is updated in “Masks” table (pdadm601).

(Post-Load) Import Roles and Role Actions (pdadm400-401)

Data pertaining to Roles Management are not imported using DCA Tool, instead it is exported using the “DCA Utility for PLM” (PLM.DCA.Utility.exe). This is imported using this session.

This approach takes care of evaluating the labels for Roles and Role Actions correctly. Since there can be additional role actions in target application, using this approach ensures that new role actions of target are also available for the migrated roles as well.

It must be noted that these six standard Roles and Role Actions are shipped along with the master data:

  • Design Engineer
  • General Administrator
  • None
  • Observer
  • Project Administrator
  • Project Manager

It is required that during Data Migration, one must not delete above mentioned standard roles.

When user clicks on this button:

  • · User is prompted to select following file (exported using “DCA Utility for PLM”) : roles.xml

  • New roles are created by duplicating (based on the value of (ROLE.USER_TYPE) the standard roles.
  • Permissions values for role actions are updated based on the xml input from source application.

(Post-Load) Import Text Data

Text Data is not migrated using DCA Tool, instead it is exported using the “DCA Utility for PLM” as xml files. This is imported using this session.

The reason for this approach is that, Text Data are stored in tables of LN Tools and its ID (number) is assigned to the various text fields in “pd” tables.

Before performing this operation, user needs to place the exported files for text data into following directory in LN Application Server.

  • $BSE/tmp/MIGRATION/PLM_TEXT_DATA/

When user select this option:

  • System reads the contents from the temporary directory.
  • Text Data is set for the migrated records and records are saved.

(Post-Load) Import Thumbnail Images (pdpdm502)

Thumbnail Images are not migrated using DCA Tool, instead these are exported using the “DCA Utility for PLM” as image files (.png/.jpeg). This is imported using this session.

The reason for this approach is that Thumbnails Images are stored as files under LN Tools; a compact GUID is used as reference for this in the “File Images” (pdpdm502) table.

Before performing this operation, user needs to place the exported image files into this directory in LN Application Server.

  • $BSE/tmp/MIGRATION/PLM_FILE_IMAGES/

When user select this option:

  • System reads the contents from the temporary directory.
  • Thumbnail Images are copied from temp location to the File Images directory of LN Tools.
  • The value of field “Thumbnail” is updated in the “File Images” table (pdpdm502).

Note

The actions are to be performed by a PLM Admin/ Super User with all required authentication & authorizations. Other users may not have authentication to perform operations.