Configuration Guide
Plain Text Configuration Files

Informatica generally recommends the use of XML Configuration Files due to its greater flexibility. It covers a superset of use cases as compared to plain text configuration files.

The plain text configuration file (sometimes called a "flat" file), when invoked, writes option values into UM's current default attributes. These are then read and used in the creation of all objects.

See Example Configuration Scenarios for example configuration files.

Reading Plain Text Configuration Files  <-

There are two ways to read a plain text configuration file to set values in current default attributes.

API function lbm_config()
You can call the API multiple times with different file names to set configuration options in phases.

When you create UM objects (such as a context or receiver), UM sets attributes for that object using the current default attributes. Hence, you must call lbm_config() before creating objects (lbm_*_create()).

Environment variable LBM_DEFAULT_CONFIG_FILE
Reads configuration file when your application is started. You can set this variable to a full pathname or a URL; for example:
export LBM_DEFAULT_CONFIG_FILE=/home/lbm/lbtrm.cfg

(You can still use the lbm_config() API on a different file to make additional changes.)

Plain Text Configuration File Format  <-

A plain text configuration file contains lines that each take the form:

scope_keyword option_name option_value


scope_keyword - the scope to which the option applies,

option_name - the predefined name for the option, and

option_value - the new value to be assigned to that option.

Allowable values for these parameters are given throughout the rest of this document. Any text following a hash character # (also known as a pound sign, number sign, or octothorp) is interpreted as comment text and is ignored.

For example:

# Set transport_tcp_port_low to 4901
context transport_tcp_port_low 4901
# And set transport_tcp_port_high to 4920
context transport_tcp_port_high 4920
For plain text configuration files, do not enclose any fields in double quotation marks (").