Context Configuration File

This section defines the components available in TAFC configuration files.

On each server, there can be a number of TAFC configuration files. Each file contains setup information for one context on that server. The pool of configuration files (one on each server) for a given context act as a decentralized database configuring behaviour of the cluster associated with that context name.

You can locate the configuration files from the path below.

$TAFC_HOME/config/$TAFC_CONTEXT/tafc.ini

For example, if TAFC_HOME=/home/tafc and TAFC_CONTEXT=default, then the file is /home/tafc/config/default/tafc.ini.

Sections

The configuration file is made up of number of sections. Each section starts with a label [sectionName].

Parameters

Each section contains a number of named parameters as follows:

paramName=paramValue

Parameters are textual strings that can be compared for equality or inequality with other parameters. Numeric parameter types are not supported. Although a parameter may have numerical meaning to its local application, but it cannot be compared as greater or less than another parameter.

[common] Section

The [common] section name is reserved. Parameters in this section are from a configuration management perspective, equivalent to environment variables. For example,

[common]
		aParam=123

A remote server matches a local environment variable set as:

    export aParam=123

Meta-sections

Some sections, for example [OSLevels] are generated on the fly when the configuration file is queried. This enables the same comparison mechanism to be used for meta-sections and regular sections.

Configuration File as a URL

If environment variable TAFC_INI_URL is set, then the configuration file will be loaded from this location instead of the local system. This mechanism enables several servers to share a configuration file. Be aware:

• This introduces a single point of failure. If the location becomes unavailable, then all servers will fail.
• If all servers use the same configuration, then all equality TICs will pass and all inequality TICs will fail. Wherever differing parameters are required, they should be put into environment variables rather than the file.

Sample Configuration File

A typical configuration file is:

[common]
    		anEnvVariableName=aValue
[aSectionName]
    		aParameterName=aParameterValue
		anotherParameterName=anotherValue