System Component Failure
Order Routers exist on most TT Gateways as distinct processes that display individually in Guardian. If this is the case and an Order Router fails, any trader on that Order Router immediately loses his connection to the exchange. TT Gateways that use Order Routers in such a fashion include those from the LIFFE Connect and MISS families of TT Gateways.
On other TT Gateways, such as the TT CME Gateway, Order Router processes exist as threads within the Order Server (i.e., they are not separate processes). On these sorts of TT Gateways, traders cannot lose their connections due to the failure of an Order Router. Whether these Order Routers list in Guardian is dependent on the TT Gateway type.
Lastly, there are other TT Gateways that do not have Order Routers, either as separate processes or as threads within the Order Server.
For further information on Order Routers specific to a particular TT Gateway, refer to that TT Gateway’s SAM.
In a disaster recovery situation where a connection to the exchange is lost (e.g., a Telco failure), traders do not need to exit X_TRADER®. Instead, X_TRADER® remembers the exchange name(s) of the TT Gateway(s) to which it connected.
If a trader logs into a TT Gateway named ENxtFut-A, X_TRADER® records this. If the connection to Euronext fails, X_TRADER® continually attempts to connect to the TT ENxtFut-A Gateway until successful.
If a TT Gateway fails in an environment where TT Gateways neither support nor have been configured for hot failover, and a trader needs to continue trading, the trader can close X_TRADER®, reopen it, and log into an alternative TT Gateway. This alternative TT Gateway must connect to the same exchange but have a different exchange-flavor (e.g., when CME-A fails, the trader logs into CME-B).
For information specific to this sort of gateway failover, refer to Redundant TT Gateways.