Hi @shean.rhoden

Try the one copied below. It works fine with my EMA java examples. I didn't try it with the 370__MarketPrice__Batch example but it should work the same. You can probably simplify it even more and rely on EMA default values, but I find it simple enough as it is.

<?xml version="1.0" encoding="UTF-8"?>
<EmaConfig>
<ConsumerGroup>
	<DefaultConsumer value="Consumer_1"/>
	<ConsumerList>
		<Consumer>
			<Name value="Consumer_1"/>
			<Channel value="Channel_1"/>
			<Dictionary value="Dictionary_1"/>
		</Consumer>		
	</ConsumerList>
</ConsumerGroup>
<ChannelGroup>
	<ChannelList>
		<Channel>
			<Name value="Channel_1"/>
			<ChannelType value="ChannelType::RSSL_SOCKET"/>
			<CompressionType value="CompressionType::None"/>
			<GuaranteedOutputBuffers value="5000"/>
			<ConnectionPingTimeout value="30000"/>
			<TcpNodelay value="1"/>
			<Host value="YOUR_ADS_IP_OR SERVER_NAME_GOES_HERE"/>
			<Port value="14002"/>
			<XmlTraceToStdout value="0"/>
		</Channel>
	</ChannelList>
</ChannelGroup>
<DictionaryGroup>
	<DictionaryList>
		<Dictionary>
			<Name value="Dictionary_1"/>
			<DictionaryType value="DictionaryType::ChannelDictionary"/>
		</Dictionary>		
	</DictionaryList>
</DictionaryGroup>
</EmaConfig>

No matter what API you are using the minimum required information in order to connect to TREP (or directly to Elektron feed) is the following:

• Server List (or only a single server name), i.e. the server(s) you want to connect to. Port number is optional. Defaults to 14002.
• DACS username

Everything else is optional in the general scope, although this particular example application (don't know it) may force you put a value for lots of irrelevant stuff.

Good luck.

The EmaConfig.xml file comes with the example contains several groups. If you are just implementing a consumer application, you don't need "NiProviderGroup", "IProviderGroup" and "DirectoryGroup" groups in the sample configuration file. In addition, The sample configuration file has multiple elements in each of the groups to demonstrate different scenarios. Each group needs minimally one element but depend on the requirements of the application, it may have more then one elements. For instance, if the application need to consider channel fail-over situation then it should specify two channels in the ChannelGroup and list the channels in the "channle" argument of the "consumer" element in the ConsumerGroup.

Please take a look at the EMA Configuration guide. It has very clear detail explanation of all the configuration elements.