IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment
Migrating from previous versions
You can migrate from a previous version of IBM BPM or WebSphere Process Server, or use the migration facilities provided by WebSphere Lombardi Edition.
Supported migration sources
The following product and version combinations are supported as sources for migration to IBM BPM V8.0.1.
- IBM BPM Advanced V7.5 or V7.5.1
- IBM BPM Standard V7.5 or V7.5.1
- WebSphere Process Server V7.0.0.x or V6.2.x
- WebSphere Lombardi Edition V7.x
- WebSphere Lombardi Edition V6.x
- IBM BPM for z/OS V7.5
- WebSphere Process Server for z/OS V7.0 (all releases)
- WebSphere Process Server for z/OS V6.2 (all releases)
- WebSphere Lombardi Edition V7.x
- WebSphere Lombardi Edition V6.x
For migrating from V8.0 to V8.0.1, see Upgrading from IBM BPM V8.0 to IBM BPM V8.0.1.
High-level steps
The general sequence of events for migrating from an earlier version of the product to V8.0.1 is similar to the following sequence:
- Check that you have the required hardware and software. Depending on your IBM BPM configuration, visit:
- Select a migration method. See Migration methods.
- Test the migration procedure. Before performing the migration:
- Test your applications in a new environment.
- Test your migration procedure in a staging environment.
- Practice your rollback plan on a test system.
- Migrate. Use the migration procedures associated with the migration method you choose to migrate your environment.
- Verify the 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 artifact migration method, using IBM Integration Designer to import and update applications and workspaces developed using earlier versions, verify that your applications work as expected.
- If you used the application migration method, 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 runtime migration method, see Verifying migration.
- 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 artifact migration method, you might need to uninstall and then re-import and re-migrate the applications and source artifacts using Integration Designer.
- If you used the application migration method, you might need to uninstall and then reinstall the applications.
- If you used the runtime migration method, see Rolling back your environment.
- Roadmap: Migrating from previous versions
Depending on the previous version of IBM BPM and its predecessor products you are migrating from, you have different methods of migration available to you. The roadmap identifies which migration methods are supported for each version of the product, as well as the high-level tasks that are required to complete that particular migration.- Migration methods
There are several migration methods to choose from when moving to a new version of IBM BPM.- Mixed-version environments
Version-to-version migration of ND-based production environments frequently results in a period of time when the ND environment is running applications on different versions of IBM BPM. This concept is referred to as mixed versions.- Migrating from Teamworks 6
To migrate from Teamworks 6, run the Upgrade Readiness Check tool to analyze existing process assets, plan your project, and then use the upgrade utilities provided with IBM BPM V8.0.1 to complete the migration.- Migrating from IBM BPM Standard V7.5.x, Teamworks 7, or WebSphere Lombardi Edition
To migrate from IBM BPM Standard V7.5.x, Teamworks 7, or WebSphere Lombardi Edition, use the migration utilities provided with IBM BPM V8.0.1.- Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime
IBM BPM provides facilities for migrating from previous runtime products or versions. In runtime migration, the configuration of the production topology, the product databases, and the product data in the databases are all migrated to V8.0.1 by a consistent set of procedures and tools.