Try TT Now

Installation

Before you Install

You must be logged into the gateway server with Administrator rights when performing any of the BrokerTec Gateway installation tasks.

If you previously installed TT software onto your machine, the Gateway software automatically installs to the same location.

Also, depending upon the environment of the machine on which you install the TT Gateway, you may receive several informative or question prompt boxes. If a task discusses such a prompt box, and you do not receive the prompt box, skip to the next step.

During an installation, the BrokerTec Gateway installs the following software packages, which can be uninstalled using the Add or Remove Programs dialog box:

  • BrokerTec Gateway Components (includes standard TT Gateway files and utilities)
  • TT Chron
  • TT Messaging (TTM Only)
  • Guardian
Note

TT Gateways 7.16 and higher contain Guardian/GuardServer 7.9.2. If you are currently using or planning to use TT API, please discuss the licensing implications with your TAM prior to installing the gateway.

Installation and Upgrade Requirements

TT Gateway 7.16 and higher

TT Gateways 7.16 and higher fully support the Window Server 2008 R2 64-bit operating system.

Note

Window Server 2008 R2 64-bit is the only version of Windows Server 2008 supported by TT.

 

You can also install TT Gateways 7.16 on machines running Windows Server 2003.

TT Gateways 7.15 and lower

You can install TT Gateways 7.15.x or lower on machines running Windows Server 2003.

In addition, you can install the following TT Gateways on a machine running Windows Server 2008 R2 Service Pack 1:

  • TT Montreal, CBOE and FIX Gateways 7.13
  • All TT Gateways 7.14 and 7.15

Prior to installing 7.15 or lower on Windows Server 2008, you must be aware of the following caveats and required changes:

  • Migrating to Windows Server 2008: TT does not support upgrading the operating system on an existing TT Gateway server. TT strongly suggests that users perform a clean install of the operating system and the TT Gateway when migrating to Windows Server 2008.
  • Program Files directory: Windows Server 2008 does not allow applications to create files under the Program Files directory.

    If during a command line installation of the TT Gateway, you place the install root in the Program Files directory, you must select a different location for the ttconfig, ttdatfiles and ttlogfiles directories by using the installconfig, installdata and installlog arguments.

  • Event Viewer Errors: Certain TT applications may trigger minor Event Viewer error messages. These errors do not impact gateway behavior. However, users can avoid triggering these messages by starting the Windows Interactive Services Detection prior to install.
  • Console Windows: By default, some console windows triggered by TT Gateways may not display and instead produce an Interactive Service Detection dialog box. Users may run the Interactive Services Detection and switch over to the Windows “Session 0” desktop to view messages displayed from server.
  • Starting Programs: TT Chron may not properly close and/or monitor server programs that are started manually. Users should first start TT Chron and allow it to start the server program per its schedule.
  • Start TT Chron desktop icon: The “Start TT Chron” desktop shortcut may not work unless the user right-clicks on the icon and select “Run as administrator” from the context menu.
  • TTM_BASE_API error: An issue exists where TTM may trigger a TTM_BASE_API error message in the Event Viewer. This is a known issue with TTM and does not impact gateway behavior.
  • User Account Control: You must disable the Windows User Account Control for the TT Gateways to properly function. The User Account Control prevents the gateway from updating files including changes to the aconfig.xml file and updates to the product table.

When upgrading to Version 7.12, you must also work with the Exchange to obtain BO23 enabled user IDs and passwords. For more information on the BO23 broadcast, refer to Market Data Broadcasts.

Installation Methods

BrokerTec Gateways support two types of installation procedures:

  • GUI Interface Installation: Provides dialog boxes that guide the user through the installation process. Recommended when installing the BrokerTec Gateway on a small number of servers.
  • Command Line Installation: Provides command line entries to automate the installation process. Recommended when performing multiple unattended installations on a large number of servers.
Note

You can combine both types of installations.

Depending on the implementation, the command line installation can suppress some or all of the dialog boxes that appear during the GUI install. You can use the command line to automate similar install choices, then run the GUI install to customize unique options.

Warning

Regardless of the installation method, when adding a new TT Gateway flavor to your trading environment, you must restart TT User Setup before the new flavor will appear.

Installing 7.17 or higher for a Multi-Member Configuration

To install BrokerTec Gateway 7.17 or higher for a Multi-Member configuration

  1. Do a clean install. Refer to Installing via the Graphic User Interface.
  2. Configure the Member sections of hostinfo.cfg
  3. Assign the Member values of traders which will be allowed to trade on the multi-member gateway.
  4. If existing traders' Member-Group-Trader IDs do not have a Member configured on the gateway, those traders’ IDs must be updated. Refer to the OM Gateway Migration Guide for information about updating direct trader IDs for multi-member gateways.