Logon Process with Failover

The purpose of this test is to verify that client system can support primary gateway enforcement.

In the event of a Drop Copy 4.0 failover, upon logon to the new primary connection, client systems will experience a significant increase (currently set to 4000) in sequence numbers (tag 34-MsgSeqNum) sent from CME Globex to the client system. CME Group recommends that client systems request all missing messages.

For all Resend Requests, the client system can request no more than the maximum limit of 2500 messages. To recover any missed in-flight messages beyond the 2500 message range, the client system must submit multiple Resend Request (tag 35-MsgType=2) messages.

In response to the Resend Request from the client system, Drop Copy 4.0 will respond with a Gap Fill for all Administrative messages and send tag 35-MsgType35=n with tag 43-PossDupFlag=Y for business messages.

 

Additional Drop Copy Information

See the following documentation for more information on Drop Copy functionality:

• Drop Copy Impacts - iLink 3 Binary Order Entry
• Drop Copy Service for iLink - BrokerTec Markets
• iLink 3 Binary Order Entry - BrokerTec Markets
• iLink 3 FIX Tag Library
• iLink 2 FIX Tag Library

 

1. To run a Logon Process with Failover test:

1. Select a SenderComp from the drop-down and select ASSIGN if a SenderComp is not already assigned.
2. Select the START TEST button.

Note: DO NOT select the START TEST button once the test is in progress.

3. Over the Drop Copy connection, submit a Logon (35=A) message.
4. Over the Drop Copy client application, submit a Logon (35=A) message on the backup gateway.
5. Receive and process a Logon (35=A) confirmation message.
6. Submit a Resend Request (35=2) message(s).
7. Receive a Gap Fill (35=4,123-GapFillFlag=Y) message(s).
8. Submit a Heartbeat (35=0) message.
9. Receive and process a Heartbeat message.
10. Submit a Heartbeat message.
11. Submit a Logout (35=5) message.
12. Receive and process a Logout (35=5) confirmation message.