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

Runtime migration tools

Migrating stand-alone and ND environments requires that you manage the production environment (start and stop the dmgr, servers, and nodes), migrate configuration profiles, upgrade product databases, and migrate application data. The runtime migration procedures guide you through the process and the runtime migration tools are used to perform the required steps.

The following three sets of tools support the runtime migration procedures:

The following sections provide a summary of each of these groups of tools.


Profile migration tools

The profile migration tools are used to migrate the profiles that contribute to the cell, clusters, non-clustered managed nodes, or stand-alone servers being migrated.

The profile migration tools support a three-step process for each profile:

  1. Snapshot the configuration files from the source profile to be migrated.
  2. Create the target profile in the target installation using the snapshot configuration from the source profile.
  3. Create the target profile in the target installation by running the JCL jobs that are generated by the z/OS Profile Management Tool.
  4. Migrate the configuration snapshot to the target profile.
The three-step process required to migrate each profile is supported by the IBM BPM profile migration wizard that can be invoked via the BPMMigrate command-line utility or the following set of profile migration command-line tools:

The IBM BPM profile migration wizard is supported on the following platforms:

Other platforms must use the command-line tools instead of the IBM BPM profile migration wizard to perform the three-step profile migration process.

In addition to the three-step process for profile migration, the following command-line utilities play key roles in profile migration:

For a summary of the profile migration commands see the Runtime migration tools reference topic.


Database upgrade and migration tools

IBM BPM V8.0.1 uses the following product databases that are either automatically or manually upgraded or migrated during the migration of the environment:

The Common Event Infrastructure database and the Messaging Engine databases are both automatically migrated as needed by the profile migration process. The other databases are either automatically or manually upgraded or migrated according to the detailed steps found in the migration procedures. For manually updating the product databases, the commands and scripts for each of the supported database types must be invoked on the database system by a user with sufficient privileges or a system that has the database client utilities installed with a network connection to the database system. The runtime migration procedures describe how to copy the commands and scripts for your database type and the source release of the migration to the database system.

For a summary of the database migration commands see the Runtime migration tools reference topic.


WebSphere Application Server management tools

During the migration procedures, the dmgr, nodes, and servers must be stopped and started at various steps. In addition, there are several other WebSphere Application Server commands used throughout the migration procedures.

For a summary of the WebSphere Application Server management tools required by the migration procedures see the Runtime migration tools reference topic.

Plan the runtime migration


Related concepts:

Runtime migration


Related reference:
BPMSnapshotSourceProfile command-line utility
BPMMigrateProfile command-line utility


Related information:

BPMCreateTargetProfile command-line utility