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
aconfig.xml in the TT Gateway Environment
To accurately display the range of TT Gateway exchangenames in Guardian, TT has reserved a set of exchange IDs in aconfig.xml. If you want to customize the name that your TT Gateway as it displays in Guardian, you can do so by editting aconfig.xml.
However, due to TT system’s architecture you must use only one version of aconfig.xml on all TT machines in your network. Because of this restriction, during the TT Gateway installation you must supply any preexisting aconfig.xml from your TT trading network. By supplying the aconfig.xml, the TT Gateway installation updates the list with any new exchange IDs.
If you have an aconfig.xml file on your network and do not supply it during installation, you can encounter major problems since the TT Gateways install with their own aconfig.xml. When Guard Server on a TT Gateway starts up, whichever file on the host network segment has the higher RevisionCount parameter overwrites all other aconfig.xml files on that network segment. Thus, if you customized aconfig.xml and fail to provide it during installation, the following occurs:
Merging aconfig.xml Settings
When you supply an aconfig.xml file during installation, the TT Gateway install performs the following actions:
- Writes all new exchange IDs to the aconfig.xml file that you provide.
- Increments the file’s RevisionCount parameter. Incrementing this number ensures that when the Guard Server starts up, it broadcasts the file to all other TT Gateways on the network.
If you do not provide an aconfig.xml during installation, the TT Gateway installs a new aconfig.xml file and sets its RevisionCount to a low number.
Replicating aconfig.xml Data
When Guard Server starts up, it compares the RevisionCount parameter in its aconfig.xml file to the RevisionCount parameter in other TT machines’ aconfig.xml files:
- If another machine on the network has a file with a higher RevisionCount parameter, Guard Server requests the aconfig.xml and overwrites its local aconfig.xml with the requested one.
- If the version of the local aconfig.xml is higher than the other aconfig.xml files on the network, Guard Server replicates its aconfig.xml to the other TT machines.