CME STP on Google Cloud

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

Revision History

Date

Description

Date

Description

November 1, 2024

Replaced Failover with Google Cloud Regions and Resiliency

August 9, 2024

Updated details on Certain IDs, timestamps, and trade ordering "The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments.  Additionally, the trade ordering may not match between the current and GC hosted environments."

Updated operations in regions "CME STP FIXML will operate in multiple GC regions. In the event of a GC failover, there will be no lag in RTO time. Clients can continue to connect to the same URL on GC as they were connected prior to the failover. If a failover occurs, clients will receive the following error message response to their next polling request indicating that they must resubmit their subscription request to the API."

Updated definition of TrdCaptRpt/@LastUpdateTm "Updated definition for The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments.  Additionally, the trade ordering may not match between the current and GC hosted environments."

June 5, 2024

Initial publication of client impact topic.

Key Events and Dates

Date

Milestone

Date

Milestone

Thursday, June 20, 2024

New Release

  • CME STP FIXML API

Sunday, July 28, 2024

Production

  • CME STP FIXML API

Sunday, November 3, 2024

Expected Client Completion

  • CME STP FIXML API 

TBD

New Release / Production / Expected Client Completion

  • CME STP FIX API

  • CME STP Trade View application

CME STP FIXML API on Google Cloud

Onboarding

CME STP FIXML on Google Cloud will not require separate or additional client 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 clients do not need to make any changes.

Testing and Certification

Clients that have previously certified their systems are not required to perform a new certification.

CME Group recommends that clients test CME STP functionality with the Google Cloud instance.

Connectivity

New Release Environment

Connectivity Type

Asset Class

Current Service URL

New Service URL (GC)

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)

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, clients can view the same trade information from both endpoints. 

The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments.  Additionally, the trade ordering may not match between the current and GC hosted environments.

During the parallel period, the 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.

Google Cloud Regions and Resiliency

CME STP FIXML will operate in two GC regions, Eastern and Central United States. Client systems will connect to the same service URL, regardless of which region is active.

Clients should note that the x-cme-token, which is used by client systems for ongoing subscriptions and for multi-batch queries, will not be valid across regions and will receive a TradeCaptureReportRequestAck with the attribute @txt="x-cme-token is no longer valid. Please initiate a new subscription." upon regional failover.

Information related to Subscriptions and queries, which includes Token management and duplicate message detection is available in CME STP FIXML Core.

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 Google Cloud, 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, client permissions, or available services or behaviors.




How was your Client Systems Wiki Experience? Submit Feedback

Copyright © 2024 CME Group Inc. All rights reserved.