Migrating BPEL process instances in bulk to a new version of a process template

IBM BPM, V8.0.1, All platforms > Installing, deploying, and undeploying applications in the runtime environment > Installing process application snapshots > Migrating instances > Migrating BPEL processes
Migrating BPEL process instances in bulk to a new version of a process template

Use an administrative script to migrate running instances after deploying a new version of a process template, because new process instances are based on the new version, but existing instances based on the old template version continue running until they reach an end state.

The following conditions must be met:

Run the script in the connected mode, that is, the application server must be running.
If Business Process Choreographer is configured on a cluster, then at least one cluster member must be running.
If WebSphere administrative security is enabled, and your user ID does not have administrator authority, include the wsadmin -user and -password options to specify a user ID that has administrator authority.
If you are not working with the default profile, use the wsadmin -profileName profile option to specify the profile.

Use the migrateProcessInstances.py script to migrate instances of a specific process template version to the latest version, or a specified version. Instances that are in an end state (finished, terminated, compensated, or failed) are not migrated. Only instances of the specified template with the same version as the specified "valid from" value are migrated. If you prefer to write a script to migrate instances, an MBean interface is available.

Procedure
Change to the Business Process Choreographer subdirectory where the administrative script is located.
cd  INSTALL_ROOT/ProcessChoreographer/admin
cd INSTALL_ROOT/ProcessChoreographer/admin
cd INSTALL_ROOT\ProcessChoreographer\admin
Migrate the instances of process templates that are no longer valid.
 INSTALL_ROOT/bin/wsadmin.sh  -f migrateProcessInstances.py
       [([-node  node_name] -server  server_name ) | ( -cluster  cluster_name )]
       ( -templateName  template_name) 
       (-sourceValidFromUTC  timestamp ) 
       [(-targetValidFromUTC  timestamp )]
       [(-slice  slice_size
 INSTALL_ROOT/bin/wsadmin.sh  -f migrateProcessInstances.py
       [([-node  node_name] -server  server_name ) | ( -cluster  cluster_name )]
       ( -templateName  template_name) 
       (-sourceValidFromUTC  timestamp ) 
       [(-targetValidFromUTC  timestamp )]
       [(-slice  slice_size
 INSTALL_ROOT\bin\wsadmin -f migrateProcessInstances.py
       [([-node  node_name] -server  server_name ) | ( -cluster  cluster_name )]
       ( -templateName  template_name) 
       (-sourceValidFromUTC  timestamp ) 
       [(-targetValidFromUTC  timestamp )]
       [(-slice  slice_size
Where:

-node nodeName

The name of the node where Business Process Choreographer is configured. This is optional when specifying the server name. The default is the local node.

-server serverName

The name of the server where Business Process Choreographer is configured. This is required if a cluster is not specified.

-cluster clusterName

The name of the cluster where Business Process Choreographer is configured. This is required if Business Process Choreographer is configured on a cluster.

-templateName template_name

The name of the process template to be migrated.