Location of 100Custom configuration files

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.

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

System configuration files

The system configuration files contain the default IBM BPM settings that make up the content of the TeamWorksConfiguration.running.xml file. The system files should not be modified other than for product updates. The system configuration files are found in the following location:

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

You can create 100Custom.xml files to modify the default IBM BPM settings. The default 100Custom.xml file and any additional custom files are generally 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\
For clusters:
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 BPM servers at run time. This file is generated when a server is started and is subsequently enhanced by content from the system default files and custom XML change files. Each server_type configuration scope has its own file. The file is only located on the nodes after the servers have been started and it is not located on the deployment manager.

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.

The TeamWorksConfiguration.running.xml file is found in the following location:

For stand-alone server and cluster member environments:
profile_root\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\TeamWorksConfiguration.running.xml