Try TT Now

Preparing to Upgrade

Pre-upgrade Checklist

Note

TT recommends installing TT Update on the TT User Setup client. This eliminates the need to manually upgrade the TT User Setup client, and ensures that the client version always matches the TT User Setup server version.

Prior to upgrading, refer to the following Pre-upgrade Checklist:

Pre-upgrade Checklist
CompleteTask

Read the TT User Setup User Guide and/or take the TT User Setup Computer Based Training Course to familiarize yourself with the software.

Determine if you'll need to set up tiered administration. Logging into TT User Setup provides access to all trader and risk data within the environment. As such, you may choose to not upgrade some risk administrator's TT User Setup clients until you set them up as group administrators. For more information on setting up tiered administration, ask your TAM about accessing the TT User Setup webinar (a video tutorial explaining TT User Setup).

Recognize that all risk changes should be published from a TT User Setup Client rather than in Guardian.

Note

Though you can import from Guardian instead, it is not recommended and could potentially result in the overwriting of risk data.

If you are currently using AutoCredit, ensure you have version 2.2.0 installed. Other versions are not compatible with TT User Setup 7.4.

Ensure that the current TT User Setup Server machines have Login Server licenses for the TTGlobal exchange.

Ensure that one or more TTUS Slave Servers are running; they will continue to process trader logins while the master server gets upgraded.

If you have product limits configured per account, ensure the Guardian product tables are current by running Guardian in an environment that contains all of your TT Gateways before upgrading. This ensures TT User Setup can properly migrate Account-based limits to the new format.
Note

Configuration files are not overwritten when upgrading TT User Setup Server. For instructions on updating these files, refer to the Using Master Files section of this manual.

Stopping TT Services

Prior to running the installation procedure to upgrade your version of TT User Setup, you must stop all TT services on the Master Server. Slave services on other machines can continue to run and will continue to process login requests.

Note

While TT User Setup services are not running, administrators are unable to use the TT User Setup Client, and traders are unable to change their passwords.

To stop TT Master Server services

  1. From the Control Panel of the machine where the Master Server is installed, click Administrative Tools.
  2. Click Services.

    The Services window displays.

  3. Click to highlight a TT-specific row, and click the Stop button.
  4. Repeat Step 3 to stop additional services.

Upgrading the TT User Setup Client and Server Using the Installation Wizard

Note

TT recommends installing TT Update on the TT User Setup client. This eliminates the need to manually upgrade the TT User Setup client, and ensures that the client version always matches the TT User Setup server version.

The following procedure describes upgrading TT User Setup, and includes the basic configurations necessary to get the client application up and running.

Note

TT recommends upgrading all TT User Setup clients to the same version as the TT User Setup Server. If you are not upgrading the clients, refer to the release notes to verify that the upgraded TT User Setup Server will support your existing client version.

To upgrade TT User Setup:

  1. Ensure all server machines have the necessary TTGlobal licenses.

    For a detailed description on applying and publishing licenses, refer to Applying the GuardServer License in the topics listed under Installation and Configuration.

  2. On the Master Server, stop all TT services. For details refer to Stopping TT Services earlier in this chapter.
  3. Back up the local database (.mdb file), the TTUserSetupServer.ini file, and all risk files on the TT User Setup Master Server machine. For additional information on database backup, refer to Restoring Master Server Data from a Backup in the topics listed under Server Replication and Failover.Double-click the TT User Setup installation executable.
  4. A software security warning displays.

  5. Click Run.

    The TT User Setup License Agreement window displays.

  6. To accept the license agreement terms and continue the installation, click the I accept the terms in the license agreement option, and then Next.

    The Component Selection window displays.

  7. Click the TT User Setup Client and TT User Setup Server check boxes, and click Next.
    Note

    If you are only upgrading the TT User Setup Client, the Component Selection window will not display.

  8. Click Next.

    The Installation Completed window displays.

  9. Click Finish.
  10. If you are upgrading only the TT User Setup client, the upgrade is complete. If you are upgrading a TT User Setup server, continue to Upgrading the TT User Setup Database.

Installing TT User Setup Using the Command Line Interface

