Migrating from WebSphere Process Server V7.0.0.x or V6.2.0.x to IBM BPM V8.5 on Linux, UNIX, or z/OS

Migrate from WebSphere® Process Server V7.0.0.x or V6.2.0.x to IBM® Business Process Manager V8.5 on Linux, UNIX, or z/OS.

To migrate your business data and applications, complete the following tasks. Until you reach the "Shutting down applications" task, your source environment can still be running.

  1. 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.
  2. Installing IBM Business Process Manager V8.5
    Before you begin migration, use custom installation to install IBM Business Process Manager V8.5 on a different computer, or in a different directory on the same computer as your previous version. Before you begin to migrate your business data and applications, install IBM Business Process Manager V8.5 on each node in the target environment.
  3. Copying the migration utilities to the source computer
    If you installed IBM Business Process Manager V8.5 on a different computer from your source environment, package the remote migration utilities into an image and copy the image back to the source computer. You will use the migration utilities to take a snapshot of the previous version.
  4. Extracting data source information from the source environment
    Optionally, extract the data source information from your source environment so that you can make the same changes in the new version while you create the deployment environment. Using this information ensures that you can access the previous databases from your new deployment environment.
  5. Configuring IBM Business Process Manager V8.5
    After you install IBM Business Process Manager V8.5, use the BPMConfig command to create the profiles and network deployment environment. The BPMConfig command is required for migration. The deployment environment will use the same databases as the source environment.
  6. Configuring IBM Business Process Manager for z/OS V8.5
    After you install IBM Business Process Manager V8.5, create and augment the deployment manager and empty managed node profiles, and then create the network deployment environment. This deployment environment will use the same databases as the source environment.
  7. Checking for migration readiness
    Before you migrate from WebSphere Process Server, run a command to make sure that your source environment is in the correct state for migration. Then, disable the automatic starting of all applications and schedulers in the source environment to make sure that no new events or processes are entering the system.
  8. Shutting down applications
    After the migration readiness command succeeds, disable the automatic starting of all your applications and schedulers in the source environment.
  9. Taking a snapshot of the source
    Take a snapshot of your source environment to extract information such as configuration customizations, applications, LTPA keys, and service integration bus (SIB) messages. You will import this snapshot to the target environment in a later step. You need one snapshot for each deployment environment in your source cell. You do not need a separate snapshot per profile from your source cell.
  10. Copying the snapshot to the target computer
    If you installed IBM Business Process Manager V8.5 on a different computer from your source environment, copy the snapshot to the target computer. The snapshot was created when you ran the BPMExtractSourceInformation command to extract the customizations that you made in your source environment.
  11. Backing up databases
    Before you upgrade your existing databases, create backup copies. You can use backups to revert to the premigration state of the databases at any time, if necessary.
  12. Generating SQL scripts and configuring new database components
    You must generate the SQL scripts that are required to update the schemas for each of your existing databases. Based on the properties that you chose when you created your deployment environment, you might need to configure one or more new database components. You must drop the messaging engine tables if you plan to reuse your previous messaging engine database. For DB2 for z/OS, you must also configure new messaging engine tables manually.
  13. Upgrading existing databases
    After you install the new version of IBM Business Process Manager, upgrade your databases so that your data works with the new version.
  14. Starting the target environment
    Disable the automatic starting of all applications and schedulers in the target environment, start the deployment manager, start the managed node or nodes, and then start the servers.
  15. Importing the migration snapshot
    Import the migration snapshot from the source environment into the target environment.
  16. Moving your custom configuration to the target environment
    After you finish the automatic migration, you must manually move to the target environment any customizations that you made in the source environment.
  17. Restarting and verifying the migration
    After you migrate to IBM Business Process Manager, restart the deployment environment and verify that the migration was successful.
  18. Completing configuration for migrating to a different computer
    After you migrate to a different computer, you might need to change some configuration settings that were not updated automatically.
Parent topic: Migrating business data and applications from WebSphere Process Server V7.0.x or V6.2.x