Trade Tracker Basics
- Upon launching the application, the main window will appear and Trade Tracker will automatically log into TT Gateways based on the Gateway Logins assigned to the TT User Setup user specified in the “username=” field in “Trade Tracker.ini”.
- Once launched, Trade Trackershouldremainrunning at all times. You can use TTChron to schedule Trade Tracker when to run so that you can have it reset once a day or once a week if you like.
- All Adds, Changes, Cancels, Order Expirations,
Order Rejects (by the exchange only) and Fills which were accepted
by the exchange will be recorded by Trade Tracker.
Please note: In the event that Trade Tracker is shut down and restarted, Trade Tracker may not be able to recover all order activity. It will record any fills that have happened, as long as the TT Gateway’s Fill Server hasn’t rolled sessions, as well as record the current state of any orders that still exist. Any order changes and cancels that happened in the meantime will be lost.
- Trade Tracker is currently capable of sending
e-mail notifications and logging to the Windows event log for three
separate errors that may occur. These are listed below. See Figure
3 for Event Log information.
- Trade Tracker is unable to make the initial connection with the database. One thing to note is that Trade Tracker is most commonly started via the TTChron application. If there is a problem with the database and Trade Tracker is unable to connect it will immediately close and then be restarted by TTChron. If e-mail notifications are enabled this could create a large number of logon error e-mails being sent. To counteract this Trade Tracker will only send one e-mail for login failure per time specified. The default for this constraint is one hour, but it is configurable through the Trade Tracker.ini file by adding a “LOGONERRORWAIT” key to the [Email] section. The key will take a numeric value that is the amount of time to wait between e-mails in minutes.
- Trade Tracker was unable to login to all of the gateways specified in the Trade Tracker.ini file in the time specified by the “Elapsed Time” key. In this instance Trade Tracker will send an e-mail specifying what servers it was unable to log into and if the gateway was found in the environment. Note that this does not necessarily mean that Trade Tracker didn’t log into the servers, just that it had not done so within the time specified. If you receive these notifications when no error seems to exist try increasing the “Elapsed Time” key’s value.
- Trade Tracker received an error while writing
data to the database. Trade Tracker will send this message immediately
when it first encounters an error. For all subsequent errors Trade
Tracker will send a message for any errors that have occurred in
the last one hundred attempts to write to the database. This e-mail
will say how many attempts resulted in error. All of the data for
these error messages will be stored in the Trade Tracker_ErrLog.log
Trade Tracker was unable to establish a connection with the database.
Trade Tracker was unable to log into the following servers within the specified delay time:
Trade Tracker has been disconnected from the database and is unable to reconnect.
Trade Tracker has encountered an error when inserting data into the database.
Trade Tracker has encountered errors when inserting data into the database. [Number of errors] insert(s) has/have returned an error.
Trade Tracker Initialization Error - Trade Tracker was unable to log into any servers with the configured Username and Password within the specified delay time. Please consult the Trade Tracker.ini file to ensure all login credentials are correct.
Figure 3: Event Viewer Logs
- Trade Tracker loses connectivity with the database once it has already made the initial connection. If connectivity with the database is lost Trade Tracker will try to reconnect five times. If it is still unable to connect it will send the notification e-mail.
- You must have a Key Server in order to run this application. The key server ensures every order will have a unique ID. For more information on setting up and configuring a key server in your TT Architecture, refer to the TT Gateway SAM product documentation.
- Should the application need to be re-booted for any reason it is possible that orders will exist when the application restarts. In this case, Trade Tracker will add a new record to the tblOrderActions table for each order with the order action being “Existed Upon Startup” if the order was in the market or “Existed Upon Startup – On Hold” if the order was currently on hold. These records are added so that you can determine the current state of the order once Trade Tracker was re-booted.
- A combination of the TTSiteOrderKey, Date, and Fill Key are used to identify unique fills. If a duplicate fill is ever received, which would typically only happen upon a system re-boot, the duplicate fill will be ignored.
- Trade Tracker only stores messages that are received from the Exchange by the XT_API. Order reject messages from Guardian are not stored.
- Trade Tracker supports the Windows Server
2008 R2 operating system with the following caveats and required
- 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: Due to security changes made by Microsoft, Trade Tracker's main window will not be visible on a user's desktop when launched by TT Chron (an Interactive Service Detection dialog box opens instead). Running the "Interactive Services Detection" Windows Service will allow users to switch over to the "Session 0" desktop to view the Trade Tracker's main window when launched via TT Chron.
- Starting Programs: TT Chron may not properly close and/or monitor Trade Tracker if it is started manually. Users should first start TT Chron and allow it to start Trade Tracker per its schedule.
- Start TT Chron desktop icon: The Start TT Chron desktop shortcut may not work if User Account Control (UAC) is enabled unless the user right-clicks the icon and selects Run as administrator from the context menu.