Use the command line interface to expedite the upgrade process by suppressing some or all of the dialog boxes that appear during a GUI installation. This is useful when you want to perform a silent or remote installation.

When entering the command, use the following syntax:

packagename.exe -a--argument1=value--argument2=value

where:

  • packagename.exe equals the name of the executable file (e.g., tt_user_setup_r7.4.6p17.exe)
  • -a identifies that arguments follow in the command
  • --argument1 equals the arguments you wish to use from the table below.
Note

Argument values that include a space must be enclosed in quotation marks.

For multiple installations, you can open a text editor, such as Notepad, and create an install configuration file that contains a list of arguments you want to use. When creating an install configuration file, you must list each argument on a separate line.

Example Install Configuration File

setupclient

accept_eula

nofinaldialogs

configmupgrade

Once created, you can give the file any name you want. You can then begin the installation by issuing the packagename.exe-a command with the --installcfg<filename> argument.

The following example shows the command line argument used to install TT User Setup 7.4.6 package 17 using an installation configuration file named Install.txt located on the C: drive:

tt_user_setup_r7.4.6p17.exe -a --installcfg=c:Install.txt

To install TT User Setup using the command line interface:

  1. Ensure all server machines have the necessary TTGlobal licenses.

    For a detailed description on applying and publishing licenses, refer to Applying the GuardServer License in the topics listed under Installation and Configuration.

  2. On the Master Server, stop all TT services. For details refer to Stopping TT Services earlier in this chapter.
  3. Back up the local database (.mdb file), the TTUserSetupServer.ini file, and all risk files on the TT User Setup Master Server machine. For additional information on database backup, refer to Restoring Master Server Data from a Backup in the topics listed under Server Replication and Failover.
  4. Open a command window (from the Start menu, select Run, and then type cmd).
  5. When the command window appears, enter the cd <root drive>: command to navigate to the location of the executable.
  6. Enter the name of the executable file followed by -a and the arguments you want to use. lists the available arguments.
    Note

    Argument values that include a space must be enclosed in quotation marks.

    TT User Setup Command Line Installation Upgrade Arguments
    ArgumentFunction

    --installcfg=[file]

    Sets the filename and location for the file containing applicable command line interface commands. Enter one command per line and omit leading “--“.

    --reboot=[“force”| “promptrestart”|“norestart”]

    Sets the server’s behavior following the installation. The --reboot command uses the following values:

    • norestart: The installation does not reboot the server. In addition, the installation suppresses the Reboot Now dialog.
    • force: The installation reboots the server without displaying the Reboot Now dialog.
    • promptrestart: The installation displays the Reboot Now dialog.
    Note

    If the --reboot command is not present, the installation exhibits the default behavior.

    --setupclient

    Specifies that the client component should be upgraded for TT User Setup.

    Note

    The Components dialog will NOT be suppressed if the –-setupserver parameter is also passed, or if the TT User Setup Server is currently installed.

    --setupapi=1

    Specifies that the API component should be upgraded for TT User Setup.

    Note

    Applies to 7.17.13 and later.

    --setupserver

    Specifies that the server component and client component should be upgraded for TT User Setup.

    Note

    The Components dialog will NOT be suppressed if the –-setupserver parameter is passed.

    --ttustypesilent

    Suppresses the display of the Components dialog even if the Server type is selected. If this machine also has a TT User Setup client installed, the client will also be upgraded.

    --noadminutil

    Specifies that the User Setup Administration Utility should not be launched after installation.

    --accept_eula

    Accepts the license agreement and stores the accepted EULA.

    --skipdesktop

    Removes desktop icons from the desktop.

    --nofinaldialogs

    Suppresses the final success or fail dialog.
    --confirmupgradeSuppresses the dialogs that confirm upgrade of TT User Setup and required components.
  7. If you are upgrading only the TT User Setup client, the upgrade is complete. If you are upgrading a TT User Setup server, continue to Upgrading the TT User Setup Database.

Upgrading the TT User Setup Database

After upgrading the TT User Setup server, you must upgrade the TT User Setup Server database

