Configuration file format

Sample configuration file shows examples of a configuration file. A configuration file contains the following elements:

• Section names indicate the configuration categories that are included in the file. The [Startup] section (StartUp-parameters) is the only required configuration section. For more information about specifying section names, see Sections-in-configuration-files.
• Parameters specify processing options for the request. Each parameter must appear in the appropriate section of the configuration file. For more information about specifying parameters, see Format-of-configuration-parameters.
• Comments can provide information about the configuration file and its uses. For more information about including comments in a configuration file, see Comments-in-configuration-files.
• Conflict Resolution rules are special sets of configuration parameters that describe how to handle the conflict situations that can occur during apply processing. For more information about conflict resolution rules, see Conflict-resolution.

Lines of input in the configuration file can be up to 1024 bytes long. We recommend that any parameters, section names, or conflict resolution rules should be completed on one line of the file.

If you need to 'split' or 'wrap' one logical line of configuration information onto multiple physical lines, use the plus sign (+) as the last character on a line and continue the configuration information in column 1 of the next line. High-speed Apply Engine appends any characters (including spaces) onto the end of the previous line. For example, when Db2 objects have long names the BMC AMI Log Master for Db2 product can generate High-speed Apply Engine object mapping rules on multiple lines by using the plus sign as the last character in column 72.

Sample configuration file

This section contains the following topics: