Failover from Primary to Backup Components

The following instructions illustrate the process to run and complete tests for Failover from primary to backup Components.

• To select the test:

1. Select a SenderComp from the drop-down and select ASSIGN if not already assigned.

2. From the Test Suite tab, select from the following linked tests then proceed to the specific instructions.

• Failover from primary to backup components (Binding without Initialization) for Pre-Registered / On-Demand Format
• Failover from primary to backup components (Initialization and Binding) for Pre-Registered / On-Demand Format

3. Use the Instrument(s) drop down menu to choose an instrument and channel and click SELECT.
4. Click the START TEST button.

Note:DO NOT select the START TEST button once the test is in progress.
If a test is not proceeding to the next step, clicking the Refresh button () below the test steps may resolve the issue.

Referential information is included for messages sent / received during the test.

Failover from Primary to Backup - Binding without Initialization

• To run the Failover from primary to backup components (Binding without Initialization) for Pre-Registered / On-Demand Format test:

The purpose of this test is to verify that the client system can recover and continue to function properly during the primary gateway failover by re-establishing the connection to new primary gateway without re-initialization.

Note: Due to the assisted failover setup needed for repeatable conditions during certification, failover of gateway components takes a few seconds. It is necessary, only for the purposes of these certification tests, to wait a few seconds before attempting a connection to the newly promoted primary gateway.

Note: This test is used for both Pre-Registered and On-Demand formats. The above image shows the Pre-Registered version of the test.

1. Over a primary iLink connection, submit an Establish message to bind the connection.
2. Receive and process Establishment Acknowledgment.
3. Submit a Sequence message.
4. Receive and process a Sequence message.
5. Submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)] on a primary iLink connection.
6. Receive and process Execution Report - New Order message (35=8, 39=0) on a primary iLink connection.
7. Submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)] on a primary iLink connection.
8. After few seconds, re-connect to the newly promoted primary, submit an Establish message.
9. Receive and process Establishment Acknowledgment.
10. Submit a Retransmit Request message on newly promoted primary and receive and process any resent messages.
11. Did your system successfully receive and process the Execution Report(s) from the Retransmit Request?

Select Yes/No.

12. After the market open, submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)].
13. Did your system properly receive and process the execution report?

Select Yes/No.

14. Submit a Sequence message.
15. Receive and process a Sequence message.
16. Submit a Terminate message.
17. Receive and process a Terminate message.

The selected session will revert to the previous primary gateway after few seconds.

back to top

Failover from Primary to Backup - Initialization and Binding Test

• To run the Failover from primary to backup components (Initialization and Binding) for Pre-Registered Format test:

The purpose of this test is to verify that the client system can recover and continue to function properly during the primary gateway failover by re-initializing and re-establishing the connection to new primary gateway.

Note: Due to the assisted failover setup needed for repeatable conditions during certification, failover of gateway components takes a few seconds. It is necessary, only for the purposes of these certification tests, to wait a few seconds before attempting a connection to the newly promoted primary gateway.

Note: This test is used for both Pre-Registered and On-Demand formats. The above image shows the Pre-Registered version of the test.

1. Over a primary iLink connection, submit a Negotiate message using new UUID (tag 39001) to initialize the connection.
2. Receive and process a Negotiation Response message.
3. Submit an Establish message to bind the connection.
4. Receive and process Establishment Acknowledgment.
5. Submit a Sequence message.
6. Receive and process a Sequence message.
7. Submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)] on a primary iLink connection.
8. Receive and process Execution Report - New Order (35=8, 39=0) message on a primary iLink connection.
9. Submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)] on a primary iLink connection.
10. After few seconds, re-connect to the newly promoted primary.
11. Submit a Negotiate message using new UUID (tag 39001) to re-initialize the connection.
12. Receive and process a Negotiation Response message.
13. Submit an Establish message to bind the connection.
14. Receive and process an Establishment Acknowledgment.
15. Submit a Retransmit Request message on newly promoted primary and receive and process any resent messages.
16. Did your system successfully receive and process the Execution Report(s) from the Retransmit Request?

Select Yes/No.

17. After the market open, submit a Limit Day / FAK Order [35=D (tag 40-OrdType=2, tag 59-TimeInForce=3)].
18. Did your system properly receive and process the execution report?

Select Yes/No.

19. Submit a Sequence message.
20. Receive and process a Sequence message.
21. Submit a Terminate message.
22. Receive and process a Terminate message.

The selected session will revert to the previous primary gateway after few seconds.

back to top