To upgrade the TT User Setup Database:

  1. To upgrade an existing database for your TT User Setup Server and to define a destination for your database file, on your desktop, double-click the TT User Setup Utility icon.

    The TTUserSetupUtil window displays.

    (7.17)

    (7.4)

  2. Click Run SQL Script Against TT User Setup DB.

    The Run SQL Script window displays.

  3. Click to select the Upgrade database to this version, x.x.x.x option.
  4. In the TT User Setup DB file field, choose either the default database name or click Browse to search for a file.
    Note

    If you change the name of your database, follow the Editing the Server Configuration File procedure, in the topics listed under Installation and Configuration.

  5. Click Run.

    If a user has different deployment or sharing settings for different Algo SE servers, the TT User Setup Utility opens a window that allows you to correct the mixed settings during the database upgrade. If this window displays while you are upgrading to 7.17, refer to Additional Steps When Upgrading from TT User Setup 7.4.x to 7.17.10 or Higher .

  6. Reboot your machine, and start Guardian and GuardServer services.

    For a detailed description on starting services, refer to the Initially Starting Guardian and GuardServer in the topics listed under Upgrading TT User Setup.

    Note

    Do not start the TT Chron or TT User Setup service at this time.

  7. Double-click the TT User Setup Desktop icon.
  8. On the message that indicates a Master Server cannot be found, click OK and close the TT Login window.
  9. On the Services window, start your TT User Setup Sever.

    As data is imported from Guardian, the Server Messages window will display status messages. When needed, you can export these messages to a report. For additional report information, refer to Exporting Data to a Report.

    For a detailed description on starting the TT User Setup application, refer to the Starting the TT User Setup Service in the topics listed under Installation and Configuration.

    Note

    The first time the TT User Setup Server starts, all risk data from Guardian will be imported.

  10. Close the Server Messages window, and log into the TT User Setup client.

    For a detailed description on logging into TT User Setup, refer to Logging into the TT User Setup Client in the topics listed under Installation and Configuration.

  11. Upgrade Slave Server(s). For details refer to the Upgrading Slave Servers later in this chapter.

Additional Steps When Upgrading from TT User Setup 7.4.x to 7.17.10 or Higher

Before completing an upgrade from 7.4.x to 7.17.10 or later, each user must have the Algo Deployment Allowed and Algo Sharing Allowed settings configured the same way for each Algo SE server. If a user has different deployment or sharing settings for different Algo SE servers, the TT User Setup Utility opens a window that allows you to correct the mixed settings during the database upgrade.

To correct the mixed settings during an upgrade from 7.4.x to 7.17.10 or higher:

  1. Enable or disable the settings for each user:
  2. Click Save and Publish.
    Note

    Although the Guardian product tables are updated, the Guardian GUI on the TT User Setup Server will not display the new settings from TT User Setup until the Guardian service is restarted.

Additional Upgrade Steps When Upgrading from TT User Setup 7.4.3

Note

This section does not apply when upgrading to 7.17. TT User Setup 7.17 automatically publishes to Guardian.

When upgrading from TT User Setup 7.4.3, if DisableProductLimitPublishing was enabled, the first time you log into TT User Setup, some TTORD records may be listed as being out-of-sync with Guardian. Affected TTORDs will display the Trading Allowed flag as checked (True) in TT User Setup, and as unchecked (False) in Guardian. The Risk Check flags may also be out-of-sync. Publishing these records from TT User Setup will re-sync TT User Setup and Guardian.

For more information about the DisableProductLimitPublishing parameter, refer to .

Additional Upgrade Steps When Upgrading from TT User Setup 7.4.1 and Earlier

Note

This section does not apply when upgrading to 7.17. TT User Setup 7.17 automatically publishes to Guardian.

TT User Setup 7.4.2 introduced support for product margins per market rather than only per flavor. When configuring products that are hosted on more than one gateway flavor per market, you now create only one product margin rather than one for each gateway flavor.

When upgrading from a version prior to 7.4.2, there may be multiple product margins in a market that are already configured for the same product. When the margins are identical for these products, TT User Setup merges them into a single product margin. However, if the product margins are not identical, your TT User Setup administrator must review the conflicts and decide which margin to use.

