IAF configuration
When acting as a client to EBS Gateway(EBS FIX 4.4), the IAF should be configured with the EBS FIX specific configuration file, the distribution version of which can be found here: ${APAMA_HOME}/adapters/config/FIX-EBS-MDA.xml.dist
For Market data the path of the correct adapter configuration file should also be provided using the property
<property name="AdapterConfiguration" value="${APAMA_HOME}/adapters/config/FIXTransport-BaseFIXLibrary-EBS.xml" />
Note that the requirement for a EBS-FIX specific configuration file means that an IAF using this configuration file must be used for EBS FIX 4.4 sessions only. The FIX adapter will not inter-operate correctly with other FIX servers once it has been configured for EBS FIX 4.4 operation. If you need to connect to other FIX servers as well as EBS FIX 4.4, the non-EBS FIX 4.4 sessions should be configured in a separate IAF instance. However, EBS FIX 4.4 and non-EBS FIX 4.4 session can co-exist safely within the same correlator instance. As well as the standard host, port, sender and target CompID parameters, the following parameters must also be supplied for marketData session:
<!-- Username (supplied
by EBSGW) --> <property name="StaticField.body.A.553"
value="@USERNAME@"/> <!-- Password (supplied by EBSGW) -->
<property name="StaticField.body.A.554" value="@PASSWORD@"/>
<property name="StaticField.body.A.1408" value="1.1"/>
Note:
The property StaticField.body.A.1408 must be enabled in IAF configuration when you want to interact with old EBS venues (that is, Platform 1/0/1.1).