Apama Capital Markets Foundation Documentation : Capital Markets Foundation : Order Management : Order bridging services
Order bridging services
The order bridging service is analogous to the adapter status and market data bridging services, but for order management events. It provides bridging of com.apama.oms.* events between two correlators, so that an application in the client correlator can submit orders to an adapter or other order destination connected to the server correlator. An order management bridge instance is configured by sending configuration events to the client and server correlators.
On the client side, send a com.apama.oms.ConfigureClientSideBridge event, and on the server side, send a com.apama.oms.ConfigureServerSideBridge event. See the ApamaDoc for these events for details about their fields. In most cases, the fields of the client and server configuration events for a given bridge instance are identical. However, the instanceName field must be unique across all order management bridge services used by the application.
In addition to configuring the order management bridge itself, an application should also configure monitoring of the fake adapter connection between the two correlators, using an instance of the com.apama.connection.IAFStatusFaker and com.apama.adapters.IAFStatusToStatusConvertor services on both sides of the connection. If this is not done, the inter-correlator connection will appear to be down to the order management bridge service and it will not forward any events in either direction. The generic bridging service described above handles this automatically; it is recommended that applications use this service wherever possible. Otherwise, see the implementation of the com.apama.adapter.bridge.ConfigBridge service in the Adapter Bridging Utils bundle to see how bridge connection monitoring is implemented.
Once the order management bridge service is configured, com.apama.oms.NewOrder, AmendOrder and CancelOrders events routed by the client-side application for the bridged service will be forwarded to the server correlator, where they should be handled by the order routing adapter service as normal. Any OrderUpdateevents generated by the order routing adapter service will in turn be forwarded back to the client correlator where they can be handled by application listeners in the usual way.
The order management bridge deals with multiple clients bridging to the same server-side order routing adapter service in the following ways:
*Each client correlator should configure a separate connection to an order management bridge service with a unique instanceName field and channel.
*Multiple order management bridge service clients within the same correlator should ensure that the order identifiers used on new orders are unique within that client correlator.
Copyright © 2013-2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback