TTM Network Administration Documentation
- What’s New In This Release
- TTM Overview
- Unicast And Multicast Network Communication
- Network Setup And Configuration
- Installing And Upgrading TTM And Guardian
- TTM Daemon
TTM Remote Host Daemon And Remote Clients
- Introduction to the TTM Remote Host Daemon
- Remote Mode: Pros and Cons
- Remote Mode Operations
- Network Considerations when Deploying the Remote Host Daemon
- Configuring a Remote Host Daemon
- Configuring the Remote Client
- Compressing Data
- Manually Configuring TCP Window Size
- Testing the Remote Connection
- Remote Host Daemon Failover (Disaster Recovery)
- Advanced Topics
- Maintenance And Troubleshooting
- Ttmd.cfg File Reference
Introduction to the TTM Remote Host Daemon
What is the Remote Host Daemon?
The Remote Host Daemon enables TT applications to remotely connect to a target network over a standard Internet connection. Because the Remote Host Daemon uses the TTM Daemon executable, to configure the TTM Remote Host Daemon, you use standard TTM Daemon parameters.
Thus, between a TT machine operating in remote mode and a TT machine operating on a client LAN, the only difference between the two is in Guardian’s Daemon Setup dialog box.
When Should I Use the Remote Host Daemon?
It is ideal to use remote mode to connect traders to your TT trading network when:
- Only one trader exists on a site
- A trader is mobile; he uses a laptop on various network segments that may or may not have WAN Routers.
- Traders must connect to the TT Gateway network using a VPN.
- A client has a small number of traders per site (three or less) and no network administrator who can manage WAN Routing setup and administration.
A Remote Host Daemon instance can support a maximum of 100 X_TRADERs for uncompressed systems, 80 for compressed systems, and 70 for encrypted systems.
The following examples illustrate when remote mode connectivity is and is not effective.
|A sole trader sits on a small network segment but trades huge volumes and requires failover resiliency. He maintains WAN Routers set up for failover.|
|A company has one primary location with several small satellite offices that host two or three traders each. Due to the size of these offices and the distance between them, the company does not employ a network administrator outside of the primary location. These satellite offices are all connected to the primary office via private lines in a star topology. Each private line can accommodate 1 Mbps per trader. In this scenario, the network is ideal for remote mode connections.|
A company has one primary location with several small to medium-sized satellite offices. These satellite offices each host five traders and connect to the primary office via private lines in a star topology. In this scenario, those offices with only a few traders (1-3) and that cannot afford to employ a network administrator, connect to the TT Gateway using remote mode. The other offices maintain a network administrator and connect via WAN Routing.
The following diagram illustrates a TT Trading System that supports remote connections from 4 machines via a TTM Remote Host Daemon connection.
As of Version 1.7.1, TTM supports a hot failover setup for remote mode connections. To support this configuration, you must setup at least two Remote Host Daemons on the host network and configure the IP addresses of a primary and a secondary Remote Host Daemon in the Remote Client’s Guardian Daemon Setup dialog box.