All Gateways Documentation
- General Gateway Architecture
- Installation And Initial Setup
- Tools And Utilities
- Automating And Scheduling Processes
- Aconfig And System Architecture
- Configuring Miscellaneous System Behavior
- Product Tables
Configuring Server Component Behavior
- Server Component Logging
- Configuring the Order Server
- Order and Fill Server Architecture
- Performance Measurements
- Enabling the Enhanced Order/Fill Delivery
- Troubleshooting and Recovery
- Enhanced Order/Fill Delivery Enhancement: FAQ
- Account-Based Risk
- Operator ID
- Using the Operator ID Assistant
- Using the Eurex Password Assistant
- Avoid Orders That Cross
- Order Passing Support
- Expired Order Status Identification
- Configuring the Price Server
- Price Server: Architecture
- Market Data Users
- Market Data FAQ
- Price Server: FAQs
- Fill Server: Overview
- Fill Server Rollover
- Fill Server: Start of Day Records
- Modifying Fills
- Fill Server: Troubleshooting
- Configuring the Fill Server
- Configuring the Key Server
- Configuring GAL Settings
- TT Logging
- Disaster Recovery
- TT Order Keys
- System Files
You can configure TTM’s service numbers and daemon setup (such as the port that the daemon uses, its NIC card interface, and its multicast address).
TTM Daemon Setup
Because the AConfig Utility does not also update the ttmd.cfg file (which TTM also reads from), do not use the AConfig Utility to change Daemon Setup values in aconfig_local.xml. Instead, use the Guardian GUI as described in the TT Trading Systems – Network Administration Manual. The Guardian GUI updates both the aconfig_local.xml and ttmd.cfg files.
There are two areas in aconfig_local.xml that contain TTM Daemon setup parameters:
- Local: Configures the local daemon’s communication parameters.
- Remote: Stores the remote daemon’s communication parameters. This section does not configure the remote daemon’s behavior. It only sets the local daemon’s expectations of the remote daemon’s configuration.
Locations: For local daemon setup: AConfigCoreMessagingProximity-SpecificLocal For remote daemon setup: AConfigCoreMessagingProximity-SpecificRemote
Function: Sets the IP address to which the TTM daemon connects.
In the Local section, setting of default sets TTM to use the primary IP address.
Default setting: default
Function: Sets the TCP port number on which the TTM daemon communicates.
Default setting: 10200
Function: Sets the network interface (i.e., NIC card) on which the TTM Daemon sends and receives multicast information. A setting of default sets the TTM daemon to use the primary NIC card.
Default setting: default
Function: Sets the multicast group on which the TTM daemon sends its multicast.
Deprecated in TTM 1.5.
Default setting: 22.214.171.124
The following table lists parameters that set the service numbers TT applications use when sending data to TTM. For more detailed information on Service numbers and how TT applications use them, refer to the TT Trading Systems – Network Administration Manual.
Both production and simulation modes have their own service settings.
TT recommends that you do not change any of the following default values. However, if you do change these values, all machines that communicate with one another must have the same sets of values.
Locations: For Production data: AConfigCoreMessagingServiceProduction For Simulation data: AConfigCoreMessagingServiceSimulation
Function: Sets the TTM service on which TT applications send orders and non-price data.Default setting: For Production: 8900; For Simulation: 8910
Function: Sets the service on which TT applications send price data.Default setting: For Production: 8901; For Simulation: 8911
Function: Sets the service on which TT applications send order data.Default setting: For Production: 8902; For Simulation: 8912
Function: Sets the service on which TT applications send heartbeats.Default setting: For Production: 8900; For Simulation: 8910
Do not change the default value of these parameters unless instructed to do so by TT support.