EMA C++ Configuration Guide : 4 Enterprise Message API Configuration Processing : 4.3 Processing the Enterprise Message API XML Configuration File
4.3 Processing the Enterprise Message API XML Configuration File
The LSEG Real-Time SDK package installs a default configuration file named EmaConfig.xml into the Enterprise Message API’s working directory. By default, the Enterprise Message API looks for a configuration file with this name in the working directory. If you want to use a different name for your configuration file, and/or store the file in a directory other than the working directory, you must specify this filename and/or directory in your configuration object. For further details on using the configuration object, how it functions as regards paths and filenames, and how the Enterprise Message API determines its configuration, refer to Section 4.3.1.
Except for the parameters DefaultConsumer and DefaultNiProvider, you must wrap all other elements defined in the Enterprise Message API’s configuration file in a component definition (i.e., Consumer, NiProvider, Logger, Channel, or Dictionary) otherwise the Enterprise Message API ignores the element. This section includes some examples that illustrate this requirement.