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 types
Runtime migration supports the migration of stand-alone environments and ND environments.
Stand-alone migration
The following types of stand-alone migration variants are supported by the runtime migration procedures and tools:
- Side-by-side migration: where the source and target of the migration are on the same system
- Remote migration: where the source and target of the migration are on different systems
-
Operating system upgrade migration: where the operating system on the source system is being upgraded during the migration procedure to a new version that is supported by IBM BPM V8.0.1.
The following sections describe each of these types of stand-alone environment migration variants in more detail.
- Stand-alone side-by-side migration
- The stand-alone side-by-side migration process is the simplest runtime migration scenario, where the target product is installed on the same system as the source product, and the runtime migration procedures and tools are used to migrate the stand-alone profile containing the configuration, applications and the product databases to the target environment.
- Stand-alone remote migration
- The stand-alone remote migration process enables IBM BPM V8.0.1 to be installed on a different system from the source of the migration in order to support migration of the configuration and applications from one system to another. The stand-alone remote migration process can be used to support a variety of scenarios including:
- Migrating to a remote system that has the same type of hardware, operating system, and operating system version as the source of the migration
- Migrating to a remote system that has a different type of hardware (for example, 64-bit), a different operating system, or a different operating system version
The process requires the migration commands on the target system to be copied to the source system, where they are used to copy the source profiles. The snapshot directory is copied to the target system and used as the source for the profile migration.
- Stand-alone operating system upgrade migration
- The stand-alone operating system upgrade migration process enables the operating system on the system that contains the source of the migration to be upgraded during the migration process. This is typically
necessary if the operating system version containing the source product version is no longer supported by IBM BPM V8.0.1.
This process requires that you copy each of the source profiles on the prior version of the operating system, back up the copied source profiles to a remote location, reinstall the operating system to the new version, install the target product, restore the copied source profiles back to the migration system with the updated operating system, and then use the snapshot directory as the source for the profile migration.
Network deployment migration
Network deployment environment migrations are more involved than stand-alone environment migrations because of the need to migrate the dmgr, clusters, nodes, and differently scoped product databases, in the appropriate order. The side-by-side migration, remote migration, and operating system upgrade migration also are supported for ND environments. All ND migrations require IBM BPM V8.0.1 to be installed side-by-side with the source product of the migration or a different system. If the source of the migration is augmented by additional BPM products, they should be installed in the same installation directory as IBM BPM V8.0.1.
Two different types of nodes are referred to in the ND migration procedures, clustered nodes and non-clustered managed nodes. Clustered nodes contain at least one server that is a member of a cluster. Non-clustered managed nodes do not contain any servers that are cluster members.