You can customize certain Business Automation Workflow
configurations using 100Custom.xml files. After you have created a
100Custom.xml file with the required changes, you need to deploy it to your
deployment environment.
Procedure
-
Determine the server_type configuration scope to which you want to deploy
changes. The XML file should only contain changes to one of the three server types: process-server,
process-center, and performance-data-warehouse. This information is used to determine the path for
your 100Custom.xml file. For 3-cluster environments, the application cluster is
used for changes to the process-server and process-center server types. The support cluster is used
for changes to the performance-data-warehouse server type.
-
Use the updateBPMConfig command to automatically deploy changes to the
100Custom.xml files. Alternatively, you can manually place the
100Custom.xml files on the standalone server or the deployment manager.
If you want to place your 100Custom.xml files in a standalone server
environment, you should place them in the following location:
standalone_profile_root\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\config\
If you want to place your 100Custom.xml files on the deployment manager, you
should place them in the following locations (in the config directory of the
deployment manager profile):
- For each cluster
member:
dmgr_profile_root\config\cells\cell_name\nodes\node_name\servers\cluster_member_name\server_type\config\
- For the appropriate
cluster:
dmgr_profile_root\config\cells\cell_name\clusters\cluster_name\server_type\config\
Note:
The cluster files are used during the creation of new cluster members and for certain administrative
commands that are running in local mode.
Note: Ensure that you are editing the 100Custom.xml configuration files in the
deployment manager profile. If you edit these configuration files in a managed node profile, the
changes will be lost in the next node synchronization. Also, if you are replacing an existing file
and need a backup, ensure that you modify the file extension as all files with a
.xml file extension will be loaded. For example, use the
.bak file extension instead of .xml.
-
Perform a full synchronization with the nodes or restart the node agents. After you have
confirmed that all of the changes are synchronized with the nodes, restart the deployment
environment to enable the changes to take effect.
-
Review the TeamWorksConfiguration.running.xml file to confirm that the
changes have been applied properly.