1 Introduction
1.1 About this Manual
1.2 Audience
1.3 Definitions
1.4 Acronyms and Abbreviations
1.5 References
1.6 Document Conventions
1.6.1 Typographic
1.6.2 Data Types
1.6.3 Field and Text Values
1.6.4 Boolean Values
2 Configuration Overview
2.1 About Message API Configuration
2.2 Parameter Overview
2.3 Default Behaviors
3 Configuration Groups
3.1 ConsumerGroup
3.1.1 Generic XML Schema for ConsumerGroup
3.1.2 Setting a Default Consumer
3.1.3 Configuring Consumers in a ConsumerGroup
3.1.4 Consumer Entry Parameters
3.2 IProvider Group
3.2.1 Generic XML Schema for Provider Group
3.2.2 Setting a Default IProvider
3.2.3 Configuring an IProvider in an IProviderGroup
3.2.4 IProvider Entry Parameters
3.3 NiProvider Group
3.3.1 Generic XML Schema for NiProviderGroup
3.3.2 Setting a Default NiProvider
3.3.3 Configuring an NiProvider in an NiProviderGroup
3.3.4 NiProvider Entry Parameters
3.4 Channel Group
3.4.1 Generic XML Schema for ChannelGroup
3.4.2 Universal Channel Entry Parameters
3.4.3 EMA Channel Connection Types
3.4.4 Parameters for Use with Channel Type: RSSL_SOCKET
3.4.5 Parameters for Use with Channel Types: RSSL_HTTP
3.4.6 Parameters for Use with Channel Types: RSSL_WEBSOCKET
3.4.7 Parameters for Use with Channel Types: RSSL_ENCRYPTED
3.4.8 Parameters for Use with Channel Type: RSSL_RELIABLE_MCAST
3.4.9 Example XML Schema for Configuring ChannelSet
3.4.10 Example Programmatic Configuration for ChannelSet
3.5 Warm Standby Channel Group
3.5.1 Generic XML Schema for WarmStandbyGroup
3.5.2 Warm Standby Channel Entry Parameters
3.6 Warm Standby ServerInfo Group
3.6.1 Generic XML Schema for WarmStandbyServerInfoGroup
3.6.2 Warm Standby ServerInfo Entry Parameters
3.7 Server Group
3.7.1 Generic XML Schema for ServerGroup
3.7.2 Server Entry Parameters
3.7.3 EMA Server Connection Types
3.7.4 Parameters for Use with ServerType RSSL_ENCRYPTED
3.7.5 Parameters for Use with ServerType RSSL_WEBSOCKET
3.8 Logger Group
3.8.1 Generic XML Schema for LoggerGroup
3.8.2 Logger Entry Parameters
3.9 Dictionary Group
3.9.1 Generic XML Schema for DictionaryGroup
3.9.2 Dictionary Entry Parameters
3.10 Directory Group
3.10.1 Generic XML Schema for Directory Entry
3.10.2 Setting Default Directory
3.10.3 Configuring a Directory in a DirectoryGroup
3.10.4 Service Entry Parameters
3.10.5 InfoFilter Entry Parameters
3.10.5.1 Capabilities Entry Parameter
3.10.5.2 DictionariesProvided Entry Parameter
3.10.5.3 DictionariesUsed Entry Parameter
3.10.5.4 QoSEntry Section and Associated Parameters
3.10.6 StateFilter Entry Parameters
3.10.7 LoadFilter Entry Parameters
3.10.8 Status Entry Parameters
3.10.9 Setting Directory with Multiple Dictionaries Provided for IProvider
4 Enterprise Message API Configuration Processing
4.1 Overview and Configuration Precedence
4.2 Default Configuration
4.2.1 Default Consumer Configuration
4.2.2 Default Provider Configurations
4.2.2.1 Example: Default Channel Behavior (NiProvider)
4.2.2.2 Example: Default Server Behavior (IProvider)
4.3 Processing the Enterprise Message API XML Configuration File
4.3.1 Reading the Configuration File
4.3.1.1 Using EmaConfig.xml in the Working Directory
4.3.1.2 Using a Custom Filename and/or Directory
4.3.2 Use of the Correct Order in the XML Schema
4.3.3 Processing the Consumer “Name”
4.3.4 Processing the Provider “Name”
4.4 Configuring the Enterprise Message API Using Function Calls
4.4.1 Configuration Function Calls
4.4.1.1 OmmConsumerConfig Class Function Calls
4.4.1.2 OMMIProviderConfig Class Function Calls
4.4.1.3 OMMNIProviderConfig Class Function Calls
4.4.2 Using the host() Function: How “Host” and “Port” are Processed
4.4.3 Service Discovery Configuration Using Function Calls
4.4.3.1 ServiceEndpointDiscovery
4.4.4 Multi-Credential Configuration
4.4.4.1 OAuth2Credential Class Functions
4.5 Programmatic Configuration
4.5.1 OMM Data Structure
4.5.2 Creating a Programmatic Configuration for a Consumer
4.5.3 Example: Programmatic Configuration of a Consumer
4.5.4 Creating a Programmatic Configuration for an IProvider
4.5.5 Example: Programmatic Configuration of an IProvider
1.1 About this Manual
4.5.5 Example: Programmatic Configuration of an IProvider
This site works best with JavaScript enabled