Initial Configuration

Time and Time Zone

Set the machine that hosts the MEFF Gateway to run in (GMT+1:00) Central European Time (Madrid) zone and time. However, timestamps on all orders and fills are in UTC.

Since MEFF operates in (GMT+2:00) CEST in the summer, you must enable the Automatically adjust clock for daylight saving changes setting.

TTChron Settings

The gateway installs with the correct default start and stop times configured for each service in TTChron. Consult with your TAM before attempting to change any of these settings.

Configuring Login Information

You must use the exchange-provided account number when submitting orders. If you connect directly to the exchange, your account number equals the five-character account number provided by the exchange.


If you do not provide an account number, the exchange assigns the firm’s (Member’s) Daily Account number to the order. This may result in the order being filled at the exchange but listed under a different account.

To avoid any potential issues, TT strongly recommends using the exchange-provided account number when submitting orders.

When connecting to the exchange with a clearing firm or external account, you may need to request sub-account numbers from the exchange that adhere to the five-character limitation. You can work with the exchange and the clearing firm to map the new sub-account values to your existing clearing account.

If you provide an invalid account number (e.g., longer than five characters or that contains spaces), the exchange rejects the transaction and forwards a %MFEONSIVF-Invalid value for field [1=...] message to the X_TRADER® Audit Trail.

Configuring Hostinfo.cfg After an Upgrade

In addition to configuring the new credentials for connecting to HF MEFFGate, ensure that ExchangeCompany=XMEF in both the [PriceServer] and [OrderServer] sections in hostinfo.cfg after an upgrade to MEFF Gateway 7.17.20.

Member, Group, Trader IDs

You can determine and set up any Group ID and Trader ID you like, however, you must use the Member ID as distributed by MEFF. The exchange does not require members to identify each user individually.

You must complete the following fields in Guardian to map a TTORD proxy trader to a direct trader:

  • Exchange: the TT Gateway exchange-flavor (e.g., MEFF-A)
  • Member: MEFF provides the SenderCompID (1st 4 Characters of the Trader ID). This value should be entered into the GatewayCompany parameter of the [OrderServerSession] of the hostinfo.cfg file. If the Member parameter is configured in the [OrderServerSession], its value will be used as the Member portion of the direct trader.
  • Group: a three-digit variable defined by the firm.
  • Trader: a multi-digit variable defined by the firm.

If an incorrectly mapped TTORD trader submits a trade, the MEFF Gateway rejects the transaction and forwards a No mapping for Trader TTORDXX 001 001 acct |XX001001| in database error message to the X_TRADER® Audit Trail.

If a TTORD trader submits a trade with an unrecognized account, the MEFF Gateway rejects the transaction and forwards a Trader TTORDXX 001 001 is not allowed to use account |ABC| error message to the X_TRADER® Audit Trail.

Verifying the Key Range

MEFF Gateways install with the following default key range: 0M0000-0MZZZZ.

For information on configuring the key range, refer to the TT Gateway Architecture SAM Version 7.X.