The following section describes Clearing Disaster Recovery (DR) environment processing for CME Group front-end Clearing applications.
...
Through CME ClearPort, a front-end clearing application that offers a set of flexible clearing services open to OTC market participants, customers can write trades directly into the CME ClearPort API or submit trades for clearing via a web-based graphical user interface.
| Noteinfo |
|---|
Note: CME ClearPort disaster recovery events are handled in the same manner regardless of whether customers submit trades via the web-based GUI or the ClearPort API. |
Normal Production Processing Environment
The following figure illustrates a normal CME ClearPort production processing environment.
| Noteinfo |
|---|
Note: CME ClearPort is a web-based application, and therefore the environment to which you connect (production vs. disaster recovery) is transparent to the user. |
...
GCC dispatches DR-related messages to the email addresses provided by customers when creating their CME ClearPort IDs. These messages are provided to ClearPort users regardless of whether they are currently logged into ClearPort.
| Noteinfo |
|---|
Note: Disaster event messages are not routed to the CME ClearPort front end. |
Recovery Time Frames
As designated in the related Service Level Agreement (SLA), CME Group attempts to resolve CME ClearPort disaster recovery events within a 2 hour time frame. Once CME Group determines the event has been resolved and CME Aurora is available, ClearPort users must re-enter their login.
...
When the CME Aurora environment is unavailable and the CME NYDC environment has been established, CME ClearPort users can log directly into CME NYDC using their CME Aurora login credentials.
| Noteinfo |
|---|
Note: The disaster recovery environment offers all the same functionality as the production environment. |
...