CME Straight-Through Processing (CME STP) services for CME STP FIXML, CME STP FIX API and CME STP Trade View will be hosted on Google Cloud (GC).
Contents
Table of Contents maxLevel 23
Revision History
| Date | Description |
|---|---|
| June 5, 2024 | Initial publication of client impact topic. |
Key Events and Dates
| Date | Milestone |
|---|---|
| Thursday, June 20, 2024 | New Release
|
| Sunday, July 28, 2024 | Production
|
| Sunday, November 3, 2024 | Expected Client Completion
|
| TBD | New Release / Production / Expected Client Completion
|
CME STP FIXML API on Google Cloud
Onboarding
CME STP FIXML on Google Cloud will not require separate or additional customer onboarding.
Authorization and Entitlement
- Clients can continue to use existing API IDs.
- CME STP FIXML will continue to use Basic Authorization.
- Entitlement will be handled internally by CME Group so that customers do not need to make any changes.
Testing and Certification
Customers that have previously certified their systems are not required to perform a new certification.
| Info |
|---|
CME Group recommends that customers test CME STP functionality with the Google Cloud instance. |
Connectivity
New Release Environment
| Connectivity Connectivity Type | Asset Class | Current Service URL | New Service URL (GC) |
|---|---|---|---|
Internet (only) URL uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required. | All | https://servicesnr.cmegroup.com/cmestp/query | https://posttrade.api.uat.cmegroup.com/cmestp/query |
Production Environment
Connectivity Type | Asset Class | Current Service URL | New Service URL (GC) |
|---|---|---|---|
Internet URL uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required. | All | https://services.cmegroup.com/cmestp/query | https://posttrade.api.cmegroup.com/cmestp/query |
CME STP FIXML uses x-cme-token HTTP variable for continuation of queries and subscriptions. Tokens are valid only for the service (current / GC) in which it was issued.
Both service URLs will be available in parallel. During this period, customers can view the same trade information from both endpoints.
Certain IDs, timestamps, and trade ordering may not match between the current and GC hosted environments.
| Info |
|---|
During the parallel period, same trade data will be available on both services. Clients should take steps to avoid double booking trades within their systems. |
CME STP FIXML API Differences
There will be no changes to the CME STP FIXML server and client message payload.
Failover
In the event of an outage, CME STP FIXML will fail over automatically, with an Recovery Time Objective (RTO) commitment of two hours.
Due the nature of cloud architecture, GC failover scenarios are more likely but recovery is faster.
CME STP FIXML will operate in multiple GC regions. In the event of a GC failover, there will be no lag in RTO time. Customers can continue to connect to the same URL on GC to they were connected prior to the failover. If a failover occurs, customers will receive an error message response to their next polling request indicating that they must resubmit their subscription request to the API.
Customer recovery processes are similar to existing processes with the key difference that CME STP FIXML will always be available. Customers should ensure they have a solution in place to understand and respond to an error message notifying them to resubmit their API subscription request.
CME STP FIX API on Google Cloud
Details will be provided when available.
CME STP Trade View Application on Google Cloud
The CME STP Trade View will be available on GC, at a date to be announced. Applications functions will not change, however, previously created user profiles will not migrate and must be recreated. There will be no change to how CME STP Trade View is accessed, customer permissions, or available services or behaviors.