In order to submit and manage orders to the EBS exchange, it has been necessary to define a custom pre-processor module that works in conjunction with the standard FIX order manager. The pre-processor is used by routing a new order to the service id defined in session configuration using EBSFIX.SERVICEID parameter. The preprocessor will modify the order to make it suitable for the EBS market before forwarding it on to the usual order manager service and listening for responses (executions etc).

Order management support is enabled on "EBS-FIX" or value of EBSFIX.SERVICEID as specified in the session configuration. Orders must be placed only after subscribing to the Instrument. Time in Force(59) values can be - Good Till Cancelled (59=1,Quote) , Immediate or Cancel (59=3,Hit) and (59=4) Fill or Kill (Full Amount trading for Direct pairs).

According to the specification CancelOrder should have Order Type, so

Ice berg Enabled order should contain DisplayQty(1138) in extraParams. You can also specify Display method(1084) and IcebergHigh RandomTime(20112). If you don't specify it will take default values. To amend icebrg enabled order, you should send the display quantity in amend order. Sample events:

If a user is interested in placing 'FIXING' orders then you should request the same in user login request by adding parameter 'AllowFixingInfo' in UserData as:

Once logged in successfully, you will get a trading session status message which provides information on the status of the market. This message carries trading ID, its status, ValuationDateTime etc. To place a fixing order, EBS expects us to send mandatory tags - TimeInForce (Tag 59) MarketSegmentID (Tag 1300) TradingSessionID (Tag 336) ValuationDateTime (Tag 20107)

Client just needs to send an extra parameter 'TradingSessionID' with a value in the NewOrder event and adapter will map remaining tags from its cache.

For example:

For amending a fixing order, you don't need these mandatory tags except TimeInForce which will be taken care by adapter.

PartyInfo which is received as part of TradeCaptureReport, will be published in OrderUpdate as follows

The PartyInfo in the above example is "Party0":"Progress,BIC,Executing Broker" Where, "Party_x":"PartyID, PartyIDSource, PartyRole"

In EBS support monitor, on receiving an execution report with a partial fill or fill, you will open a listener for corresponding TCR with same matching Id. This execution report will be sent to base FIX Ordermanager after receiving matching TCR. In some cases though you receive an ER with filled state but still you need to receive corresponding TCR. Meanwhile user tries to cancel order but gets rejected by exchange. To handle such scenarios, use __APAMA_ORDER_STATE extra parameter to handle order completion as stated below,