Try TT Now

Configuration Files for 7.17.1 or Higher

Configuration Files

After installing the Synthetic SE software, you must configure the tt_sse.ini file. You must configure this file for every Synthetic SE Server machine in your network, regardless of which type of network deployment you choose. Additionally, you must configure the rollover settings for the Synthetic SE Fill Server, which are located in the aconfig_local.xml file.

If you deploy Synthetic SE in a multiple-multicast network, you must also configure the following files:

  • ttminclude.cfg, which defines multicast subjects for the TT Gateway Price Servers to which Synthetic SE connects in a multiple-multicast network
  • ttmd.cfg, which controls the TTM Communication Daemon configuration and includes the ttminclude.cfg file.

About the tt_sse.ini File

Synthetic SE uses the tt_sse.ini file, located in <root drive>:ttconfig, to determine how it connects to TT Gateways. This file contains a series of sections that specify the configuration information for each TT Gateway connection.

tt_sse.ini Parameters

The following table describes the parameters used in the tt_sse.ini file.

tt_sse.ini parameters

Parameter

Description

[SEServer]

Marks the beginning of the SE server section.

EnableDynamicConnections

Enables or disables support for dynamic connections:

  • Y (default): Synthetic SE logs into TT Gateways when a user connects to it.
  • N: Synthetic SE logs into TT Gateways during its initialization.

[Synthetic Engine]

Marks the beginning of the synthetic engine section.

RequestUnsolicitedEvents

Enables or disables support for order staging and the X_TRADER Avoid orders that cross configuration option. Valid values include:

  • Y:
    • Enables support for order staging
    • Enables support for the X_TRADER Avoid orders that cross configuration option
    • Enables support for OCO (one cancels other) orders (requires Synthetic SE 7.17.20 and X_TRADER 7.17.20 or higher)
  • N (default):
    • Disables support for order staging
    • Disables support for the X_TRADER Avoid orders that cross configuration option
    • Disables support for OCO (one cancels other) orders
CheckMaxOrderSizeForSyntheticOrders

(Optional) Specifies whether Synthetic SE should reject parent synthetic slicer orders when the parent order quantity exceeds the X_TRADER Max Order Quantity setting.

Possible values include Y and N (default).

Note

Enabling this setting requires traders to use X_TRADER 7.17.20 or higher. If the setting is enabled, Synthetic SE will reject all synthetic slicer orders from earlier X_TRADER versions.

MaxTicksAdverseMarket

MaxTicksBeneficialMarket

(Valid for 7.17.50 and higher)

Specifies the range of an acceptable price when SSE submits slice orders of parent synthetic slicer orders.

If these options are set when a multi-child Synthetic SE order (volume slicer, volume duration, time slicer, time duration, iceberg) is submitted, Synthetic SE takes a snapshot of the current market. Note that if a start time was specified on the parent, then the snapshot will not be taken until the start time.

Before sending a child order of any multi-child synthetic order, Synthetic SE compares the price of the child order with the snapshot price. Specifically, Synthetic SE calculates an offset as follows:

  • For a buy: Offset = (New Order Price - Original Snapshot price)
  • For a sell: Offset = (-1) * (New Order Price - Original Snapshot price)

If (-MaxTicksBeneficialMarket <= Offset <= MaxTicksAdverseMarket) is false, the parent synthetic order is put on hold.

[SSE]

Marks the beginning of the SSE section.

RiskPLChecking

Enables or disables support for P&L risk checking for child orders of staged orders.

  • 0: Disables P&L risk checking for child orders of staged orders.
  • 1: Enables P&L risk checking for child orders of staged orders (default when RequestUnsolicitedEvents=Y).
Note

If this configuration option is set to 0, P&L risk checking will not be performed even if an administrator configures a user with P&L limits in TT User Setup. However, if users are not configured for P&L risk checking in TT User Setup, TT recommends setting this configuration option to 0 for performance reasons.

If you disable P&L risk checking on Synthetic SE and later map a user to Synthetic SE which is configured to be P&L risk checked in TT User Setup, you should re-enable P&L risk checking on Synthetic SE. Failure to re-enable P&L risk checking on Synthetic SE in this case will result in this user not being P&L risk checked when submitting OCOs and child orders of staged orders.

[gw-Exchange-Flavor]

Marks the beginning of the configuration section for the specified TT Gateway (e.g. gw-CME-A).

Note

