Try TT Now

Configuring Order Sessions

 

Overview

You must configure and establish a unique connection for each order session:

  • For each Member configured in the Hostinfo.cfg file, configure at least one FIX session for order and real-time fills processing.
  • TTORDs mapped to the direct trader (Member) can perform order actions. However, orders entered through a FIX order session can be modified or canceled only through the same FIX order session.
  • For OTC reporting and clearing, configure a low-frequency or low-frequency light derivatives ETI session.

For information related to configuring multiple order sessions, refer to Configuring Multiple Sessions.

Order Routing

GMEX Gateway order routing is based on the Member portion of the direct trader's member-Group-Trader ID (MGT) configured in TT User Setup. This is the same value used for the Member parameter configured in Hostinfo.cfg.

Each FIX order session is selected based on the Member value of the user placing the order.

Configuring an Order Session

Although the GMEX Gateway uses Order Routers, they run as threads within the Order Server and not as separate processes on the gateway. To configure each Order Router’s TCP connection to the exchange as an order session in Hostinfo.cfg, you must configure the parameters in the [OrderSession_1] section.

To configure an order session

  1. Open <root drive:>ttconfigHostinfo.cfg in a text editor (e.g., Notepad).
  2. Configure the following parameters in the [OrderSession_1] section:
    [OrderSession_trade#] section parameters

    Parameter

    Description

    [OrderSession_1]

    This is the section heading for a single order session. Subsequent order sessions can be numbered sequentially (e.g., [OrderSession_2], [OrderSession_3], etc.).

    ExchangePrimaryIP

    Sets the IP address that the GMEX Gateway uses to connect this order session to the exchange. The exchange assigns this value.

    ExchangePort

    Sets the port that the GMEX Gateway uses to connect to the exchange. The exchange assigns this value.

    ReconnectionInterval

    Defines the length of time in seconds the Order Server will attempt to reconnect with the exchange host in the event of a disconnect. The minimum recommended value to enter is “15.” By default, this parameter is set to 35.

    GatewayCompany

    Identifies the FIX Order ID of the firm sending messages from the GMEX Gateway. This field populates the value of Tag 49 (SenderCompID) in all outbound messages for this session. Enter the FIX Trade Gateway ID provided by the exchange.

    HeartbeatInterval

    Sets the frequency, in seconds, that the Order Server sends a heartbeat to the exchange and expects Heartbeats from the exchange. HeartbeatInterval is established as part of Logon. In order to maintain a connection, the Order Server must send and receive a heartbeat to and from the exchange at the HeartbeatInterval specified. Setting HeartbeatInterval to a value less than 1 will result in the parameter using the default value.By default, the GMEX Gateway installs with this parameter set to 30.

    ExchangeCompany

    Identifies the name of the exchange host that sends messages to the GMEX Gateway. This field supplies the value of the Tag 56 (TargetCompID) in all inbound messages to the GMEX Gateway. Enter the Target CompID provided by the exchange.

    Member

    Identifies the client’s Member login for routing orders through this session. Each [Order_Session_#] section must have a unique Member value.

    Enter the exchanged-provided member ID. This value must be the same as the member ID used for configuring the corresponding FIX session.
  3. Add all new trader login IDs using TT User Setup.
  4. Verify that the Price Server is running. If it is not running, start it. Refer to Testing Price Server Setup. Stop and restart the Order Server on the GMEX Gateway. Log in to Guardian as an Administrator and, using the View Status function, verify that an Order Router appears listing the new connection.

Example: Order Session

Example Hostinfo.cfg File configured with order and FIXML sessions

[OrderSession_1]

ExchangePrimaryIP=172.123.4.567

ExchangePort=16540

ReconnectionInterval=35

GatewayCompany=T_TTECH1

HeartbeatInterval=30

ExchangeCompany=T-FORUM

Member=TTGXV

Configuring an ETI Session

To configure the gateway for OTC reporting and receiving and sending Trade Confirmations, configure an ETI session using the parameters in the [ETIRouterSession_1] section in Hostinfo.cfg. Before you begin, consider the following:

    • The ETI session must be either LF or LF light.
    • The session must be assigned to the customer's Eurex membership and have permission to approve trades.
    • The Operator ID must be a valid exchange User ID mapped to an exchange MGT, and must be assigned to the customer's Eurex membership with permission to approve trades.

To configure an ETI session

  1. Open <root drive:>ttconfigHostinfo.cfg in a text editor (e.g., Notepad).
  2. Configure the following parameters in the [ETIRouterSession_1] section:

    Parameter

    Description

    [ETIRouterSession_1]

    Sets the name of the ETI order session. The session name is a unique, user-defined value.

     
    Warning

    If the ETI Router session names are not unique, the ETI Router will not route orders through the ETI interface.

    Member

    Sets the synthetic TT member ID used for routing orders within the TT system. Configure a single member per session to assign the session to an exchange membership (business unit). The member value must be defined as part of a valid Member-Group-Trader ID in TT User Setup.

    Note

    TT requires configuring one LF session per synthetic Member.

    BusinessUnit Sets the exchange member credential for routing and managing orders. This value is provided by Eurex as part of their exchange credentials. Eurex assigns session IDs based on exchange membership (i.e., business unit for T7). Configure one BusinessUnit parameter per [ETIRouterSession_1] section. TT recommends configuring one LF session per BusinessUnit.
    SessionId Sets the ETI session ID for routing orders to the exchange. Enter the value provided by Eurex as part of their exchange credentials. Eurex provides low-frequency (LF) session IDs for reporting OTC trades. Add low-frequency sessions (e.g., [ETIRouterSession_2]) based on the projected throughput of the gateway. Current TPS (transaction-per-second) figures are 50 for LF sessions. Only one SessionId parameter can be configured per [ETIRouterSession_1] section in hostinfo.cfg.
    SessionPassword The exchange-provided session ID password. Configure one password per session.
    NetworkInterfaceFeed1

    If you do not use the default NIC IP address and port as determined by the binding order on your machine, this parameter sets the ETI Router's local IP address to route orders to an application gateway. Note the following when configuring NetworkInterfaceFeed1:

    • This parameter is not required if your server only uses one NIC card.
    • This parameter is optional if your machine uses a dual-NIC card.
    • This parameter is required if your machine has more than one NIC card and the default NIC does not have a route to the exchange (e.g., it faces your internal network).

    By default, this parameter is blank and the GMEX Gateway uses the default NIC IP address and port.

    NetworkInterfaceFeed2

    If you do not use the default NIC IP address and port, this parameter sets the ETI Router's local IP address to route orders to an application gateway. Note the following when configuring NetworkInterfaceFeed2:

    • This parameter is not required if your server only uses one NIC card.
    • This parameter is optional if your machine uses a dual-NIC card.
    • This parameter is required if your machine has more than one NIC and the default NIC does not have a route to the exchange (e.g., it faces your internal network).

    By default, this parameter is blank and the GMEX Gateway uses the default NIC IP address and port.

    ConnectionGw1 Sets the exchange-provided IP Address of a connection gateway that dynamically provides IP Addresses to an application gateway. The ETI Router receives an IP Address from the connection gateway and automatically connects to an application gateway in the Eurex network. Eurex provides two connection gateway IP Addresses as part of their exchange credentials. Configure ConnectionGW1 using the first connection gateway IP Address provided by Eurex. At least one connection gateway IP Address must be configured on the GMEX Gateway.

    TT recommends configuring both parameters (ConnectionGW1 and ConnectionGW2) on the ETI Router in order to support exchange-failover of the connection gateways. If one connection gateway loses connectivity or is shutdown, the ETI Router automatically routes all orders via the second configured connection gateway.

    ConnectionGw2 Sets the exchange-provided IP Address of the second connection gateway to connect to per session.

    Both connection gateway parameters are required to support exchange-failover for ETI. If both ConnectionGW1 and ConnectionGW2 parameters are configured, the ETI Router routes all orders via the second connection gateway if the first one is shutdown or loses connectivity.

    port Sets the port address where the ETI Router sends/receives orders and confirmations to/from the application gateway. The default value is 19008.
    LogSendReceive Sets whether the gateway logs messages to the send-receive log. Valid values are 1 and 0, where:
    • 1: enables logging
    • 0: disables logging

    The default value is 0.

    OperatorID Enter an Operator ID that is a valid User ID assigned to the customer's Eurex membership with permission to approve trades. The Operator ID also must be mapped to an exchange MGT.
    OperatorPassword

    Enter the password associated with the Eurex member's User ID (Operator ID).

    GMEXExecutingFirm

    Identifies the firm reporting and confirming OTC trades. Enter the value provided by the exchange. Commented-out by default.

  3. Add all new trader login IDs using TT User Setup.
  4. Verify that the Price Server is running. If it is not running, start it. Refer to Testing Price Server Setup. Stop and restart the Order Server on the GMEX Gateway. Log in to Guardian as an Administrator and, using the View Status function, verify that an Order Router appears listing the new connection.

Example: ETI Session

Example A single ETI router session for one exchange membership (business unit)

[ETIRouterSession_1]

Member=TTGXV

BusinessUnit=TTGXV

SessionId=92501234

SessionPassword=tLu&123sabc

NetworkInterfaceFeed1=172.17.10.67

NetworkInterfaceFeed2=172.17.10.68

ConnectionGw1=193.029.089.001

ConnectionGw2=193.029.089.002

port=19008

OperatorID=10950

OperatorPassword=Eurex123

#GMEXExecutingFirm=GCBTT