Considerations when migrating runtime workflow processes from one Worpoint server into a new Workpoint server of the same version of Workpoint

Document ID : KB000077090
Last Modified Date : 05/10/2018
Show Technical Document Details
Introduction:
This article helps to answer questions around migrating runtime workflow data from one server to another server when both are running the same version of Workpoint. This is needed when two different versions of CA Identity Manager that use the same version of Workpoint, and the customer upgrades from one version of Workpoint, to move the runtime workflow data from one environment to the (upgraded) other environment.
Environment:
CA Identity Manager, CA Identity Governance, CA Identity Portal, CA SSO, CA Identity Suite
Instructions:

Review these considerations before migrating all existing active workflow processes and workflow configuration from one Worpoint server into a new Workpoint server.

Note: Both servers are running the same version of Workpoint.

*************

You have two options when you migrate Workpoint data that does not need updating:
1)    Use the Database Vendor utilities to copy the data from the old to the new server. 
2)    Use the Workoint Archive facility to export data from the old server and import the data into the new server. 

Option one is the simplest, especially when migrating a large number of Workpoint Jobs. Option two, the Archive facility, creates XML for each Process, Job, and Library objects. Option two is slower. Depending on the number of jobs to migrate, it would take multiple export/import procedures to migrate, resulting in more  riski. 

All the job states remain the same when you copy over the database.

Migration is unnecessary if you plan to complete the existing Workpoint workflows in the old system and start new Workpoint workflows in the new system. Because CA installation adds the OOTB Workpoint Process Definition models, you only need to validate the Workpoint Process Definitions to confirm if any of your custom updates are needed, and if yes, import them.

The Workpoint tables begin with "WP_". For the complete list, see the Workpoint_Database_Diagram.pdf This PDF is located here:
C:\Program Files (x86)\CA\Identity Manager\IAM Suite\Identity Manager\tools\Workpoint\docs\database 

The Archive facility is "Archive.htm", located in the following path: 
C:\Program Files (x86)\CA\Identity Manager\IAM Suite\Identity Manager\tools\Workpoint\docs\designer

If you are concerned with the Workpoint counter, there's no need for concern: 
When you copy all the WP tables, you automatically get the IDs too (WP_ID_GEN table controls the IDs). If Workpoint is running when you copy over the database, then it needs to be restarted after the transfer completes.

Another suggestion is to change the Workpoint Database ID: this is a 4-character value located in the wp_ini table. This starts the numbering for all new objects and is used when the current data is large and the customer may hit the threshold of incremental numbering on the current Database ID.
Workpoint should not be running when copying the data from one database to the second database.