FIX_StatusManager
The FIX_StatusManager provides session status notifications to other applications via the com.apama.statusreport interface.
For each session the following are monitored:
Connection Status - Notifies applications of a loss of connection to the IAF as detected by the
FIX_SessionManager.
Session Status - Notifies applications when the transport is logged in or out of the target server.
Trading Session Status - Some exchanges support the notion of trading session status and report this through the corresponding FIX message. The session manager will notify applications of a change in status.
Market Data - Warns applications that no market data has been received for a specified length of time.
Any application wishing to receive the reports must route a com.apama.statusreport.SubscribeStatus event specifying the following parameters (blank strings are taken as wildcards):
Input | Description |
ServiceId | "FIX" |
Object | "Adapter" |
Sub_serviceId | The connection (transport) prefix |
connection | The connection (transport) name |
The sub-service id can be used to subscribe to groups of related connections. For example, if we had the following transports:
EXCHANGE1_MARKET_DATA
EXCHANGE1_TRADING
EXCHANGE2_MARKET_DATA
EXCHANGE2_TRADING
We could subscribe to all status relating to exchange 1 by routing the following subscribe event:
SubscribeStaus("FIX", "Adapter", "EXCHANGE1", "")
We could subscribe to status for all the connections by routing the following:
SubscribeStaus("FIX", "Adapter", "", "")
Note, the sub-service separator token defaults to “_” but can be overridden at session configuration time (see below).
To stop receiving status events a corresponding com.apama.statusreport.UnsubscribeStatus event must be routed.
