EMA C++ Configuration Guide : 4 Enterprise Message API Configuration Processing : 4.2 Default Configuration : 4.2.2 Default Provider Configurations : 4.2.2.1 Example: Default Channel Behavior (NiProvider)
 
4.2.2.1 Example: Default Channel Behavior (NiProvider)
The default (hard-coded) behavior for a Channel adheres to the following configuration:
ChannelType value=”RSSL_SOCKET”
CompressionType value=”None”
TcpNoDelay value=”1”
Host value=”localhost”
Port value= “14003”
Note that unlike the Enterprise Message API’s default behavior of choosing the first NiProvider component in the NiProviderList, Enterprise Message API applications will not choose the first Logger or Channel in their respective lists. Instead, if an application wants to use a specific channel, logger, or dictionary configuration, the application must explicitly configure it in the appropriate NiProvider section of the XML file.