In the following configuration file snippet (only those parts needed for the example are included), the application creates a consumer with a Name of Consumer_1 which logs to a file named emaLogfile.
<ConsumerGroup>
<ConsumerList>
<Consumer>
<Name value="Consumer_1"/>
<Logger value="Logger_2"/>
</Consumer>
</ConsumerList>
</ConsumerGroup>
<LoggerGroup>
<LoggerList>
<Logger>
<Name value="Logger_2"/>
<LoggerType value="LoggerType::File"/>
<FileName value="emaLogfile"/>
</Logger>
</LoggerList>
</LoggerGroup>
Now assume that the following was not included in the XML configuration:
<FileName value="emaLogfile"/>
In this case, the Enterprise Message API application relies on its hard-coded behavior and uses the filename emaLog_pid.log.
However, if the snippet is configured in either of the following configurations, the Enterprise Message API application reverts to its default behaviors because the parameters are not in the correct order (i.e., the FileName parameter needs to be contained in a Logger component entry):