IAF configuration
When acting as a client to Lava, the IAF should be configured with the Lava- specific configuration file, the distribution version of which can be found here: ${APAMA_HOME}/adapters/config/FIX-Lava.xml.dist
Note that the requirement for a Lava-specific configuration file means that an IAF using this configuration file must be used for Lava FIX sessions only. The FIX adapter will not interoperate correctly with other FIX servers once it has been configured for Lava operation. If you need to connect to other FIX servers as well as Lava, the non-Lava sessions should be configured in a separate IAF instance. However, Lava and non-Lava 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 all Lava sessions:
<!-- Username -->
<property name="StaticField.body.A.553" value="<LAVA_USER>"/>
<!-- Password -->
<property name="StaticField.body.A.554" value="<LAVA_PASSWORD>"/>
<!--- start/end time/day properties and default values ---->
<!--
Start/end days/times are based on days as well for LAVA.
LAVA's trading session is Sun 5pm to Fri 5pm.
Note that you must start the adapters before the
start day/time.
-->
<property name="QuickFIX.StartTime" value="22:31:00" />
<property name="QuickFIX.EndTime" value="21:59:00" />
<property name="QuickFIX.StartDay" value="sun" />
<property name="QuickFIX.EndDay" value="fri" />
The session start/end time specifications always use UTC - users may need to update their configuration files to account for daylight savings time changes, depending on their local time zone.
Note:
The QuickFIX.ResetOnLogon property must be set to "Y" for market data connections and "N" for trading connections.