Migrate Long-Running Process Instances Between Any Two IBM Business Automation Workflow Environments
Don't let data migration worries derail your upgrade or infrastructure plans.
BAW is a key component of IBM Cloud Pak for Business Automation, but there is no out of the box solution for moving process instance data between BAW environments. The Apex Instance Migration Tool makes it easy to move data, for example from on-premises to SaaS; or from Oracle to MSSqlServer. The solution uses published APIs to read and create instances to ensure there is no risk of data corruption. Individual process applications can be migrated to support whatever phasing your project requires.
Apex BAW Instance Migration can be customized to suit your process applications, giving you the option of running it yourself, or having the Apex team take care of the migration process. Migrate to SaaS or a new database vendor without losing your in-flight data.
BAW Instance Migration also supports moving in-flight data from traditional to container infrastructure.
How did a large bank get off their legacy mainframe infrastructure for BAW? The bank setup a new environment with a MS SQLServer database instead of the DB2 on z/OS of the legacy environment. Apex helped them use the instance migration tool to migrate 35,000 in-flight instances to the new environment.