If the file contains both a [market-] section and a [gw-] section for the same market, the parameters in the [gw-] section override those in the [market-] section for that gateway.

Member

Group

Trader

Provides the Member, Group, and Trader IDs (MGTs) for Synthetic SE to use when logging in to the specified TT Gateway.

  • Not needed if the EnableDynamicConnections parameter is Y.
  • Required if the EnableDynamicConnections parameter is N.

For more information, refer to the section called Determining TT Gateway Login Credentials with Dynamic Connections Disabled.

Note

For TTSIM Gateways, you should not use TTADM/XXX/MGR credentials.

Primary

(Optional) Identifies the primary Synthetic SE in an environment with more than one Synthetic SE for this TT Gateway. In a multiple Synthetic SE environment, the client application (i.e. X_TRADER) routes synthetic orders through the Synthetic SE that enables this parameter.

Possible values include Y and N (default).

For more information about this parameter, see Multiple Synthetic SE Servers for a TT Gateway.

Price_Subscription_Gateway

(Optional) Sets Price Server mapping. By setting this parameter equal to the Exchange-Flavor, or to a comma-separated list of them, to which you want to map, Synthetic SE routes price subscriptions to that Exchange-Flavor. In the following sample configuration, Synthetic SE routes the price subscriptions to CME through CME-A.

[gw-CME]

Member=TTORDPM

Group=XXX

Trader=MGR

Price_Subscription_Gateway=CME-A

Primary=Y

[market-MarketName]

(Used only when EnableDynamicConnections=Y) Marks the beginning of the configuration section for the specified market (e.g. market-CME).

Note

If the file contains both a [market-] section and a [gw-] section for the same market, the parameters in the [gw-] section override those in the [market-] section for that gateway.

Primary

(Optional) Identifies the primary Synthetic SE in an environment with more than one Synthetic SE for this market. In a multiple Synthetic SE environment, the client application (i.e. X_TRADER) routes synthetic orders through the Synthetic SE that enables this parameter.

Possible values include Y and N (default).

For more information about this parameter, see Multiple Synthetic SE Servers for a TT Gateway.

Price_Subscription_Gateway

(Optional) Sets Price Server mapping. By setting this parameter equal to the Exchange-Flavor to which you want to map, Synthetic SE routes price subscriptions to that Exchange-Flavor. In the following sample configuration, Synthetic SE routes the price subscriptions to CME through CME-A.

[market-CME]

Price_Subscription_Gateway=CME-A

Primary=Y

Multiple Synthetic SE Servers for a TT Gateway

You can use multiple Synthetic SE Servers to support a single TT Gateway to create a more robust environment. For example, you could distribute traders across multiple TT Synthetic SE Servers. You might also want to allow traders to log into multiple Synthetic SE Servers so that they can still access an Synthetic SE Server in the event that one fails.

If you want to allow a trader to log into multiple Synthetic SE Servers that are all configured to connect to the same TT Gateway(s), it is important that one of the Synthetic SE's indicate to client applications, such as X_TRADER, that it is the primary one to be used for a given TT Gateway.

Example: Configuring Multiple Synthetic SE Servers for Failover

In the following example, you configure one Synthetic SE Server (SSE-A) as the primary destination for client applications, such as X_TRADER, to connect to both Synthetic SE Servers to route orders. Then, you configure another Synthetic SE Server (SSE-B) to serve as the secondary, or backup, destination for client applications to use if SSE-A becomes unavailable.

Example tt_sse.ini (for SSE-A)

[gw-ICE_IPE]

Primary=Y

Example tt_sse.ini (for SSE-B)

[gw-ICE_IPE]

Primary=N

In this scenario, if both Synthetic SE Servers are up and the client application is connected to both, all synthetic ICE_IPE orders will be routed to the one designated as the primary (SSE-A). If the primary Synthetic SE Server becomes unavailable, the client application will submit all synthetic ICE_IPE orders to the backup Synthetic SE Server (SSE-B).

Note

Client applications randomly choose from multiple Synthetic SE Servers associated with a TT Gateway in the following circumstances:

  • Multiple Synthetic SE Servers enable the Primary parameter.
  • No Synthetic SE Servers enable the Primary parameter.
  • When three or more Synthetic SE Servers support the TT Gateway and the primary Synthetic SE Server becomes unavailable.
  • Synthetic SE always synthesizes the stop / if-touched portion of a trailing stop / if-touched order.