EMA C++ Configuration Guide : 4 Enterprise Message API Configuration Processing : 4.1 Overview and Configuration Precedence
4.1 Overview and Configuration Precedence
The Enterprise Message API configuration is determined by hard-coded behaviors, customized behaviors as specified in a configuration file (i.e.,EmaConfig.xml), programmatic changes, and other internal processing. All of these vectors affect Enterprise Message API’s configuration as used by application components. The Enterprise Message API merges configuration parameters specified from all vectors with the following precedence: Function calls, Programmatic Configuration, File Configuration (such as EmaConfig.xml), and finally the default configuration (i.e., if parameters are specified in both function calls and the programmatic configuration, the function call configuration takes precedence).