EMA C++ Configuration Guide : 4 Enterprise Message API Configuration Processing : 4.3 Processing the Enterprise Message API XML Configuration File : 4.3.1 Reading the Configuration File : 4.3.1.1 Using EmaConfig.xml in the Working Directory
 
4.3.1.1 Using EmaConfig.xml in the Working Directory
If OmmConsumerConfig lacks an argument, the application attempts to open a configuration file named EmaConfig.xml in the current working directory:
If EmaConfig.xml exists and contains valid XML, the Enterprise Message API uses the XML to modify its configuration.
If EmaConfig.xml exists, but is empty or contains malformed XML, the application uses the default configuration (for details on the default configuration, refer to Section 4.2).
If EmaConfig.xml does not exist, the application uses the default configuration (for details on the default configuration, refer to Section 4.2).
For example, to use an EmaConfig.xml stored in the working directory, have the application create an OmmConsumerConfig object (for details on this object, refer to the Enterprise Message API C++ Developers Guide) and pass it to the OmmConsumer object as follows:
 
 
OmmConsumerConfig config();
 
OmmConsumer consumer(config);
 
For complete details, refer to the example 100__MarketPrice__Streaming included with the LSEG Real-Time SDK.