Setting configuration properties using 100Custom.xml

To modify the Process Server or IBM® Process Center configuration, you must create a 100Custom.xml file if it does not exist. Then you can change the configuration properties in the 100Custom.xml files of the IBM BPM deployment environment to override the default configurations in other XML configuration files (such as the 99Local.xml file), including repository server information and Performance Data Warehouse communication methods.

Before you begin

CAUTION:

You should make a backup copy of the XML configuration files that you intend to modify. These files are located in the .../config directory under the IBM BPM profile root directory (which should not be confused with the .../config directory under the WebSphere profile root directory). The location of the files in the IBM BPM .../config directory is described in the topic Location of configuration files. When you make a backup copy of the files, you can leave the copies in the IBM BPM .../config directory and rename their file extensions from *.xml to *.bak, or you can move the copies to another directory that is not under the .../config directory.

All the files in the IBM BPM .../config directory that end in .xml are loaded when you start or restart the product. The XML files are loaded in a sequence where those starting with a letter of the alphabet are loaded before ones that start with numbers, which are loaded in numeric order. So any copies of XML configuration files that keep the .xml extension can cause unexpected behavior.

For example, if you have the following files in the IBM BPM ../config directory, they are loaded in the order shown.

.../config/system/Copy of 99Local.xml
.../config/system/00Static.xml
.../config/system/50AppServer.xml
.../config/system/60Database.xml
.../config/system/80EventManager.xml
.../config/system/98Database.xml
.../config/system/99Local.xml
.../config/100Custom.xml

In this example, the possibly old settings in the Copy of 99Local.xml file take effect first and all settings in the 99Local.xml file are ignored - except for elements that include the attribute merge="replace".

Tip: Always use a standard extension for the copies (for example, .bak).

In an ND environment, ensure you are editing the 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.

About this task

At run time, only the settings from the application server files are read. If you make changes after deployment in an ND environment, you must make them on the deployment manager profile in the cluster member version of the file for each server and then synchronize the changes to the managed nodes, which enables the changes to take effect at run time.

For network deployment 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 will be used by certain administrative commands that run in local mode, such as the BPMUpdateSystemApp command.

Important: If you edit the file at the cluster member level, make the changes at the cluster level as well to ensure that the changes are also created on new cluster members when they are added in the future. The 100Custom.xml file on the cluster level cannot contain node-specific settings or server-specific settings, such as host names. For more information about the location of the configuration files, see the topic Location of configuration files.

Procedure

To change the cluster members, complete the following steps:

Stop the servers for Process Server or Process Center.
Although the preferred way of updating 100Custom.xml files is by running the updateBPMConfig command (as described in the topic updateBPMConfig command), you can manually update the 100Custom.xml files by completing the following substeps:
1. Open the appropriate 100Custom.xml configuration file or files to your topology. If you have an ND environment, make the same changes to the 100Custom.xml file of each cluster member. For more information about the location of the configuration files, see the topic Location of configuration files.
  Tip: If, for some reason, the 100Custom.xml file is missing, copy it from the appropriate server location:
  - For both Process Server and Process Center: install_root\BPM\Lombardi\process-server\configTemplates\100Custom.xml.
  - For Performance Data Warehouse: install_root\BPM\Lombardi\performance-data-warehouse\configTemplates\100Custom.xml
2. Copy the relevant sections from the 00Static.xml or 99Local.xml file to the 100Custom.xml files appropriate to your topology.
  Note: If you omit a property value where a Boolean type is expected, the property value defaults to false. In the case of some configuration properties (for example, <automatic-schema-management>), if the property is commented out, its value defaults to true.
  
  Important: Apply customizations and modifications only to the 100Custom.xml file or additional files added to the same directory as the 100Custom.xml file.
3. Save your changes in the 100Custom.xml file.
If you have an ND environment and you did not stop the deployment manager and node agents as described at the beginning of this procedure, select Full Resynchronize to replicate the settings from the deployment manager server to the individual nodes.
Start the servers for Process Server or Process Center.