Modifying individual configuration properties

Use the appropriate 100Custom.xml files in your topology to modify the configuration properties of the workflow server or Business Automation Studio.

Increasing the maximum number of cached objects during refactoring
Your attempt to copy or clone a large project might fail with an error.
Disabling user registry group synchronization during server startup
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 at a convenient time to perform the group synchronization manually.
Retrieving all user registry groups during server startup
Logging into the server can take longer than expected or even fail when some of the user registry groups cannot be retrieved during server startup. This problem can occur when some groups are marked as inactive during server startup and are not retrieved along with the other groups. However, you can use the configurable property mark-group-inactive-as-needed-in-start-up to prevent groups from being marked inactive.
Resolving user mismatch between the user information cache and the database
When the user is mismatched between the user information cache and the database, the user information cache holds references to users that are not in the database. If the user information in the cache is used for further database operations, a database transaction that follows the mismatch might fail with a constraint violation exception. To prevent this mismatch, you can add the user-info-cache-block-period configuration setting to the 100Custom.xml files. Using this setting, you can specify a period of time during which the cache entry is considered invalid and is not used (if it has not been confirmed by at least one successful read from the database).
Controlling administrator access to task instance data
By default, administrators are permitted to obtain and view task instance data regardless of whether they own the associated tasks. However, you can control administrator access to task instance data by adding the authorization-enabled-for-admins-to-get-set-task-data configuration setting to the 100Custom.xml files.
Restricting Inspector actions for online workflow servers
You can limit Inspector actions for specific workflow servers or environment types.
Specifying an absolute URL for the TWManagedFile JavaScript API
By default, a relative URL is used for the .url property of the TWManagedFile JavaScript API. However, if necessary, you can use an absolute URL instead by adding a configuration setting in the 100Custom.xml file.
Web services
Some behaviors of web services can be modified by setting configuration properties.
Controlling warning limits for variable sizes of process and service flows
There are some settings in configuration files that define warning limits for the variable sizes of process and service flows. If a warning limit is reached or exceeded for any of the settings, a warning message is logged in the SystemOut.log file. You can, however, override the default warning limits for the settings by adding the settings to the 100Custom.xml file.
Detecting infinite loops in services and process instances
There are two loop detection properties that you can use to detect and handle infinite loops in services and process instances.
Disabling updates for user names with trailing blanks
IBM® Business Automation Workflow considers user names that contain trailing blanks and their corresponding entries without the trailing blanks in the Lightweight Directory Access Protocol (LDAP) registry identical. By default Business Automation Workflow updates the information for user names with trailing blanks in its database with their LDAP counterparts during synchronization. This is also the recommended behavior. However, for compatibility reasons you can disable updates for user names with trailing blanks.
Restrictions on large file uploads and SVG browser display for ECM documents
To prevent any potential security issues, additional restrictions on large file uploads and SVG browser display apply to ECM documents.
Disabling group membership update at login time for web applications
When a user logs in to Business Automation Workflow web applications such as Process Portal, group membership is recalculated and can be cached for that user on the database, in order to keep accurate permission checks based on group memberships. This process might significantly affect performance because it can take up to several seconds, depending on how many user groups are registered in the system. You can use the synchronize-user-registry-groups-on-login configuration property to disable this mechanism. In this case, it is recommended to call the group synchronization REST APIat a convenient time to perform the group synchronization manually.
Enabling adding user registry groups of a user at login time for web applications
When a user logs in to Business Automation Workflow web applications such as Process Portal, group membership is recalculated and can be cached for that user on the database, in order to keep accurate permission checks based on group memberships.
Optimizing the login time for web applications
To help improve performance, you can reduce the time that a user spends logging in to web applications, including Process Portal. For this purpose, you set the user-group-membership-sync-cache-expiration configuration property to a number of minutes under which that user's membership to user groups is not recalculated.
Specifying that members of a group member cache are retrieved from the database
Use the group-member-cache-source setting in the appropriate 100Custom.xml file in your topology to specify that members of a group are retrieved from the IBM Business Automation Workflow database only, and not from a user registry, for example LDAP. This setting significantly increases the speed at which group members are loaded into the cache and reduces the number of cache reloads.
Optimizing the group member cache heap size
To tune the group member caching, use the group-member-cache-memory-optimized and group-member-cache-max-size settings in the appropriate 100Custom.xml file.
Limiting the number of REST calls to the server
In the 100Custom.xml files for the workflow server and Business Automation Studio, you can add or modify configuration settings that are used to limit the number of REST calls to the server within a time interval and prevent a denial of service attack.

Parent topic: The 100Custom.xml file and configuration