com.apama.oms
Monitor ServerBridge


This service allows another correlator to submit orders to an adapter attached to this one.

This service is used to bridge the com.apama.oms interface between two correlators. One correlator, connected to an adapter, acts as a server. The other correlator as a client. To perform the bridging, this monitor needs to be injected in the server correlator and an instance created by sending in the ConfigureServerSideBridge event. The two correlators must be connected to each other, and the channels in the configuration events have to match those of the engine connections.

This server instance listens for the new orders coming from other correlators and makes sure that they receive the order updates.

This service will also monitor the connection by using the IAFConnectionMonitor component, note that this means that the IAFStatusFaker must be running on the client correlator. Setting up instances of The IAFConnectionMonitor will normally be done by the adapter bridging configuration service. When a connection goes down, this monitor will unsubscribe to the adapter. When it comes back up, it will re-subscribe.
Since:
CMF 1.1.0
Version:
10.2
See Also:
com.apama.adapter.bridge.ConfigBridge - The adapter bridging config service will normally create instances of this bridge
com.apama.oms.ClientBridge - The client bridge communicates with the server bridge in another correlator.
com.apama.adapters.IAFConnectionMonitor - This bridge monitors the connection to the client correlator using this connection monitor
Routes:
com.apama.oms.CancelOrder - 
Sends:
com.apama.oms.OrderUpdate - The updates on orders to send back to the client correlator
Listens:
com.apama.oms.ConfigureServerSideBridge - The event that creates instances of this monitor.
com.apama.oms.NewOrder - New orders that are received from client orders
com.apama.oms.OrderMonitorFinished -