IAF configuration
BARX Adapter can be configured to run in two modes - Legacy or MDA
MDA configuration makes use of the Market Data API of the Apama CMF
Order handling is done using the Legacy Mode even when Quote (Market data) handling is done using MDA mode
When acting as a client to BARX, the IAF should be configured with the BARX specific configuration file, the distribution version of which can be found here:
${APAMA_HOME}/adapters/config/FIX-BARX.xml.dist (for MDA Mode)
or
${APAMA_HOME}/adapters/config/FIX-BARX-Legacy.xml (for Legacy Mode)
Note that the requirement for a BARX-specific configuration file means that an IAF using this configuration file must be used for BARX FIX sessions only. The FIX adapter will not interoperate correctly with other FIX servers once it has been configured for BARX operation. If you need to connect to other FIX servers as well as BARX, the non-BARX sessions should be configured in a separate IAF instance. However, BARX and non-BARX session can co-exist safely within the same correlator instance.
BARX uses a custom data dictionary (FIX42-BARX.xml). This file must be referenced by the "QuickFIX.DataDictionary" transport property. For example:
<property name="QuickFIX.DataDictionary" value="${APAMA_HOME}/adapters/config/FIX42-BARX.xml"/>
The IAF configuration file should contain appropriate host, port, sender and target CompID parameters.
For the MDA Mode the path of the correct adapter configuration file should also be provided using the property -