Location of configuration files

Path names to configuration files are specific to the server type you are configuring, where server_type is performance-data-warehouse, process-center, or process-server. In addition, the location of the configuration files depends on whether your environment is a stand-alone or a clustered network deployment environment.

For general information about the 100Custom.xml file and the use of elements and attributes (such as the merge attribute), see the topic "The 100Custom.xml file and configuration."

Table 1. . Configuration file location in stand-alone environments and clustered network deployment (ND) environments
Files	Stand-alone server	Network deployment (ND) environment
System configuration XML files	`standalone_profile_root\config\cells\cell_name\nodes\node_name \servers\server_name\server_type\config\system\99Local.xml`	In the deployment environment's cluster, go to `dmgr_profile_root\config\cells\cell_name\clusters\cluster_name \server_type\config\system\99Local.xml` where `cluster_name` is either the application cluster name (when `server_type` is `process-server` or `process-center`) or the support cluster name (when `server_type` is `performance-data-warehouse`). For each cluster member, go to `dmgr_profile_root\config\cells\cell_name\nodes\custom_node_name \servers\cluster_member_name\server_type\config\system\99Local.xml` where `cluster_member_name` is either the application cluster member name (when `server_type` is `process-server` or `process-center`) or the support cluster member name (when `server_type` is `performance-data-warehouse`).
Location of 100Custom.xml file	`standalone_profile_root\config\cells\cell_name\nodes\node_name \servers\server_name\server_type\config\100Custom.xml`	In the deployment environment's cluster, go to `dmgr_profile_root\config\cells\cell_name\clusters\cluster_name \server_type\config\100Custom.xml` where `cluster_name` is either the application cluster name (when `server_type` is `process-server` or `process-center`) or the support cluster name (when `server_type` is `performance-data-warehouse`). Note: For ND environments, XML configuration files on the cluster level are templates for 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 each cluster member, go to `dmgr_profile_root\config\cells\cell_name\nodes\custom_node_name \servers\cluster_member_name\server_type\config\100Custom.xml` where `cluster_member_name` is either the application cluster member name (when `server_type` is `process-server` or `process-center`) or the support cluster member name (when `server_type` is `performance-data-warehouse`). Important: At run time, only the settings from these cluster member files are read.
Location of TeamWorksConfiguration.running.xml file	`standalone_profile_root\config\cells\cell_name\nodes\node_name \servers\server_name\server_type\TeamWorksConfiguration.running.xml`	`node_profile_root\config\cells\cell_name\nodes\managed_node_name \servers\cluster_member_name\server_type\TeamWorksConfiguration.running.xml` For each running server, the TeamWorksConfiguration.running.xml file only exists on the node profile server location for the specific server. It is generated by merging the settings from all underlying configuration files at startup and it contains the setting used by the running server. The process-server, process-center, and performance-data-warehouse directories each have a TeamWorksConfiguration.running.xml file. Note: If you cannot see the file, it is not necessarily a cause for concern. The file is regenerated with each server startup, but 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.