Planning a migration

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Before you migrate any production environment, make sure that you have migrated your staging or test environment and have tested your applications in the new environment.
Migrate to a new version for one or more of the following reasons:
  • You want to improve performance.
  • You need fixes that are in the new version.
  • You want to use new features that are provided in the new version.
  • Your existing product version is going out of service.
Use migration testing for one or more of the following reasons:
  • You must estimate in advance the amount of downtime that will be needed for migration. An estimate of downtime cannot be created without testing.
  • You want to make sure that the new version improves performance.
  • You want to make sure that the fixes you require are in the new version and work as expected.
  • You want to make sure that your existing applications work correctly in the new version.
To test the migration:
  • Prepare test cases that are based on the existing functions and requirements.
  • Prepare the test environment. The following factors must be the same in both the test environment and the production environment:
    • Operating system type and version
    • Database type and version
    • IBM® Business Automation Workflow version and WebSphere® Application Server version
    • IBM Business Automation Workflow topology
    If you are not testing for the amount of downtime, you might not care about disk space, memory, or processor.
  • Test the migration. Make sure that all the migration steps run successfully.
  • Use your test cases to make sure that all applications work correctly after migration.
  • Make sure that you note all changes to your applications, and keep track of everything that you moved to the new environment, to help when you migrate the production environment.
This topic applies only to the IBM Business Automation Workflow Advanced configuration.Restriction: IBM Business Automation Workflow 21.x and 22.x do not support migration of the Unit Test Environment (UTE) for IBM Integration Designer.

When you move the database to a new server, the data sources are generally updated using the BPMConfig command. However, BPMConfig does not update the transaction log data sources. The data sources for transaction logs must be updated in the admin console or using wsadmin commands. The target database requires XA and same user privilege. See Configuring XA transactions for your database type, for example: Configuring XA transactions for Oracle in a network environment on Windows.

To back up the database, stop the IBM Business Automation Workflow server system. Otherwise, if the system is running, you might experience data loss when backing up the database. If you receive this error message:
J2CXAResource W J2CA0061W: Error creating XA Connection and Resource com.ibm.ws.exception.WsException: DSRA8100E: Unable to get a XAConnection from the DataSource jdbc/DefaultEJBTimerDataSource
then recovering from this error will cause data loss when the transaction log tables are truncated. A similar error occurs when the transaction log data sources are not updated.

For tuning guidance on migration, see Chapter 6: Migration considerations in IBM Business Process Manager V8.5 Performance Tuning and Best Practices External link opens a new window or tab.