Splitting server configuration information

Configuration elements that are common to all IBM® z/OS® Connect Servers can be included from a shared configuration file.

Each server must have a valid Liberty server configuration file that is called server.xml in its server configuration directory ${server.config.dir}. The following mechanisms can be used to split a server configuration file into server-specific content and content that is common to multiple servers:

Use include elements in server configuration files to include additional server configuration files, in the format.
```
<include  location="pathname/filename"/>
```
For example, each server's configuration file might contain only those entries that are specific to that server and specify an element to include another configuration file whose content is common to all servers.
When you use include elements, be aware of the Liberty profile configuration element merging rules. See Liberty:Configuration element merging rules in the WebSphere® Application Server for z/OS documentation. Specify each element's attribute in only one of the configuration files to ensure that only one value takes effect. For more information, see Using include elements in configuration files in the WebSphere Application Server for z/OS documentation.
Use properties in server configuration files to enable an otherwise server-specific element to be contained in the common server configuration file. Properties for each server are defined in a file that is called bootstrap.properties in the server configuration directory ${server.config.dir}. The properties are defined in the format of name=value pairs that are written one line per property. For example,
```
propertyName=propertyValue
```
Server configuration files can reference these properties by using the syntax.
```
${propertyName}
```
For example, for two servers to specify unique three-part names for WOLA, the configuration file contains the following statements.
- server1 has a bootstrap.properties file with the following content:
  - wola_dgn=ZC1DGN
  - wola_ndn=ZC1NDN
  - wola_svn=ZC1SVN
- server2 has a bootstrap.properties file with the following content:
  - wola_dgn=ZC2DGN
  - wola_ndn=ZC2NDN
  - wola_svn=ZC2SVN
A shared configuration file might then specify the element by using these properties:
```
<zosLocalAdapters wolaGroup="${wola_dgn}" wolaName2="${wola_ndn}" wolaName3="${wola_svn]" />
```
Note: If you update the bootstrap.properties file, you must restart the server for the changes to take effect. For more information, see Using variables in configuration files in the WebSphere Application Server for z/OS documentation.