This service allows TT customers, co-located in the same data center facility as a TT environment, to connect their trading network to TT via a simple, point-to-point, duplex fiber connection managed by the data center provider. This service is offered in unprotected (single link) or protected (redundant) configurations.
The following diagram shows the scenario for connecting directly to a co-located TT data center.
In this diagram:
Through the Internet, a DNS lookup occurs for *trade.tt allowing the client browser to connect to *trade.tt on private AWS in TT Cloud.
The connection to TT Cloud is established through the Internet from the client network's Web Proxy and firewall and maintained for less latency-sensitive traffic. The Trade application, Setup application, and other available TT Cloud services are downloaded to the client's browser.
Note: A DNS and Internet connection are required for connecting to TT Cloud.
In the user's browser at the client site, the Trade application scans the access lines in Setup for a Direct Connect URL and determines that there is an unrestricted IP address available for an optimal route from the client network to a co-located TT data center.
The Web Proxy is bypassed and the user's browser connects directly to the HA Proxy load balancer and Edge Server in the TT data center.
Note: Use of a Web Proxy is not recommended for connecting directly to the TT data center. If Web Proxy is rebooting during trading, then traders will not see market data during the service outage. In addition, Web Proxies are not usually high performance and therefore add unnecessary latency for traders. You should use a Web Proxy Bypass when using Direct Connect. This can be accomplished by placing the *cc.trade.tt web proxy bypass exception in your PAC file.