Disabling team synchronization during process instance migration

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
When you migrate process instances into a new IBM® Business Automation Workflow snapshot on an Workflow Server environment, groups and members are automatically reinstated that were intentionally deleted from teams to prevent them from being able to launch a process. However, you can use the configurable property disable-team-sync to disable team synchronization during process instance migration and prevent deleted groups and members from being automatically added back to teams.

About this task

The disable-team-sync setting disables team synchronization during process instance migration. If false is specified (which is the default), team synchronization is not disabled during process instance migration and deleted groups and members will be automatically added back to teams. If true is specified, team synchronization is disabled during process instance migration and deleted groups and members will not be added back to teams.

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">
      <disable-team-sync merge="replace">false
      </disable-team-sync>
   </instance-migration>
</server>

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

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

Procedure

  1. Stop the servers for Workflow Server and Workflow Center.
  2. Start the scripting client in disconnected mode as described in the topic updateBPMConfig command.
  3. 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/disable-team-sync', '-xNodeValue', 'true_or_false' ] )
wsadmin> AdminConfig.save()

    Replace the true_or_false variable with either true or false.

  4. 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 Creating a 100Custom.xml configuration file.