TT CME Gateway System Administration Manual - Trading ...
TT CME Gateway System Administration Manual - Trading ...
TT CME Gateway System Administration Manual - Trading ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2<br />
Preparing to Install<br />
<strong>CME</strong> <strong>Gateway</strong> <strong>System</strong> <strong>Administration</strong> <strong>Manual</strong> 31<br />
<strong>Trading</strong> Technologies International, Inc.<br />
Installing and Upgrading<br />
Customer Tasks Before the <strong>CME</strong> <strong>Gateway</strong> is installed, the customer must perform the following<br />
tasks:<br />
• Obtain the host server IP addresses, Firm ID, associated passwords, and<br />
connection ports. <strong>CME</strong> Group distributes this information in a separate<br />
document (or E-mail). You must obtain one set of connection information<br />
for each Order Router or customer membership that uses the <strong>TT</strong> <strong>Gateway</strong>.<br />
• For circuit sizing (network bandwidth) between your network and the <strong>CME</strong><br />
Group host, refer to the <strong>CME</strong> Group specifications.<br />
• Confirm that all network routes to <strong>CME</strong> Group work from the server onto<br />
which <strong>TT</strong> plans to install the <strong>TT</strong> <strong>Gateway</strong>.<br />
• Obtain the IP address that <strong>CME</strong> Group defines for your <strong>TT</strong> <strong>Gateway</strong>. You<br />
must use this IP address as either the NATed address (if you are using a<br />
NAT firewall) or the address of the NIC that faces the <strong>CME</strong> Group network<br />
(if you are using a dual-homed server).<br />
• For each connection to <strong>CME</strong> Group, obtain the SessionId from <strong>CME</strong> Group.<br />
The following are customer tasks specific to networking and network<br />
setup:<br />
- <strong>CME</strong> Group distributes its MDP price streams via multicast traffic to a<br />
network area that you define for <strong>CME</strong> Group.<br />
- For history data requests, you must enable TCP connections on the <strong>TT</strong><br />
<strong>Gateway</strong>.<br />
- The IP address and subnet mask that the customer sends to <strong>CME</strong><br />
Group for the Price Server MDP connection should be that of the local<br />
LAN facing NIC on the <strong>CME</strong> <strong>Gateway</strong>.<br />
- When setting up IP addresses, the customer must make sure that they<br />
are fully resolved through any NAT firewalls and NAT routers that are<br />
used.<br />
Warning: <strong>TT</strong> does not support or recommend using NAT IP addresses to<br />
connect to the <strong>CME</strong> Group. <strong>CME</strong> Group holds you fully responsible for all<br />
maintenance regarding NAT IP addresses. You must consult the exchange<br />
for all NAT implementation details.<br />
- On all network devices that reside between the <strong>CME</strong> <strong>Gateway</strong> and the<br />
<strong>CME</strong> Group host network, the customer must ensure that the Primary<br />
port used in the hostinfo.cfg file is available for one-way, outbound TCP<br />
sessions to the <strong>CME</strong> Group host servers.<br />
- Obtain network connectivity information from <strong>CME</strong> Group for the<br />
remote host IP addresses and ports to which the <strong>CME</strong> <strong>Gateway</strong> must<br />
connect and the names of the customer-side routers.
Change language