Try TT Now

Section: [Global] 7.16.X or lower

Example

In BrokerTec Gateways 7.17 and later, the [Global] section is no longer used. The following example shows this section configured for 7.16.x or lower.

Example [Global] section parameters

[GLOBAL]

Root=SQE1UserPassword=Supersecret

AccessIP=65.244.93.1

AccessPort=24024

TTOs=8

# config values

LogLevel=Normal

ForceAutoAggress=0

ResubmitOnStartup=0

ResubmitOnSessionDown=0

PollingInterval=50

HeartBeatInterval=8

Parameters

BrokerTec implements a naming convention utilizing a root name in the [Global] section to derive the BrokerTec user names. BrokerTec assigns all the users a common root (e.g., Root1) and ensures that all these users share the same password, target IP address, and port. The BrokerTec Gateway can then generate the user names of all the users given the Root Name and the number of TTOs assigned to the Gateway.

The following table lists this section’s parameters and their descriptions.

[Global] section parameters

Parameter

Description

Root

BrokerTec distributes this value and refers to it as the root name. This root name is used to create the BrokerTec user names.

UserPassword

BrokerTec distributes this value and refers to it as the User Password.

AccessIP

Identifies the IP address that the Gateway uses to connect with the Exchange.

AccessPort

Identifies the port that the Gateway uses to connect with the Exchange.

TTOs

The number of TTOs assigned to the BrokerTec Gateway; eight is recommended.

LogLevel

Sets the level of detail that the BrokerTec Gateway provides to its log files. This parameter has three available settings and are listed from the least detailed to the most:

  • Low: This level is the least verbose and logs only required and important messages.
  • Normal: This level logs important and normal messages.
  • Verbose: This level logs all messages.

By default, BrokerTec Gateways install with logging level set to Normal.

SendImmediateFills This parameter is deprecated in Version 7.3.0 and higher.

Instead of sending a fast fill when trades occur, then a confirmed fill at the workup end, this setting enables the customer to get confirmed fills sent immediately upon notification of the trade. Available settings are:

  • 1: This sets the send immediate fills property to On. Confirmed fills are sent immediately upon notification of the trade.
  • 0: This sets the send immediate fills to Off. When trades occur a fast fill is sent, then a confirmed fill is sent at the workup end. This is the default setting.

If this keyword is missing or has an invalid value, the TT Gateway behaves as if it were set to 0.

ForceAutoAggress

Sets a customer sites ability to force auto-aggressive behavior on all orders submitted through a gateway. Available settings are:

  • 1: This sets the auto-aggressive property to On. All orders are sent to the Exchange through auto-aggressive behavior, regardless of how the client submitted their order.
  • 0: This sets the auto-aggressive property to Off. Orders are sent to the Exchange how the client submitted their order.

If this keyword is missing or has an invalid value, the TT Gateway behaves as if it were set to 0.

ResubmitOnStartup

Sets whether the TT Gateway resubmits held orders after the Order Server recovers from a failure. Available settings are:

  • 1: Working orders are automatically put on hold. On startup the orders are resubmitted as active orders.
  • 0: Removes held orders from the Exchange. The order is not resubmitted; rather it puts them on hold status.

If this keyword is missing or has an invalid value, the TT Gateway behaves as if it were set to 0.

For information on the dynamic between the Order Server connection and traders’ orders at BrokerTec, refer to Connection Failure and Recovery.

ResubmitOnSessionDown

After a TTO fails and BrokerTec puts its orders on hold, sets that TTO to resubmit those held orders as active when it reconnects to the Exchange. Available settings are:

  • 1: When a TTO fails, that TTO resubmits the orders when it reconnects.
  • 0: Removes held orders from the Exchange. The order is not resubmitted; rather it puts them on hold status.

If this keyword is missing or has an invalid value, the TT Gateway behaves as if it were set to 0.

For information on the dynamic between the Order Server connection and traders’ orders at BrokerTec, refer to Connection Failure and Recovery.

HeartbeatInterval

sets the maximum amount of time, in seconds, between heartbeats before the Exchange logs out the Order Server (TTO) connection. To maintain connectivity, the BrokerTec Gateway sends heartbeats to the Exchange at regular intervals.

By default, the value is set to 8.

PollingInterval This parameter is only available in BrokerTec Gateways Version 7.2.3.19 and higher.

Set the length of time, in N milliseconds, the Gateway waits before requesting new data from the Exchange after receiving a “no new broadcast” message. The TT Gateway consistently requests data from the Exchange. If the Exchange responds with new data, the Gateway continues to request and receive updates. However, if the Exchange sends a message showing that there is no new data available, the Gateway will wait N milliseconds before sending a new request.

By default, this parameter is set to 50. TT recommends referencing the hostinfo.cfg_master file for the appropriate default value.

If the parameter is missing or contains an invalid value, the Gateway behaves as if set to 1.

The following considerations can assist your TAM in changing this parameter, if needed. Only change this parameter if told to do so by a TAM or TT personnel.

Setting to a low value (i.e., 50 milliseconds or less), can result in loss of data and disconnection caused by a buffer overflow on the Exchange end.

Setting to a higher value (i.e., 50 milliseconds or more) can result in latency issues caused by the Order Server polling the Exchange interface too aggressively.

Warning

Do not alter this parameter unless told by a member of TT to do so.