This chapter explains how to migrate instances of one application as the instances of another application by using the Business Process Portal interface and the migration utility.
In a dynamic organization, processes continuously undergo change. The cost of ownership of processes can be significantly affected when changes are not promptly applied to running instances of processes. The "Instance Migration" feature of Business Process Portal can help reduce the cost of ownership of processes by allowing for bulk migration of instances of processes from one application to another.
For example, you have few instances of application "Application". Then you created another application with name "Application_version1". You can use the instance migration feature to migrate the existing instances of application "Application" as the instances of new application "Application_version1". After migrating an instance the source instance is suspended. The name of the migrated instance has the following nomenclature:
<source_instance_name>#IM#<target_instance_id>
Business Process Portal and the instancemigration utility, both generate appropriate entries in the pim.log file.
Note: The current version of Business Process Server does not support instance migration to a target application which is in a deprecated state.
When you migrate the instances in which worksteps that are mapped to worksteps of target application are in the different state, how it works:
Active state — For worksteps in active state, in Business Process Server as well as in BPM Process Store workstep tables an equivalent record gets created for the mapped workstep from target process template. If such a workstep is human activity workstep, then it is reactivated, so that, if performer of the mapped workstep has been changed in target Process Template, then new workitems are created for the latest performer(s).
Inactive state — If the workstep is not activated then no records are created in Business Process Server and BPM Webflow workstep tables.
Completed state — For worksteps in completed state, for Business Process Server as well as BPM Process Store workstep tables an equivalent record gets created for the mapped workstep from the target process template.
