This topic applies only to the IBM Business Process Manager Advanced configuration.

migrateProcessInstances.py administrative script

Use the migrateProcessInstances.py administrative script to migrate running instances.

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.

Prerequisites

The following conditions must be met:

Run the script in the connected mode, that is, do not use the wsadmin -conntype none option.
At least one cluster member must be running.
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.

Location

The migrateProcessInstances.py administrative script is in the Business Process Choreographer admin directory.

install_root\ProcessChoreographer\admin
install_root/ProcessChoreographer/admin

Syntax

-f migrateProcessInstances.py
        -cluster cluster_name
       ( -templateName template_name) 
       (-sourceValidFromUTC timestamp ) 
       [(-targetValidFromUTC timestamp )]
       [(-slice slice_size

Parameters

-f: This parameter specifies the script file to run.
-cluster clusterName: The name of the cluster where Business Process Choreographer is configured. In a multicluster setup, you must specify the application cluster because that is where Business Process Choreographer is configured.
-templateName template_name: The name of the process template to be migrated.
-sourceValidFromUTC timestamp: The timestamp specifies which version of the named template will have its instances migrated.
The timestamp string specifies the date from which the template is valid, in Coordinated Universal Time (UTC), and must have the following format: yyyy-mm-ddThh:mm:ss (year, month, day, T, hours, minutes, seconds). For example, 2009-01-31T13:40:50. In the administrative console this date is displayed in local time of the server, so make sure that you take the server time zone into account.
-targetValidFromUTC timestamp: This optionally specifies which version of the named process template the instances will be migrated to. If this parameter is not specified, the latest available version of the template will be used. The timestamp string has the same format as for the sourceValidFromUTC parameter.
-slice slice_size: This parameter is optional. The value slice_size specifies how many process instances are migrated in one transaction. The default value is 10.