Comparing RFA and EMA, we interpret EMA config management via EMAConfig.xml is not as flexible as RFA.
From configuration file perspective, with RFA specifying one Session it is possible to connect to several Connections (not only resiliency pair, but several ADS group or silos), each connection / ADS pool providing different concrete service.
Only modifying RFA configuration (not modifying the RFA source code), we can add (in the session) a connection / pool of ADS, providing new services.
With EMAConfig.xml, we understand it is not feasible to add a new ADS Pool to be used by EMA application without source code modification. We interpret we only can specify via OmmConsumerConfig() one Consumer, and a single ChannelSet (ADS Pool) per consumer, is it correct ?
How to achieve with EMA Application configuration (as RFA), ADS pool addition (as RFA adding connection within session). ?