Try TT Now

NYSE Liffe Gateway

Example Case Studies: Order Session Configuration

Overview

The following represents a sample case study in which the administrator performs the following tasks:

  1. Enabling two traders to trade the Amsterdam CAQ40 Equity products by sharing an ITM (14E) but not sharing an Order Book.
  2. Enabling the same two traders access to the London FTSE-100 Equity products by sharing a second ITM (15E) but not sharing an Order Book.
  3. Adding a third trader to trade the London Euribor Financial product when the first ITM (14E) is enabled for both clearing environments and exchanges.

Case Study 1: Sharing an ITM

Firm ABC has two traders who trade the CAQ40, an equity product, on the Amsterdam Exchange. The CAQ40 clears through the Equity clearing environment. They would like to share a single ITM, (in this case, 14E) but not share an Order Book.

The administrator configures the following in TT User Setup:

Since both users share a Member ID, they will also share Order Sessions and ITMs that are mapped in the hostinfo.cfg file. However, since the Group IDs are different, they will not share an Order Book.

To complete this configuration, the administrator configures the following in the hostinfo.cfg on the TT Gateway:

Example Hostinfo.cfg for two traders mapped to the same ITM

[OrderServerSession_One]

SenderCompId=14E

SenderSubId=SSS

Member=ABC

PrimaryAddress=10.1.2.3

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=EQT

Exchanges=Amsterdam

AccountCodeMapping=DefaultMapping

Case Study 2: Sharing a second ITM

Firm ABC would like the same two traders to also access the London FTSE-100 Equity products by sharing a second ITM (15E) but not sharing an Order Book.

The TT User Setup configuration remains the same:

In the hostinfo.cfg file, the administrator creates a second Order Session with different values as highlighted in Blue below:

Example Hostinfo.cfg for two traders mapped to multiple ITMs

[OrderServerSession_One]

SenderCompId=14E

SenderSubId=SSS

Member=ABC

PrimaryAddress=10.1.2.3

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=EQT

Exchanges=Amsterdam

AccountCodeMapping=DefaultMapping

[OrderServerSession_Two]

SenderCompId=15E

SenderSubId=SSE

Member=ABC

PrimaryAddress=10.2.3.4

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=EQT

Exchanges=London

AccountCodeMapping=DefaultMapping

In this scenario, the Member parameter remains the same in both Order Sessions. When either trader submits an order for the Amsterdam Equity products, it routes through [OrderServerSession_One] via the ITM set by the SenderCompID (14E) and the unique IP address (10.1.2.3).

In addition, orders for the London Equity products route through [OrderServerSession_Two] via the ITM (15E) and unique IP address (10.2.3.4).

Case Study 3: Adding a trader

Firm ABC will add a third trader to trade the London Euribor Financial product. In this case, the first ITM (14E) is enabled by the exchange for both clearing environments. To facilitate this, the exchange has provided a second IP address for the ITM to access the Financials clearing environment.

The administrator adds the third trader in TT User Setup:

To complete this configuration, the administrator creates a third Order Session with the same ITM as [OrderServerSession_One] but different values as highlighted in Blue below:

Example Hostinfo.cfg when the ITM is configured for both clearing environments.

[OrderServerSession_One]

SenderCompId=14E

SenderSubId=SSS

Member=ABC

PrimaryAddress=10.1.2.3

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=EQT

Exchanges=Amsterdam

AccountCodeMapping=DefaultMapping

[OrderServerSession_Two]

SenderCompId=15E

SenderSubId=SSE

Member=ABC

PrimaryAddress=10.2.3.4

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=EQT

Exchanges=London

AccountCodeMapping=DefaultMapping

[OrderServerSession_Three]

SenderCompId=14E

SenderSubId=SSS

Member=DEF

PrimaryAddress=10.3.4.5

PrimaryPort=8008

#NetworkInterfaceFeed=

Environment=FIN

Exchanges=London

AccountCodeMapping=DefaultMapping

In this scenario, the new Order Session uses the same SenderCompID (14E) as [OrderServerSession_One] but different values for the Member, PrimaryAddress, Environment and Exchanges parameters.