Configuring Access to All Markets
NASDAQ_OMX_EU Gateways connect to multiple exchanges and require a unique approach to trader mapping and Customer Defaults than other gateways.
To properly setup support for trading all products available through the NASDAQ_OMX_EU Gateway, TT recommends the following:
- Select Member IDs that reflect the name of the exchange that will be accessed by the related order session
- Create Customer Defaults and accounts for each exchange
- For each trader, create two TTORD IDs: one for NLX and
one for Nordic
To access products on both NLX and Nordic, the user must upgrade to X_TRADER 7.17.X and TT User Setup 7.17.X.
The following table illustrates how IDs are mapped between X_TRADER, TT User Setup, and the exchange.
TT User Setup
The Firm ID provided by the exchange.
This value is forwarded to the exchange as FIX Tag 49.
Not present in the hostinfo.cfg file
The traders’ Operator ID.
The exchange provides this value and the gateway uses this value to populate FIX Tag 50.
Mapped to the order session via the Member parameter
Trader ID (MGT)
The Trader ID portion of the direct trader’s Member, Group, Trader ID (MGT).
The exchange provides this value and the gateway uses this value to populate FIX Tag 553.
Member ID (MGT)
The Member ID portion of the direct trader’s Member, Group, Trader ID (MGT).
This value is user-defined and used to map direct trader logins and the gateway order session.
Configuring Support for all Products
The following procedure provides and overview on how to configure gateway logins in TT User Setup and order sessions on the NASDAQ_OMX_EU Gateway to support trading all available products.
To configure support for all products:
- In TT User Setup, create at least
two gateway logins: one for NLX and one for Nordic.
TT recommends configuring the direct traders’ Member IDs (of their Member, Group, Trader ID) to include the exchange name (e.g., NLXP or NordicP).
- For each login, populate both the Trader ID with the exchange-provided Username.
- For each login, populate both the Operator ID with the exchange-provided SenderSubID value.
- On the NASDAQ_OMX_EU Gateway, populate the Member parameter in the first order session with the NLX Member ID you created in TT User Setup.
- In the first order session, populate the remaining exchange credentials as provided by the exchange.
- Populate the Member parameter in the second order session with the Nordic Member ID you created in TT User Setup.
- Restart the Order Server to ensure that the order sessions log into the exchange.
- In TT User Setup, create a separate TTORD ID
for the NLX and the Nordic gateway logins.
A single TTORD trader cannot map to two separate direct traders on the same gateway. Therefore, each trader must utilize two TTORD logins that are each uniquely mapped to two different direct traders for the same username. This configuration requires X_TRADER 7.17.X and TT User Setup 7.17.X.
- In X_TRADER, create a separate Customer Default
to map to each order session the NASDAQ_OMX_EU Gateway. When populating an
Account Number, ensure that the value is less than ten (10) characters.
When creating the Customer Default, you may view the name of the order session in the OrderGW Alias column as shown in the graphic below.
This step allows traders to easily select the correct order session when configuring the routing rules for each order.
Example: Creating Member IDs
TT recommends configuring the direct traders’ Member IDs (of their Member, Group, Trader ID) to include the exchange name. This will aid the user in easily identifying the order-routing gateway, order session and customer account they wish to trade.
In this example, the administrator has created a separate login for NLX and Nordic as shown below:
This example uses two separate gateway logins: NLXP and NORDICP. The Trader ID (TTG_FIX6 and SETTTS1) have been provided by the exchange and enabled for NLX and Nordic products respectively. In addition, the administrator sets each gateway login’s Operator ID equal to the SenderSubID.
When configuring the NASDAQ_OMX_EU Gateway, the administrator sets the following values:
Example Order Server Sessions
# AccountCode Mapping
After configuring the order sessions, the administrator restarts the Order Server so that the changes can take effect.