EMA C++ Configuration Guide : 4 Enterprise Message API Configuration Processing : 4.2 Default Configuration : 4.2.2 Default Provider Configurations
 
4.2.2 Default Provider Configurations
Each Enterprise Message API provider-type application must eventually instantiate an OmmProvider object. Constructors for OmmProvider require a OmmProviderConfig object. The OmmProviderConfig constructor can read and process an optional XML file, which applications can use to modify the Enterprise Message API’s default provider behavior. By default this file is named EmaConfig.xml and stored in the working directory. For details on using non-default names and directories for your XML configuration file, refer to Section 4.3.1.2.
The Enterprise Message API provides a hard-coded configuration for use whenever an OmmProviderConfig object is instantiated without an EmaConfig.xml file in the run-time environment. The resulting Enterprise Message API configuration is created by taking the defaults from the various configuration groups.