...
The following figure illustrates a normal CME ClearPort production processing environment.
| Info |
|---|
CME ClearPort is a web-based application, and therefore the environment to which you connect (production vs. disaster recovery) is transparent to the user. |
...
Using an automated messaging tool, the CME Group Global Command Center (GCC) uploads a list of CME ClearPort contacts. The CME ClearPort team provides GCC management with text explaining the disaster event, and that text is reviewed, edited (if necessary), approved, and dispatched to the email addresses associated with the contact list.
...
The following rules apply when transitioning to the DR environment:
The URL by which ClearPort users connect to the CME ClearPort Login page (https://services.cmegroup.com/cpc/) is set for Global load balancing. Therefore, users are dynamically redirected from CME Aurora to CME NYDC during DR testing.
ClearPort users must log into CME NYDC after being redirected.
CME NYDC and CME Aurora offer the same functionality to ClearPort users.
ClearPort customers using an IP, such as CME Aurora IP 164.74.122.29, would (for example) have to connect to CME NYDC IP 204.10.15.11 during DR testing.
CME NYDC must be brought up after a DR event prior to the redirect from CME Aurora.
Trades that are in-flight at the time of a DR event must be re-submitted in the DR environment.
When hard coding to an IP Address, you will not have the benefit of auto-recovery via the CME NYDC, but must instead manually point to the CME NYDC.