Try TT Now

All Gateways

Heartbeat Architecture

Heartbeat Data

Heartbeats carry the following data:

Heartbeat Data
Data TypeDescription

Load

Only server applications (Price, Order, and Fill Servers) send this data. It counts the number of client connections to the particular server application.

Product Table Sequence Number

Only Guard Server sends this data. Guardian uses this sequence number to determine whether it has the most up-to-date product table. For further information, refer to General Table Structure.

Status Identifier

Indicates the status of each TT application (e.g., initializing, active, etc.) running on the machine.

Service ID

Identifies the TT application(s) running on the machine (i.e., Order Server, Price Server, X_TRADER®, etc.).

Exchange ID

If the heartbeat comes from Guardian, the exchange ID represents the exchange to which the TT client application is connected. If the heartbeat comes from Guard Server, this ID represents the exchange to which the TT Gateway connects.

PID

The process ID of each TT service currently running on the machine.

IP Address

IP Address of the machine on which Guardian or Guard Server runs.

License token

Represents the license currently in use by the TT application.

Heartbeat Process

The following sections discuss the standard process by which Guardian and Guard Server communicate via heartbeats. For information on what happens when the heartbeat process fails, refer to Heartbeat Failure.

Note

You cannot configure the interval between heartbeats (i.e., the heartbeating process starts every seven (7) seconds).

Guardian

Every seven seconds Guardian initiates the following process:

  • Guardian requests a heartbeat from each TT client application on the workstation (e.g., X_TRADER®).
  • All active TT client applications send a heartbeat to Guardian.
  • Guardian waits one second, during which time it receives all heartbeats from TT client applications.
  • If no other TT client applications reside on the workstation, or if no TT client applications are running, Guardian does not receive any heartbeats, and the process ends here. Thus, if a TT Gateway has no other TT applications on it, Guardian does not send a heartbeat. Instead, refer to the following section called Guardian Server for details on Guard Server's heartbeat.
  • Guardian packages all client heartbeats into a Guardian heartbeat and sends it out on TT's multicast address.
  • All Guard Server components on the network that listen to the specified multicast address receive the heartbeat.

Guardian Server

Every seven seconds Guard Server initiates the following process:

  • Guard Server requests a heartbeat from each TT server application on the workstation (Price Server, Order Server, Fill Server).
  • All active TT server applications send a heartbeat to Guard Server.
  • Guard Server waits one second, during which time it receives all heartbeats from resident TT server applications.
  • Guard Server packages these individual heartbeats into a Guard Server heartbeat and sends it out on TT's multicast address.
    Note

    Even if no other TT server applications reside on the workstation, or are running, Guard Server still sends out a heartbeat, which contains its own information.

  • All Guardian and Guard Server applications on the network that listen to the specified multicast address receive the heartbeat.