When acting as a client to MATCHING FIX GATEWAY(MFG), the IAF should be configured with the MFG specific configuration file, the distribution version of which can be found here:

Note that the requirement for a MAPI-specific configuration file means that an IAF using this configuration file must be used for MAPI FX FIX sessions only. The QFIX adapter will not interoperate correctly with other FIX servers once it has been configured for MAPI operation. If you need to connect to other FIX servers as well as MAPI, the non-MAPI sessions should be configured in a separate IAF instance. However, MAPI and non-MAPI session can co-exist safely within the same correlator instance.

As well as the standard host, port, sender and target CompID the following parameters must be supplied for MAPI session:

MFG will not allow client to use message header tags 1128 and 1156 to specify a different protocol version then that which was already defined as the default version within initial to the session.

Tag#1128 (ApplVerID) - Supported values are 9 (FIX50SP@). All others result in reject.

Tag#1156 (ApplExtID) - Valid value ="100". All others result in reject

These are defined in .dist file as:

The logon message will identify the default version of FIX to be carried over the given FIX session in tag 1137 (DefaultApplVerID) and tag 1147 (DefaultApplExtID)

These are defined in .dist file as:

You can assign username and password using,