IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Plan the runtime migration

Advanced: What gets migrated and what does not get migrated

When you use the IBM BPM runtime migration procedures to migrate to IBM BPM Advanced V8.0.1, the following items are migrated: user applications, profile configuration data, adapters, data sources and providers, and long-running processes.


User Applications

Your user applications (any applications not provided with the IBM BPM product) are binary-compatible for the supported migration scenarios. When you use the runtime version-to-version migration method, all user applications are automatically migrated to the new target version. You should not have to modify any part of the application to have it run on the newer version of the product. Except for sample applications, applications that are provided as part of the source product are migrated to the latest version of those applications. These are handled as follows:

If you use the application migration process rather than the runtime migration process, you create a parallel target production environment that is configured differently from the source production environment, and then selectively redeploy your applications from the source production environment to the target production environment.

The artifact migration process is similar to the application migration process in created a parallel target production environment that is configured differently from the source production environment. However, instead of the applications being manually redeployed from the source environment directly into the target production environment, they are imported into the development environment and migrated by the development tools.


Business Process Rules Manager

The Business Process Rules Manager (also referred to as "business rules manager") at any given version can manage applications that contain business rules at the same version or a later version (in most cases), but does not support managing applications that contain business rules created and deployed on prior versions. Because the Business Process Rules Manager is cell-scoped, meaning that it manages all business rules deployed in a cell, and cells can be mixed version, containing for example clusters on version 7.5 and clusters on V8.0.1, it is typically wise to defer the migration of the Business Process Rules Manager until all the Business Rules applications have been migrated. To support this concept, the Business Process Rules Manager application is not automatically migrated until the last non-clustered managed node or the last cluster in a cell is migrated.

If the last migrated node is not an IBM BPM profile, business rules resources and the Business Process Rules Manager migration script are not available. Therefore, Business Process Rules Manager is not automatically migrated during the migration process. In this scenario, you must manually run the Business Process Rules Manager migration script in an IBM BPM custom node after the entire system is migrated. See installBRManager command-line utility.

As an example, assume a scenario where a cell contains four clusters named cluster1, cluster2, cluster3, and cluster4, each running version 7.5; the Business Process Rules Manager is deployed to cluster1; and you want to migrate the cell sequentially beginning with cluster1 followed by clusters 2, 3, and 4. If cluster1 is migrated first to V8.0.1, the Business Process Rules Manager deployed to cluster1 remains at version 7.5, enabling it to continue to manage the Business Process Rule applications deployed to clusters 2, 3, and 4. The Business Process Rules Manager continues to run at the 7.5 version while clusters 2 and 3 are migrated, but it is then automatically migrated to V8.0.1 when cluster4 is migrated.

There are also scenarios where it makes sense to migrate the Business Process Rules Manager manually at an earlier step, instead of waiting for the very last node in the cell to be migrated. Take, for example, a slightly modified version of the prior scenario where the Business Process Rules Manager is deployed to cluster1 and only cluster2 contains Business Rule applications. Similar to the first scenario, when cluster1 is migrated to V8.0.1, the Business Process Rules Manager remains at the version 7.5, enabling it to manage the Business Rules deployed to cluster2. When cluster2 is migrated to V8.0.1, it then makes sense to migrate the Business Process Rules Manager, because clusters 3 and 4 do not contain any Business Rules, and the only rules in the cell are now at V8.0.1. To support this scenario, the Business Rules migration process provides the installBRManager command-line utility, which can be manually invoked at various phases of the migration process. See installBRManager command-line utility.

In a stand-alone migration scenario, the Business Process Rules Manager is always migrated automatically when the stand-alone profile is migrated.


Adapters

For version 6.2.0 WebSphere Adapters, install an interim fix with the name "Mandatory adapter fix for running 6.1 and 6.2 Adapters on WPS v7.0." Apply this interim fix on the source environment if you do not plan to update the WebSphere Adapter to a 7.x or 8.x level and want to use the application with a 6.2.0 version of the WebSphere Adapter. For information on how to apply this interim fix, see the appropriate step in Runtime premigration checklist.

The runtime migration procedure for IBM BPM V8.0.1 allows you to upgrade the adapter as part of the runtime migration that uses previous versions of WebSphere Adapters.

All WebSphere Adapters for version 6.0.2 and Websphere Adapter for SAP versions 6.0.2, 6.1.0, 6.1.2, and 6.2.0 are not supported on IBM BPM V8.0.1. This set of adapters must be updated to V8.0.1 before any applications that are using them can be deployed on IBM BPM V8.0.1. See Runtime premigration checklist for instructions on how to handle WebSphere Adapters during runtime migration.


Profile configuration data

The version-to-version migration tools (wizard or commands) automatically apply the configuration settings from the previous profile to the new profile created during the migration process.


JDBC providers and data sources

Profile migration automatically migrates the JDBC provider and data source definitions for each existing data source and provider.


Long-running processes

Long-running business process instances and human task instances are handled during version-to-version migration as the databases storing the instances are taken over. During migration, the database schema is upgraded and the data is converted to the new schema. After migration, those instances continue to run in the migrated environment.

Because the previously installed predefined human task applications might still have instances running, they are not uninstalled during migration. This means that after migration, both the new and the previous versions of the predefined human task applications are installed on your system. The version numbering indicates when the application was last updated. For information on when you can safely uninstall the previous versions of the applications, see Postmigration tasks for Business Process Choreographer.


What does not get migrated?

Custom files or artifacts are not automatically migrated. Most of these artifacts are user-created, and are not recognized by IBM BPM. Because they are not recognized, they are not migrated.

Plan the runtime migration