Location of 100Custom configuration files

Edit online

The location of 100Custom XML configuration files and the system files that contain the default values is dependent on the server type that you are configuring. It is also dependent on whether your environment is a stand-alone environment or a clustered network deployment environment.

 Containers:  IBM® Business Automation Workflow on containers supports one 100Custom.xml file, which includes all the needed customization. It is mounted as /opt/ibm/wlp/usr/servers/defaultServer/config/199Custom.xml in the Workflow server pod. The current settings for a running server are in /opt/ibm/wlp/usr/servers/defaultServer/TeamWorksConfiguration.running.xml.

 Traditional: For 100Custom configuration files and system files, the following considerations apply:

  • At run time, only the settings from the cluster member files are read.
  • For ND environments, XML configuration files on the cluster level serve as templates for the XML configuration files that are created when new cluster members are added. Also, XML configuration files on the cluster level are used by certain administrative commands that run in local mode, such as the BPMUpdateSystemApp command.
  • For the Workflow Center deployment environment, the server_type value is either performance-data-warehouse, or process-center. For the Workflow Server deployment environment, the server_type value is either performance-data-warehouse, or process-server.
  • Both standalone and single-cluster environments can have two directories for each server.
  • For three-cluster environments, the process-center or process-server files are for the application cluster. The performance-data-warehouse files are for the support cluster.
Note: Do not update the 100Custom.xml files used for cluster or cluster members, directly. Follow the steps in Creating a 100Custom.xml configuration file and Deploying a 100Custom.xml file to a deployment environment to modify the runtime properties.

System configuration files

The default IBM Business Automation Workflow runtime properties are defined in the system configuration files. These system configuration files may be updated by software updates, and should not be manually changed. The system configuration files are found in the following locations:

For stand-alone server and cluster member environments:
profile_root\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\config\system\
For clusters:
dmgr_profile_root\config\cells\cell_name\clusters\cluster_name\server_type\config\system\

Configuration file locations

The 100Custom.XML configuration files for different servers and runtime can be found in different locations. The runtime properties for cluster member environments are defined at:
profile_root\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\config\
The runtime properties of clusters are defined in:
dmgr_profile_root\config\cells\cell_name\clusters\cluster_name\server_type\config\

Current settings for a running server

The TeamWorksConfiguration.running.xml file contains configurations that are used by IBM Business Automation Workflow cluster members at runtime. This file is generated when a server is started. For a stand-alone server or cluster members, this file can be found at: 
profile_root\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\TeamWorksConfiguration.running.xml
.
Note: If you cannot see the TeamWorksConfiguration.running.xml file, it is not necessarily a cause for concern. Although the file is regenerated with each server startup, it is no longer needed by the running server after the initial generation. The file may be discarded during node synchronization when the latest configuration changes are mirrored from the deployment manager to the managed node profile. This is expected behavior.