To upgrade from TT User Setup version 7.4.1 or earlier:

  1. Complete all the steps in Upgrading the TT User Setup Client.
  2. From the TT User Setup Client, access the Server Admin menu and select Product Margins.

    The Product Margins window appears.

  3. Click View All TTUS Guardian Conflicts.

    The Product Table Conflicts window appears.

  4. Select the TT User Setup or Guardian value:
    • To use the value in TT User Setup, click Use this margin for the TT User Setup row. Or if you want to use the value in TT User Setup for all conflicts in this market, click Use TT User Setup value to resolve all <gateway> conflicts.
    • To use the value in Guardian, click Use this margin for the appropriate gateway flavor. Or if you want to use the value in Guardian for all conflicts in this market, click Use Guardian <gateway flavor> value to resolve all <gateway> conflicts.
  5. Example: In the above example , the CONF, FDAX, and other products have different margins on EUREX, EUREX-A, and EUREX-B. To resolve the conflicts, you could select the appropriate Use this margin for each product. Alternatively, if you always want to use the EUREX-B margin, you could select Use Guardian Eurex-B margin values to resolve all Eurex conflicts just once.

  6. When you are finished resolving conflicts, click Done.

    TT User Setup returns to the Product Margins window.

  7. Click Save and Publish.
    Note

    Although the Guardian product tables are updated, the Guardian GUI on the TT User Setup Server will not display the new settings from TT User Setup until the Guardian service is restarted.

Exporting Data to a Report

The first time your server starts, it will automatically import all risk data from Guardian. During this import you can monitor the Server Messages window for any pertinent messages related to the import. For example, when all import and start-up tasks have been successful, the Server Messages window will display, "Master ready".

To preserve a copy of your messages, export the message data to an HTML or CSV report.

The following procedure describes exporting server messages data to an HTML report.

To export data to an HTML report:

  1. From the TT User Setup Client menu, select Server Admin and click Server Messages.

    The Server Messages window displays.

  2. From your machine's Control Panel, select Administrative Tools and click Services.

    The Services window displays.

  3. On the Services window, click to highlight the TT User Setup (Server) row and click the Start button.

    The Server Messages window begins to populate.

  4. Right-click in the primary pane to display a context menu.

  5. Click Export to HTML.

    The Windows Save As dialog box displays.

  6. Select the destination for your .html file and give the report a file name.
  7. Ensure HTML Files displays in the Save as type field, and click Save.

    Your report displays in your Internet browser.

Upgrading Slave Servers

After upgrading TT User Setup on your Master Server machine, you can upgrade your Slave Servers on their respective machines.

Note

Prior to upgrading TT User Setup on the Slave Server machine, stop all TT services on that machine. For a detailed description of stopping services, refer to Stopping TT Services.

To upgrade Slave Servers:

  1. On the Slave machine, run the TT User Setup installation package.
  2. Double-click the TT User Setup Utility desktop icon.

    The TTUserSetupUtil window displays.

  3. Click Run SQL Script Against TT User Setup DB, click the Upgrade database to this version, x.x.x.x option, choose either the default database name or Browse to the TT User Setup DB file field, and then click Run.
    Note

    If you change the name of your database, follow the Editing the Server Configuration File procedure, in the topics listed under Installation and Configuration.

  4. Reboot your machine, and start Guardian and GuardServer services.

    For a detailed description of starting services, refer to Initially Starting Guardian and GuardServer in the topics listed under Installation and Configuration.

  5. Start the TT User Setup (Server) service.

Publish Differences To Guardian (7.4 only)

TT User Setup provides a detailed account of differences that exist between TT User Setup and Guardian data prior to publishing. You can use the information provided in the Guardian/User Setup Differences Details window to help reconcile these differences. In order to synchronize the two systems, you must publish the dissimilar data.

To publish differences to Guardian:

  1. From the TT User Setup Client, on the File menu, click Publish to Guardian.

    -or-

    On the toolbar, click the Publish to Guardian icon.

    The Publish to Guardian window displays.

  2. Highlight the rows of the differences you want to publish.
  3. Click Publish Selected Gateway Logins to Guardian.
    Note

    For details on TT User Setup publishing functionality, refer to the TT User Setup Help system and the How to Recognize and Review Changes Prior to Publishing to Guardian tutorial topic.