Migrating specific BPEL process instances to a different process version

A process template represents a version of a process. Running BPEL process instances can be migrated to a different process template version. You might want to do this, for example, when a newer version of the process becomes available, or because the current version has errors in it and you want to roll back to a previous process version. Use Business Process Choreographer Explorer to migrate selected process instances.

Before you begin

To migrate process instances, you must be a process administrator or system administrator.

About this task

When a new version of a BPEL process is deployed, you can base new process instances on this process version if you start them in Business Process Choreographer Explorer from the corresponding template. However, existing process instances which are based on a previous version of the process continue to run with this version until they reach an end state. You can migrate these existing process instances to a different process version; you do not need to migrate all of the instances to the same version.

You can also use the migrateProcessInstances.py script to migrate process instances in bulk. For more information, see the related information section.

In Business Process Choreographer Explorer, perform the following steps to migrate process instances.

Procedure

Navigate to a page that shows a list of process instances. For example, click All Versions, select one or more process templates, then click Instances.
Select the relevant process instance entries and click Migrate.
In the Process Instance Migration page, select the process template version to migrate the process instances to.
Optional: Test whether the process instances can be migrated to the process template version by clicking Test.
Click Migrate to migrate the process instances to the specified process template version.

Results

The process instances that qualify for migration to the selected process template version are migrated. For all other instances, an error message is displayed for each failed migration.