Try TT Now

Configuring the Order Server and Order Routers

Section: [OrderServerSession_#]

The Order Server uses the configuration settings in this section to maintain an order session. For each session, you must configure an Order Router using the [OrderServerSession_#] section. Additional sections configure an Order Router on the BVMF Gateway to host multiple firm memberships.

You must assign each section a unique name using the # part of the name. For example, if you have two sections in your hostinfo.cfg, you could simply name them:

  • [OrderServerSession_1]
  • [OrderServerSession_2]

Whenever a trader submits an order, that trader’s Member ID determines which order session carries the order. The Member ID maps to the order session’s member parameter. For additional considerations in determining order sessions based upon the Member ID, refer to Order Router Selection.

For Order Server configuration details, refer to Configuring the Order Server and Order Routers.

Adding [OrderServerSession_#] sections

Warning

You must cancel all working orders before altering or removing any EntryPoint session information. Failure to do so can result in orders becoming lost or deleted from the BVMF Gateway.

If you need to configure additional order sessions, for each session you must:

  • Add a [OrderServerSession_#] section with a unique set of connection information.
  • Include the sessionId, ExchangeIP, and ExchangePort.

To add a new [OrderServerSession_#] section:

  1. Open hostinfo.cfg.
  2. Add the new [OrderServerSession_#] section.
  3. Add all new trader login IDs to TT User Setup 7.4.2.
  4. Verify that the Price Server is running. If it is not running, start it. Refer to
  5. Stop and restart the Order Server on the BVMF Gateway.
  6. Log in to Guardian as an Administrator and, using the View Status function, verify that an Order Router appears listing the new connection.

Maximum Supported Order Sessions

TT currently supports up to 100 separate order sessions on each BVMF Gateway 7.16. Internal testing shows that this amount of order sessions supports the optimal performance during continuous operation and periods of heavy order entry.

TT recommends users work with their Technical Account Manager (TAM) to accurately load balance traders across multiple order sessions.

Order Session Identification

TT Gateways 7.16 and higher contain an enhancement that displays the exchange credential used to route all orders and fills through the exchange. This includes all order modifications and exchange rejects but does not include order actions on Hold orders and position reserve orders.

Currently, this value is available in the following locations:

  • Audit logs: appears in the ExchangeCredentials column
  • Order Server logfile
  • FIX Adapter 7.8: via Tag 18216 (ExchCred)
Note

The exchange credential will be available in future versions of other TT client applications.

To provide users a way to identify which order session routed a particular order on a BVMF Gateway, the order session is identified by a concatenation of BVMF’s Firm ID, EntryPoint Session ID, and SenderCompId, which is configured in hostinfo.cfg as the Firm, sessionId, and ExchangeCompany. The session identification appears on orders and fills for all order actions (add, modify, cancel) routed to the exchange. If the gateway rejects an order action, the session is not identified.

Configuring Order Sessions

Although the BVMF Gateway uses Order Routers, they run as threads within the Order Server and not as separate processes on the BVMF Gateway. You must configure each Order Router’s connection to the exchange as an order session in hostinfo.cfg.

BVMF distinguishes between order actions entered by DMA traders and order actions entered by Desk Traders. The exchange also requires the counterparty code on all order actions to identify the Entering Firm. To configure the BVMF Gateway to support these exchange PUMA requirements, configure the parameters in the Order Router section.

Tip

You can map multiple memberships to the same Order Router. If you expect to generate a high volume of traders, TT recommends that you configure multiple [OrderServerSession_#] sections, each with a unique set of information (obtained from BVMF).

On a BVMF Gateway:

  • ttchron.ini does not contain an Order Router section.
  • Each order session must have its own section in the hostinfo.cfg file called [OrderServerSession_#]. This section configures the Order Router that hosts the session.
  • Guardian displays individual Order Routers and their status for a specified BVMF Gateway when you use Guardian’s administrative function called View Status.

To configure the [OrderServerSession_#] section:

  1. Open hostinfo.cfg in a text editor (e.g., Notepad).
  2. Configure the following parameters.
    [OrderServerSession_#] section parameters
    ParameterDescription
    [OrderServerSession_#]

    This is the section title, where # uniquely identifies the Order Router.

    Member

    Sets how the BVMF Gateway selects an Order Router for either a Desk Trader session or DMA Trader session. This value is also called the Member ID. Because each Member ID must be unique on a BVMF Gateway, each [OrderServerSession_#] section must be configured with a unique Member parameter. The brokerage firm assigns Member IDs to each Desk Trader and DMA Trader associated with the firm, and defines the IDs in the TT system using TT User Setup 7.4.2. The Member value is not sent to the exchange for any order actions.

    Enter up to 7 alphanumeric characters. This parameter should be set to the same Member ID value defined in TT User Setup for the Desk or DMA Trader using this session. No special characters are allowed and this parameter is not case sensitive. This is a required parameter.

    Warning

    If there is a duplicate Member parameter configured on a multi-session BVMF Gateway, the Order Server will not start.

    PasswordSets the password for the session. Enter the case-sensitive password provided by BVMF for the sessionId configured in this section. The password appears as plain text in this field.

    If you receive a password as part of your exchange credentials provided by BVMF, then this parameter is required. Contact BVMF if you do not receive a password as part of your exchange credentials. If the exchange does not require a password and this parameter is not configured, the Order Server still sends a session logon attempt to the EntryPoint server at startup.

    ExchangeIP

    BVMF provides two IP addresses as part of their exchange credentials: one for their primary network, and one for their disaster recovery network. Each IP address is for a BVMF EntryPoint FIX Server that traders connect to for sending orders to the exchange host. BVMF sends this value as the “IP” in their exchange credentials. This is a required parameter.

    ExchangePort

    This is the port on the BVMF EntryPoint FIX Server to which the TT Gateway connects. If the exchange provides two port numbers, BVMF assigns each port to a specific IP address. If this is the case, then you must use the appropriate number for each of the port parameters. BVMF sends this value as the “port” in their exchange credentials. This is a required parameter.

    sessionIdSets the FIX session ID for the order routing connection to the Entrypoint system. The BVMF Gateway sends this value as SenderCompID in the FIX messages sent to the Entrypoint server. Desk Traders and DMA traders cannot share the same session ID, so the Member parameter for this session is set for either a Desk Trader or DMA Trader. A session remains active based on the heartbeat message timer programmed on the BVMF Gateway.

    Enter the session ID provided by the exchange, which sets permissions per product for each ID. In the exchange credentials, BVMF provides the session ID as the “SenderComp ID.” This is a required parameter.

    ExchangeCompanySets the value of FIX tag TargetComp ID populated by the BVMF Gateway for each order action sent to the EntryPoint server. Enter the value provided by the exchange for BVMF Gateways connecting to the BVMF Puma platform. In the exchange credentials, BVMF provides this value as the “TargetComp ID.” This is a required parameter.
    FirmSets the Firm ID based on the code used for identifying the Desk Trader’s brokerage firm or “counterparty”(e.g., Firm=180). The code is defined by the brokerage community and is made available to the public. Brokerage firm codes can be obtained from the BVMF website. The BVMF Gateway uses the Firm parameter to identify the Entering Firm in the FIX messages for order actions sent to the EntryPoint server. This is a required parameter.
    SenderLocation

    Sets whether an order is entered by a Desk trader or DMA Trader for a particular session by defining the location of the EntryPoint session connection. You must set this parameter to one of the following values:

    • BVMF This value configures the gateway to determine that an order is entered by a Desk Trader session.
    • A three-character exchange-assigned code (e.g., TTN). This value configures the gateway to determine that an order is entered by a DMA trader via a DMA trader session.

    This is a required parameter.

    InternationalDMAProviderSets whether the gateway appends the "External Market Participant" value of “8” to FIX Tag 529-OrderRestrictions. The exchange requires Tag 529 on all order actions. Tag 529 contains multiple values in a space delimited format. Example of maximum options: 529=1 7 8. However, only option “8” is configurable on the gateway based on the InternationalDMAProvider setting. Valid values are Y or N where:
    • Y configures the gateway to populate tag 529=8, which indicates that order actions were sent by an international DMA provider (e.g., TTNET).
    • N configures the gateway to omit option “8” from Tag 529, which indicates that order actions were sent by a local DMA provider.

    For the other options, the Order Server is programmed to determine if order actions were sent by an Automated Training System (529=1) or another exchange (529=7), and populate FIX Tag 529 accordingly. For example, an order with Account Type=A2 would append “7” to FIX Tag 529.

    This is a required parameter.

    GiveupAccounts

    Sets the exchange-assigned identifier for a Give Up relationship between two firms. Setting this parameter also defines whether orders that carry the specified account type have a Give Up account. If X_TRADER® submits an order with the specified account type, the BVMF Gateway sends a Give Up firm. Mapping is taken care of by BVMF’s clearing firm.

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

Example: [OrderServerSession_#]

The following example sections illustrate:

  • A hostinfo.cfg configured for one membership.
  • A hostinfo.cfg configured for two memberships: one for a DMA Trader and one for a Desk Trader.
Example [OrderServerSession_#] sections
Example HostInfo.cfg File - One MemberExample HostInfo.cfg File - Two Members

[OrderServerSession_1]

Member=TR409

Password=12345678

ExchangeIP=10.140.120.45

ExchangePort=11092

sessionId=TRTT14

ExchangeCompany=BVMF

Firm=188

SenderLocation=TTN

InternationalDMAProvider=N

[OrderServerSession_1]

Member=TR409

Password=12345678

ExchangeIP=10.140.120.45

ExchangePort=11092

sessionId=TRTT14

ExchangeCompany=BVMF

Firm=188

SenderLocation=TTN

InternationalDMAProvider=N

[OrderServerSession_2]

Member=TR408

Password=12345678

ExchangeIP=10.140.120.45

ExchangePort=11092

sessionId=TRTT15

ExchangeCompany=BVMF

Firm=188

SenderLocation=BVMF

InternationalDMAProvider=N

Example: [OrderServerSession_1]

The following example shows an order router configured for a DMA Trader.

Example

[OrderServerSession_1]

ExchangeIP=10.2.60.80

ExchangePort=61000

#ExchangeIP=10.2.60.81

#ExchangePort=61001

sessionId=TRTT14

Member=DEF456

ExchangeCompany=BVMF

Firm=188

SenderLocation=TTN

InternationalDMAProvider=N

Password=12345678

Multi-Member Order Routers

To configure an Order Router to support multiple memberships:

  • The customer must contact BVMF and have the exchange enable this functionality.
  • For all multi-member Order Routers, BVMF must distribute the appropriate SessionId and FirmID values for use by each order session.
  • The BVMF exchange maps traders according to the SessionID and the TT Trader ID. To complete a multi-member setup, you may have to furnish this data (TT Trader IDs) to BVMF.
  • To set up the multi-member Order Router (i.e., the [OrderServerSession_#] section), use the SessionID and Member ID of one of the memberships that are assigned to the multi-member Order Router.

There is no additional change to trader setup (i.e., risk parameter configuration). All traders must have their Trader IDs set up and their risk settings defined using TT User Setup 7.4.2.

Order Router Selection

Whenever it receives an order, the Order Server looks for an exact match of the trader’s Member ID and the Member parameter value configured in the [OrderServerSession_#] section. Again, each session is hosted by an Order Router that runs as a thread on the Order Server.

If you have traders who use a Member ID (assigned by the firm) that does not match the Member parameter of an order session in the BVMF Gateway’s hostinfo.cfg file, their orders will be rejected by the gateway.

Desk Trader Sessions

When the Member parameter selects a session for a Desk Trader, the trader ID (i.e., the “T” in MGT) sent in FIX Tag 448-PartyID by the BVMF Gateway is the Desk Trader ID provided by the exchange and configured in TT User Setup 7.4.2 as a TTORD or Direct Trader ID. The gateway sends the TTORD “T” first, if it’s available. If it’s not, the gateway sends the Direct Trader “T” in FIX Tag 448-PartyID. The BVMF Gateway identifies this session as a Desk Trader’s session based on the parameter SenderLocation.

DMA Trader Sessions

When the Member parameter selects a session for a DMA Trader, the trader ID (i.e., the “T” in MGT) sent in FIX Tag 448-PartyID by the BVMF Gateway is the ID defined by the brokerage firm and configured as the Username in TT User Setup 7.4.2. The BVMF Gateway identifies this session as a DMA Trader’s session based on the parameter SenderLocation.

If FIX Adapter sends a SenderSubID value, then the BVMF Gateway populates this value in FIX Tag 448-PartyID instead of the TT User Setup Username, and sends it to the EntryPoint server.

Order Book Sharing

Desk Traders and DMA Traders associated with the same membership can share an order book. The trader IDs assigned by the exchange for each Desk Trader and DMA trader are unique, but the trader IDs can be mapped to the same member ID in order to share an order book.

For example, a Desk Trader with a Member-Group-Trader (MGT) ID of “DEF456 001 ALZ” can share an order book with a DMA Trader assigned an MGT of “DEF456 001 TTN”. Both memberships can have the same or different Firm IDs configured in hostinfo.cfg for separate order routers. As long as they are mapped to the same Member ID, they will be able to share an order book.

Order Server Startup Parameters

You can use command line parameters when starting up the Order Server. You can use these options in a command window, ttchron.ini, and in the Services dialog box. The following is an example of using the -r parameter.

Currently, the BVMF Gateway supports using the following parameters to start the Order Server:

Command Line Parameter
ParameterDescription
-r

This tells the Order Server to reset the sequence numbers for specific EntryPoint Order Sessions on the BVMF Gateway.

  • To reset specific EntryPoint sessions, use the format: OrderServer.exe -r <MemberID1> <MemberID2>

    Where: <MemberID1> is based on the Member parameter setting in hostinfo.cfg.

  • To reset all sessions, use the format: OrderServer.exe -r all