Migrating a large number of inflight process instances using the Process Admin Console

When you use the Process Admin Console to migrate a large number of inflight process instances, the web browser might crash or hang because of memory issues. The server returns very large blocks of instance data to the client browser. However, a configurable property migrate-instances-count has been introduced to let you to specify the number of instances that are migrated during a single migration using the Process Admin Console.

About this task

Although you can use the BPMMigrateInstances command to migrate a large number of process instances, the migrate-instances-count lets you limit the number of instances to migrate in a single migration using the Process Admin Console. The default value is 1000.

If you want to change the value for the setting, you can override the value by adding or updating the setting in your 100Custom.xml files. For example, to add the setting to a 100Custom.xml file, you would add the following elements under the <properties> element and modify the value as needed:

<server>
   <instance-migration merge="mergeChildren">
      <migrate-instances-count merge="replace">1000
      </migrate-instances-count>
   </instance-migration>
</server>

When this setting is enabled in the 100Custom.xml file, it applies to both the Process Admin Console and the BPMMigrateInstances command. After each migration, you should check Process Inspector to determine whether there are any remaining instances that are still pending for migration and then perform another migration for the remaining instances.

For information about the individual 100Custom.xml files that need to be updated and their locations, see the topic Location of configuration files.

To consistently and reliably change the value of the setting in all of the 100Custom.xml files in your IBM® BPM deployment environment, it is recommended that you use the updateBPMConfig command as described in the following procedure:

Procedure

Stop the servers for Process Server and Process Center.
Start the scripting client in disconnected mode as described in the topic updateBPMConfig command.

Run the following commands to simultaneously update all affected servers:

wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server' ] )
wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server/instance-migration' ] )
wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server/instance-migration/migrate-instances-count', '-xNodeValue', 'instances_count' ] )
wsadmin> AdminConfig.save()

Replace the instances_count variable with the number of process instances that you want to have migrated in a single migration.

Restart the servers.

Results

The recommended way of updating the 100Custom.xml files is by running the updateBPMConfig command. However, if the updates are unsuccessful, you can manually update the files by following the steps in the topic Setting configuration properties using 100Custom.xml.