Try TT Now

Upgrading from TT User Setup 7.4to 7.17 Checklists

Master Server Upgrade Checklist

Master Server Upgrade Checklist
Complete Task

Stop all TT services.

Back up the .mdb database file, the datfiles directory that has risk (.rsk) files, and the TTUserSetupServer.ini file. For added security, back up the entire TT directory.

Run the installation package to upgrade the server (and client) on the machine.

Note: Make sure to allow the installation to complete.

Reboot the machine (if prompted during installation).

From the TT User Setup Utility, click the Run SQL Script Against TT User Setup DB option and then select the Upgrade database to this version option. Click Run.

Warning: If any errors occur while running an upgrade script, discontinue the installation and contact the TT Customer Support Center.

From the TT User Setup Utility, click Edit Server Configuration File and update the database replication and location options as needed.

Note: In TT User Setup 7.4 the Master Server does not require authentication, and the server automatically communicates with the local Guardserver. As such, Admin Login credentials are no longer an option.

Open a TT User Setup Client and close the TT Login prompt that appears.

Note: You will be unable to log in at this time.

From the Server Admin menu, click Server Messages to open the Server Messages window. This allows you to monitor the first startup of the new TT User Setup Server.

Start all the necessary services, including TT Guardian, TT Guardian Server, and the TT User Setup services, either individually or via TTChron.

Review any errors, which if necessary, can be exported to a report by right-clicking in the Server Messages window.

Note: If TT Chron is configured to start TT Guardian and TT Guardian Server automatically, you will only need to start the TT User Setup Service manually.

When the server is ready, a message displays indicating, "Done with all startup tasks. Master ready." Should you believe you missed the message, you can quickly scroll through the window.

Start all the necessary services, including TT Guardian, TT Guardian Server, and the TT User Setup services, either individually or via TTChron.

Note: Duplicate ID errors in aconfig for FIX-T and FIX-U can be safely ignored, as can messages indicating TT User Setup and Guardian are out of sync..

Verify that you have completed the Master Server upgrade by successfully logging into TT User Setup with a valid username and password.

Slave Server(s) Upgrade Checklist

Slave Server Upgrade Checklist
Complete Task

On the Slave machine(s), stop all TT services, or TTChron will continually reboot the machine(s) and you will be unable to run with a new Master server until an upgrade is complete.

Run the installation package to upgrade the TT Slave server on the machine.

Note: Make sure to allow the installation to complete.

Reboot the machine (if prompted during installation).

From the TT User Setup Utility, click the Run SQL Script Against TT User Setup DB option, select the Upgrade database to this version option, click Run, and verify the database upgrade completes without errors.

Start all TT services on the Slave machine and verify the service starts successfully.

Note: In the client, the Server Messages window should indicate that the Slave has been able to replicate the data of the Master.

Miscellaneous Notes and Tasks 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.

Miscellaneous Notes and Tasks
Complete Task

If DisableProductLimitPublishing was enabled in TT User Setup 7.4.3, 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. Refer to Publish Differences To Guardian if needed.

Miscellaneous Notes and Tasks When Upgrading From TT User Setup 7.4.x To 7.17.10

Miscellaneous Notes and Tasks
Complete Task

You need to be aware of the following changes to the user database and reflected in the user interface after an upgrade to 7.17.10.

During an upgrade from 7.4.x to 7.17.10, existing account-based product limits are migrated in the database and imported into the redesigned Product Limit window as follows:

  • Existing intra-product spread limits are mapped to the applicable future or energy limit. For example, spread limits for a CME 6A futures spread would appear as a CME 6A futures product limit in the database and Product Limit window after an upgrade.
  • Existing intra-product strategy limits are mapped to the applicable future or option limit. For example, strategy limits for a CME OZD options strategy would appear as a CME OZD options product limit in the database and Product Limit window after an upgrade.
  • Stocks and bonds product limits will be unchanged.
  • Limits for unsupported product types (Swap, Warrant, Forex, and NDF) are deleted.
  • Spreads and strategies that do not appear in the Guardian product table are imported as an inter-product spread or inter-product strategy. For example, an OZI strategy (product type “strategy”) with an OZI option and ZI future.

For more details, refer to the Account-Based Risk Upgrade Feature Guide

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. For more information refer to Additional Steps When Upgrading from TT User Setup 7.4.x to 7.17.10 or Higher.