Using the Admin Migration Wizard

Once you are ready to migrate your final changes to the production server, you can start the migration wizard. You can also run the wizard to view the existing state of synchronization and the order of objects between the production and staging servers. You can order the admin objects based on the order of either the staging server or the production server and modify the selected order before you migrate the objects. Only an Integrity Lifecycle Manager server administrator can perform the final operation to migrate changes. Type administrators are only permitted to view migration details using the wizard.

You launch the migration wizard from the Integrity Lifecycle Manager administration client by right-clicking the Workflows and Documents node and selecting Launch Admin Migration Wizard from the shortcut menu. The Launch Admin Migration Wizard menu item appears only when the server is configured as a staging server and for users who are assigned as Integrity Lifecycle Manager server administrators or type administrators.

Only the Integrity Lifecycle Manager server administrator can actually perform a migration. Type administrators may access the migration wizard only to view the information but cannot complete the migration operation. Type administrators can view all admin provided objects but can only edit the ones that they have permissions for.

Changes made by the migration wizard are shown as being carried out by the Integrity Lifecycle Manager server administrator user who ran the migration operation. All changes are viewable in the history for the object and in the audit log.

To view the audit log, the Integrity Lifecycle Manager administrator must grant you ViewAuditLog or AdminServer permission.

If the staging server or the production server is disconnected, or if the whole system is put into a state where the migration cannot be completed, then the operation is rolled back to put the production server (or staging server) into a usable state. You can also cancel a migration that is in progress. The operation is then rolled back to put the production server into a usable state.

Migrating admin provided objects from the staging server to the production server involves updating the configuration for the entire object being modified. When you perform the migration, all overrides are transferred to production. Therefore, you should only start a migration when all changes are finalized on the staging server. Since this may affect the work of multiple type administrators, you may want to consult with all type administrator before starting a migration. Once the migration is complete, a migration report displays.

• The Integrity Lifecycle Manager server administrator who performs the migration must also be an Integrity Lifecycle Manager server administrator on the target production server (that is, he or she must have the Admin ACL permission under mks:im).

• Maintaining all locks while the migration is running is recommended. If the lock on the production server is broken during a migration, an error message displays and the migration stops.

• To prevent deadlock situations from occurring during an admin migration, you cannot delete admin objects on a staging server if they have been migrated to a production server. Admin objects that have not been migrated to a production server may be deleted.

• Multiple users cannot edit admin objects at the same time. If you attempt to make and save a change at the same time as another user, a message displays indicating that concurrent changes were made. Unlike in configuration management, there is no attempt to merge your changes by the system. The only option is to exit the dialog box and re-enter.

• To migrate a shared field or state that has an override, without migrating the overrides of the new types that refer to it, see “Migrating a Shared Field or State Override”.

• To properly migrate custom views in ViewSets, the server.hostname property specified in each custom view must reflect the server host name specified in the mksis.hostname property of the corresponding Integrity Lifecycle Manager server. For example, if a server specifies mksis.hostname=abcFinancial.com, custom views connecting to that server must specify server.hostname=abcFinancial.com.

• If you convert a dynamic computed field to a static computed field on the production server, you must recalculate the computed field.

• When promoting an item presentation template (IPT) change from a staging server to a production server, the Integrity Lifecycle Manager client GUI may not display the IPT change, even after restarting the client. This issue may also occur when updating an IPT in the database from the CLI. This occurs when the IPT cache on theIntegrity Lifecycle Manager server does not update correctly.

After using this command, PTC recommends restarting the Integrity Lifecycle Manager client GUI to ensure updated IPTs display correctly.