This topic applies only to the IBM Business Process Manager Express configuration.

Performing premigration tasks

Before you begin the migration procedure, verify that your target migration environment is supported and that your source migration environment is ready to be migrated.
Figure 1. Sample environment before migration begins. The source environment is running and transferring data to and from its databases.
The details of the diagram are provided in the figure caption.

Procedure

  1. Verify that your target migration environment - including hardware, operating systems, and database prerequisites - is a supported operating environment for IBM® Business Process Manager V8.5.6. See IBM Business Process Manager Express system requirements.
    Important: The minimum DB2 level has been increased to 9.7.0.5. If required, move to the new database version and make sure that IBM Business Process Manager is working correctly before you proceed with the migration.
  2. Prepare your applications for migration.
    1. Identify all applications that might be affected. Potentially affected applications are all applications that are installed on the source environment and all back-end applications that communicate with the source environment. Identify the contact person for each of these applications.
    2. Some authentication aliases and users have been removed from IBM Business Process Manager V8.5.6. Before you migrate, check Default users and authentication aliases removed from IBM Business Process Manager V8.5.
      • If your applications are using aliases that have been removed, you must re-create them manually in the target environment after migration.
      • If your applications are using users that have been removed, you must assign the required security roles to them again after migration.
    3. If your applications rely on specific WebSphere® Application Server configuration, the applications might fail to start, or fail to work correctly in V8.5.6 unless you re-create any required resources. Check for dependencies in the following areas:
      • JMS configurations
      • Schedulers
      • Environment variables
      • Shared library configurations
      • Work Manager
      You might need to re-create these resources manually in the target environment after migration.