In this use case, the Enterprise Message API manages the entire connection from start to finish. To use session management, you need to configure the API to enable session management. To do so, in the ChannelGroup, set the Channel entry parameter EnableSessionManagement).
The API exhibits the following behavior for this use case:
1. Obtains a token (according to the details in Section 6.4.2).
2. Queries service discovery (according to the details in Section 6.6).
3. Consumes market data (according to the details in Section 6.7).
Manages login reissues for Version 1 authentication when needed on a cyclical basis (according to the details in ).Enterprise Message API’s Consumer example (113__MarketPrice__SessionManagement example) provides sample source to illustrate session management.
With session management enabled, application may specify a host and port in ChannelGroup parameters. In this case, the Enterprise Message API exhibits the same behavior listed above, but ignores the endpoints it receives from the service discovery and connects to the specified host and port.