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 is upgrading from one to the other, in need to move the runtime workflow data from one environment to the (upgraded) other.
CA Identity Manager, CA Identity Governance, CA Identity Portal, CA SSO, CA Identity Suite
Considerations when migrating all existing active workflow processes and workflow configuration from one Worpoint server into a new Workpoint server (both running the same version of Workpoint):
To migrate Workpoint data that does not need to be updated there are two options:
1) Use the Database Vendor utilities to copy the data from the old to the new
2) Use Workpoint Archive facility to export data from the old and import the data into the new.
Option one is the simplest especially when migrating a large number of Workpoint Jobs. Option two, the Archive facility which creates XML for each Process, Job and Library objects would be slower. Depending on the number of jobs to migrate, it would take multiple export/import procedures to migrate which is riskier.
All the job states will remain the same when you copy over the database.
If you plan to complete the existing Workpoint workflows in the old system and start new Workpoint workflows in the new system, no migration is necessary. CA's install adds the OOTB Workpoint Process Definition models, so you would 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_". You can also look at Workpoint_Database_Diagram.pdf, in the following path: C:\Program Files (x86)\CA\Identity Manager\IAM Suite\Identity Manager\tools\Workpoint\docs\database for the complete list.
The Archive facility is "Archive.htm" 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 then you will automatically get the IDs too (WP_ID_GEN table controls the IDs). If Workpoint is running when you copy over the database, then it will need to be restarted after the transfer is complete.
Another suggestion we have is to change the Workpoint Database ID, this is a 4-character value located in the wp_ini table. This will start 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. When copying the data from one database to the second database, Workpoint should not be running.