IBM Business Process Manager Migration roadmap

Use the following flow diagram and high-level migration task descriptions to learn about the tasks involved in a version-to-version migration.

Figure 1. IBM Business Process Manager migration roadmap for version-to-version migration

 1  Identify the migration requirements

Identifying the migration requirements is the first step in planning your migration.

See the Migration method comparison topic for a list of the set of considerations involved in the migration process.

 2  Select a migration method

There are three migration methods to choose from when migrating:

• Runtime migration
• Manual migration
• Artifact migration

To review the migration methods and determine which migration method fits your requirements see the Migration methods topic.

 3  Identify resources and availability

When planning your migration, it is critical to identify the availability of all of the resources you need for the migration, including:

• Human resources: How many people and what skill level is needed? What is the timeframe for the human resource need?
• Hardware and software resources: What hardware or software do you need to acquire to ensure a successful migration?
  Restriction: WebSphere Process Server can migrate only to Business Process Manager Advanced edition; refer to IBM Business Process Manager Advanced system requirements.

 4  Test the migration procedure

Before performing the migration, thoroughly test the migration procedure:

• Test your applications in a new environment.
• Test your migration procedure in a staging environment.
• Practice your rollback plan on a test system.

When planning which test or tests will best suit your migration, keep in mind the necessary resources to make the test successful.

 5  Migrate

Use the migration procedures associated with the migration method you choose to migrate your environment.

 6  Verify migration

After performing the migration, use one of the following methods to verify success, depending on which migration method you used:

• If you used the runtime migration method, see Verifying migration.
• If you used the manual migration method, manually redeploying your applications from a production environment that is the source of the migration to a parallel target production environment, verify that your applications work as expected.
• If you used the artifact migration method, using IBM Integration Designer and IBM WebSphere Business Modeler to import and update applications and workspaces developed using earlier versions, verify that your applications work as expected.

 7  Roll back if necessary

If the migration was not successful, you might need to roll back your environment and perform the migration again. Use one of the following rollback methods, depending on which migration method you used:

• If you used the runtime migration method, see Rolling back your environment.
• If you used the manual migration method, you might need to uninstall and then reinstall the applications.
• If you used the artifact migration method, you might need to uninstall and then re-import and re-migrate the applications and source artifacts using Integration Designer or IBM WebSphere Business Modeler.