Disabling user registry group synchronization during server startup

Edit online

Group names from the configured user registry are replicated into the product database when the server starts. If the user registry contains many groups, the server startup can take longer than expected. However, you can use the configurable property synchronize-user-registry-groups-on-start-up to disable the user registry group synchronization during server startup. In this case, it is recommended to call the group synchronization REST API or the syncGroupMembershipForGroups tool at a convenient time to perform the group synchronization manually (see Synchronizing group membership by groups).

About this task

The synchronize-user-registry-groups-on-start-up setting is used to disable or to enable the group synchronization during server startup. If it is set to true (which is the default), user registry groups are replicated into the database during server startup. 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, add the following elements under the <properties> element and modify the value as needed:

<common>
  <security>
    <synchronize-user-registry-groups-on-start-up merge="replace">false</synchronize-user-registry-groups-on-start-up>
  </security>
</common>

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

Procedure

Traditional:
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 to use the updateBPMConfig command as described in the following 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', '/common' ] )
wsadmin> AdminTask.updateBPMConfig( [ '-create', '/common/security' ] )
wsadmin> AdminTask.updateBPMConfig( [ '-create', '/common/security/synchronize-user-registry-groups-on-start-up', '-xNodeValue', true_or_false ] )
wsadmin> AdminConfig.save()
```
4. Replace the true_or_false variable with either true or false.
5. Restart the servers.
Containers:
If you use containers, make changes to the 100Custom.xml file by following the procedure described at Customizing Business Automation Workflow properties.