The Enterprise Message API is hard-coded to use a default consumer of EmaConsumer. However, you can change this by using the configuration file (e.g., EmaConfig.xml). When you use the XML file, the default Consumer Name is either specified by the DefaultConsumer element, or if this parameter is not set, then the Enterprise Message API application will default to the name of the first Consumer component.
• If DefaultConsumer uses an invalid name (i.e., no Consumer components in the XML file use that name), the Enterprise Message API throws an exception indicating that DefaultConsumer is invalid.
• If the configuration file has no Consumer components, the Enterprise Message API application uses EmaConsumer.