For iLink order entry on the CME Globex platform, CME provides two gateway access models.
- Convenience Gateway (CGW) - provides a connection to any CGW session, which manages routing for all order entry messages to all market segments; routing is transparent to customer.
- Market Segment Gateway (MSGW) - provides a connection to a dedicated market segment, which is defined as a group of products on a given trading engine instance.
Info |
---|
Connecting directly to MSGWs involves a separate Session ID model, messaging behavior, and functional differences from that of the CGW. |
Customers can choose to access CME Globex markets through the MSGWs or CGWs, which route through the MSGWs.
...
Table of Contents | ||
---|---|---|
|
iLink Architecture Video Overview
Watch this brief video for an overview of iLink architecture.
iLink Session Model
For CGW, Session ID can exist on only one CGW.
For MSGW, Session IDs are shared across multiple MSGWs. Customers utilize a single Session ID, password, and port across all MSGWs.
...
Info |
---|
Sequence streams are unique per Market Segment ID and Session ID combination. For example, if session ABC has logged into Market Segment ID 50 and 60, then session ABC could receive Execution Reports from both market segments with the same message sequence number (tag 34-MsgSeqNum). |
Excerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
iLink Fault ToleranceFor iLink, Fault Tolerance is managed at the gateway application level. iLink has a designated host that is primary and another that is designated backup.
iLink Fault Tolerance Scenarios
|
Convenience Gateway
Customers can continue access and trade on the "standard" iLink gateway, referred to as the iLink Convenience Gateway (CGW).
The CGW allows the client system to connect to any CGW session, which manages routing for all order messages.
CGW FIFO Message Processing Model
The CGW FIFO message handling is enforced once the message reaches the MSGW. The following diagram shows the CGW model in which the example Session, AB1, exists on a single gateway.
Gliffy | ||||
---|---|---|---|---|
|
CGW Sequence Number Management
CGW message sequencing is managed using the SenderCompID value as in standard iLink Session Layer - Message Sequence Numbers.
Market Segment Gateway
One iLink MSGW provides connectivity to a single market segment. Currently there are 17 market segments or groups of products on a given trading engine instance.
Info |
---|
Client system messaging must identify the market segment for order entry routing. Market Segment is defined for each instrument in tag 1300-MarketSegmentID in the MDP Security Definition message. |
SFTP - MSGW Configuration
...
Info |
---|
Packet size maximum behavior based on MTU (Maximum Transmission Unit) - 1420 bytes, as defined on our network
|
MSGW Sequence Number Management
A single session is able to login to all 17 MSGW instances. To manage message sequence numbers, the customer must leverage the combination of Session ID (the first 3 characters of tag 49-SenderCompID) and tag 1300-MarketSegmentID.
...
CGW Session ID | MSGW Session ID | |
---|---|---|
Number of TCP connection(s) | 1 TCP connection to access all market segments | 1 to 17 TCP connections to access all market segments |
Number of sequence stream(s) | 1 sequence stream | Customers must manage 1 to 17 different sequence streams based on the combination of Session ID and Market Segment ID |
Tag 57-TargetSubID
Customers may connect directly to all Market Segment Gateways using the same Session ID. Customers can use tag 1300-MarketSegmentID from the market data Security Definition (tag 35-MsgType=d) message to specify the market segment for the products they want to trade on CME Globex.
...
Info |
---|
CGW sessions will continue to use tag 57-TargetSubID=G for all messages sent from the client system to CME Globex. |
MSGW Failover Scenarios
During a MSGW failover from the primary to the backup instance, customer iLink messages will be rejected.
...
- The failure of a backup component will not affect the primary connection state.
- The failed backup MSGW is restored.
CME Globex Timestamps
Watch this brief video for an overview of CME Globex timestamps.
...
Gliffy | ||||
---|---|---|---|---|
|
Nanosecond Timestamp (tag 5979-RequestTime)
To provide more transparency between iLink order entry and MDP 3.0 market data, iLink supports a FIX tag 5979-RequestTime on all Convenience Gateway (CGW) and Market Segment Gateway (MSGW) sessions.
...
- Execution Report: Order Creation, Cancel, or Modify (tag 35-MsgType=8, tag 39-OrdStatus=0, 4 or 5)
- Execution Report: Fill Notice (tag 35-MsgType=8, tag 39-OrdStatus=1 or 2)
- Execution Report: Trade Cancel (tag 35-MsgType=8, tag 39-OrdStatus=H)
- Execution Report: Order Elimination (tag 35-MsgType=8, tag 39-OrdStatus=4 or C
- Execution Report Order Status Request Acknowledgment (tag 35-MsgType=8, tag 150-ExecType=I)
- Execution Report: Reject (tag 35-MsgType=8, tag 39-OrdStatus=8)
- Order Cancel/Replace Reject (tag 35-MsgType=9, tag 434-CancelRejResponseTo=2)
- Order Cancel Reject (tag 35-MsgType=9, tag 434-CancelRejResponseTo=1)
- Order Mass Action Report (tag 35-MsgType = BZ)
- Quote Acknowledgement Acknowledgment (tag 35-MsgType=b)
- Quote Reject (tag 35-MsgType=b, tag 297-QuoteAckStatus =5)
- Quote Cancel Acknowledgement Acknowledgment (tag 35-MsgType=b, tag 297-QuoteAckStatus=1, 3, 4 or 5 without tag 9775-UnsolicitedCancelType)
- Only for Solicited Quote Cancel
...
Info |
---|
To ensure the 5979 timestamp never reflects an out-of-sequence event, in certain cases CME Globex will increment timestamp value. These forced timestamps still accurately reflect the sequence of events on the MSGW. |
iLink Unsolicited Outbound Message Scenario
For unsolicited outbound messages where there are no iLink inbound messages, tag 5979 will represent the time at which the transaction is processed on the trading engine in nanoseconds.
...
- the iLink tag 60 value will be derived from iLink tag 5979-RequestTime, but represented in the existing UTC format with millisecond precision.
- MDP 3.0 tag 60 timestamp is sent in number of nanoseconds since the Unix epoch synced to a master clock to microsecond accuracy.
Testing and Certification
...
- .
New Release Weekly Failover Testing Windows
Market Segment ID (tag 1300) | Market Segment Description | Date | Time |
---|---|---|---|
54 | CME Equity options | Tuesday and Thursday | 11:00 pm CT - MSGW failover to backup component 11:30 pm CT- MSGW failover to primary component |
70 | CME Commodity Futures | Tuesday and Thursday | 9:00 am CT - MSGW failover to backup component 9:30 am CT - MSGW failover to primary component |
84 | CBOT Treasury Futures | Tuesday and Thursday | 11:00 pm CT - MSGW failover to backup component 11:30 pm CT - MSGW failover to primary component |
An SFTP site (sftpng.cmegroup.com), accessed via a CME Globex network direct connection, is used to disseminate the MSGW configuration information. The MSGW Configuration allows client systems to receive the list of all market segments and MSGW IPs. This SFTP site contains the configuration files for all environments. The SFTP site is a secure site that requires a user name and password for access.
Table Key:
Note: The Autocert+ tool will use the NR MSGW config file.