NOTE: The following section uses Consumer objects (i.e., OmmConsumer and OmmConsumerConfig) to illustrate how the Enterprise Message API checks for a configuration file, and if one exists, how the Enterprise Message API starts to process it.
The OmmConsumer constructor expects an OmmConsumerConfig object. By default, OmmConsumerConfig searches its working directory for a configuration file by the name of EmaConfig.xml. However, if you store your configuration file elsewhere on the system, or use a custom filename, you can include an argument with the configuration object to specify the alternate path and/or name of your configuration file.