Capital Markets Adapters 10.11 | Apama Capital Markets Adapters Documentation 10.11 | FXall TCPI Server Adapter | Status reporting events
 
Status reporting events
 
Adapter object
Status reporting uses the standard com.apama.statusreport event interface, defined in the StatusSupport.mon file. Heartbeats and status messages between the service monitors and the transport/codec are managed by the IAFStatusManager.mon service monitor.
Applications should subscribe to status by sending the following event to the correlator:
com.apama.statusreport.SubscribeStatus("FXALL_TCPI",<object>,"",<transportname>)
Where <transportname> is the transport name as used in the SessionConfiguration event, and <object> is one of the following:
Adapter
subscriptions where all fields are "wildcards" are also supported:
com.apama.statusreport.SubscribeStatus("", "", "", "")
In this case the subscriber will receive all status reports from the FXALL_TCPI adapter as well as every other status-reporting entity in the system.
A com.apama.statusreport.UnsubscribeStatus event with the same field values can be used to cancel a previous status subscription.
Status reports are routed as com.apama.statusreport.Status objects, with the "serviceId", "object" and "connection" fields set as above for subscriptions. The reported status is as follows: