EMA C++ Configuration Guide : 2 Configuration Overview : 2.2 Parameter Overview
 
2.2 Parameter Overview
Many default behaviors are hard-coded into the Enterprise Message API library and globally enforced. However, if you need to change API behaviors or configure the API for your specific deployment, you can use the Enterprise Message API’s XML configuration file (EmaConfig.xml) and adjust behaviors using the appropriate parameters (discussed in this section). While the Enterprise Message API globally enforces a set of default behaviors, certain other default behaviors are dependent on the use of the XML file and its settings.
For example, according to the Enterprise Message API’s global default behavior:
The Enterprise Message API’s logs its messages at a LoggerSeverity level of Success to a file named emaLog_pid.log (where pid is the process ID). You can manually change the LoggerSeverity and the log filename by using EmaConfig.xml.
The Enterprise Message API does not XML trace to file (equivalent to XmlTraceToFile value=“0”). You need to add this parameter only if you want to turn on XML tracing. If you turn on XML tracing (a non-default behavior), the Enterprise Message API will trace to a file named EmaTrace (equivalent to XmlTraceFileName value=“EmaTrace”).