← Back to X_TRADER® Help Library

Trade Tracker Documentation


  1. Verify that both X_TRADER and the X_TRADER API are installed.  Also, ensure that MS .NET is installed on the machine.
  2. Before installing Trade Tracker, you must close all windows based applications, including Guardian.  If you leave Guardian running while installing Trade Tracker, you may receive an error message which will automatically shut down Guardian.  This is ok.  You will just need to restart Guardian after installation if this happens.
  3. Double-click on the installation file (i.e. Trade_Tracker_Install.exe).  This opens the Trade Tracker installation wizard.
  4. Click the Next button through all of the screens of the installation wizard, making sure to accept the license agreement.  Change the default User Information and Destination Folder if desired.
  5. The application will be installed.  The last screen will display a message that Trade Tracker was successfully installed.
  6. Click the Finish button.  A Trade Tracker shortcut icon will be added to the desktop.  The computer does not need to be rebooted.
  7. After installing Trade Tracker through the installation wizard, the first thing you will need to do is create the database.

    For SQL Server:

    • Open up SQL Server Enterprise Manager and navigate to the database server where you want to create this database. Open up Query Analyzer. Open up the Trade Tracker.sql file that can be found in the application’s root directory (e.g., C:TTProf ServTrade Tracker).  Run this query to create the database and the user.  By default, this database script will create a database user with the following username and password:
      1. Username = TradeTrackerUser
      2. Password = 12345678
    • Feel free to change this password to something that you can easily remember.
    • Once the password has been set, go to the following within the SQL Enterprise Manager application: Enterprise Manager->Security->Logins->TradeTrackerUser->Properties. Enter the password again in this location.

    For Oracle:

    • Create a new schema and user that Trade Tracker will use.  Make sure that the machine that Trade Tracker will run on has the Oracle Client installed with administrator rights.
    • Import the Trade Tracker_Oracle.sql file into Oracle’s SQL Scripts and click Run.  This script will create all of the tables that Trade Tracker needs.

    For MySQL

    • Open the MySQL command line client and login using the appropriate credentials.
    • Run the database script by typing the command “source” followed by the path to the SQL file (default file path is “C:ttProf ServTrade TrackerTrade Tracker_MySQL.sql”).  This will create all of the tables that Trade Tracker needs.

    For Access

    • There is no database setup for Access.  Trade Tracker will create the Access database when it is started.
  8. Next you must configure the Trade Tracker.ini file for the login user.  The “Trade Tracker_master.ini” file can be found in the application’s root directory, “<root>:TTProf ServTrade Tracker”.  This must be copied and renamed to “Trade Tracker.ini” in the “<root>:TTProf ServTrade Tracker” directory.  A sample Trade Tracker.ini file is shown in Figure 1 below.

    Figure 1: Trade Tracker.ini file snippet

  9. Update the [Database] section with the name of the database server (you can leave “(local)” if the application is running on the same machine as the database server, or you can use as a loopback IP). If running SQL Server, Oracle, or MySQL with multiple databases on one machine then update the “DATABASE” key with the name of the database.  If using Access the “DATABASE” key should be the full file path of the database that Trade Tracker will be using.  There is no need to create the Access database prior to running Trade Tracker because Trade Tracker will create it if it does not exist.  Update the UserID and password values to the logins that you created for this user when creating the database.  If using the default login on MySQL than the UserID will be “root”.  If using Access there is no need for a UserID or Password key. If using SQL Server, the “SOURCE” key should be set to “SQL Server”.  If using Oracle, the “SOURCE” key should be set to “Oracle”.  If using MySQL, the “SOURCE” key should be set to “MySQL”.  If using Access, the “SOURCE” key should be set to “ACCESS”.  If there is no “SOURCE” key, it will default to SQL Server.  If running Oracle, SQL, or MySQL and using a port other than the default, add a “port” key and type the port that your database is listening on.  If using Access there is also an optional key called “MAXFILESIZE”; this key will set how large, in MB, Trade Tracker will allow the .mdb file to get before creating a new one.  For performance reasons, Trade Tracker will only check the file size every 1,000 records, so the actual file size will slightly overshoot the “MAXFILESIZE” specified.  When it creates new files they will always be named according to the “DATABASE” key, and old files will be renamed with the date appended to the end of the file name.  If using MySQL, there is an optional “DRIVER” key to specify the driver version that is being used.  The default value is “{MySQL ODBC 5.1 Driver}” which is the most recent driver version available.  If using a different version add the new key and replace the 5.1 portion with the version number that is being used.  If unsure about what version you have, look in the Data Sources (ODBC) located in Administrative Tools.  Under the Drivers tab locate the MySQL driver, and it will show which version is installed on the machine.
  10. After the [Database] section you will see a section called [Data Mode].  The [Data Mode] section was added to the 1.7 version to control the granularity of the fill and/or order data stored in the database. To add this functionality to an existing TradeTracker.ini file, add the following, adjusting the parameters as required.

    [Data Mode]



    If FillUpdates is set to True, the application will store any fill updates into the database, and if it is set to False, it will not store fill data.  If OrderUpdates is set to True, the application will store the order updates (i.e. Adds, Changes, and Deletes) into the database, and if it is set to False, then it will not store order data.

  11. The [Email] section will include all information for setting up e-mail notifications that Trade Tracker will send out.  This section can be configured through the Trade Tracker interface by clicking “Email Settings…” under the Preferences menu item.  This will bring up a configuration window similar to Figure 2.  Once all the required information is filled out, the Test button will be enabled.  Pressing this button will send a test e-mail to the e-mail address in the “User information” section.  Trade Tracker will notify the user of the success or failure of the test.  These settings are saved every time the window is closed.  The user can turn the e-mail notifications on and off by clicking “Enable Email Notifications” under the Preferences menu item.

    Figure 2: E-mail Settings

  12. Update the [UniversalLogin] section with the username and password that you have configured for Trade Tracker in TT User Setup.  Trade Tracker will log into the TT Gateways with the Gateway Logins assigned to that user in TT User Setup.
  13. The [Logging] section is used to enable and disable logging to the Windows Event Log.  This option is on by default and can be turned off by setting the “WINDOWSEVENTLOGGING” key to false, or by clicking “Enable Windows Event Logging” under the Preferences menu.
  14. At the bottom of the ini file is a [Delay] section. This contains a value that indicates the number of seconds Trade Tracker will wait before sending Login Error e-mails.  If you are receiving error e-mails when no errors exist, you may need to extend this time.
  15. All Password keys in the Trade Tracker.ini file will be encrypted once Trade Tracker is executed.
  16. There is a file named “ttchron – snippet.ini” in the application’s root directory.  If you have TTChron installed you can cut and paste the content of this file into your TTChron.ini file (typically found in C:TTConfig) in order to utilize TTChron to automatically launch Trade Tracker every week at a certain time and close it at another time.

    Hint: It is probably best to schedule Trade Tracker to start up on Sunday and run for the entire week. You can then schedule it to shut down over the weekend when all exchanges are closed.