CME STP FIX API on Google Cloud
- Space Sync for Confluence
This topic describes client impacts for CME STP FIX API on Google Cloud.
Revision History
Date | Description |
|---|---|
Wednesday, November 20, 2024 | Initial publication of client impact topic. |
Key Events and Dates
Date | Milestone |
|---|---|
Wednesday, January 8, 2025 | New Release |
Sunday, February 16, 2025 | Production Launch |
Onboarding
CME STP FIX on Google Cloud will not require separate or additional client onboarding.Â
Authorization and Entitlement
Clients can continue using existing CME STP FIX API IDs.
Entitlements will be handled internally by CME Group, clients do not need to make any changes.
Testing and Certification
Certification requirements will be determined and announced at a future date.
CME Group recommends that clients test CME STP functionality with the Google Cloud instance.
Connectivity
This section outlines CME STP FIX connectivity on Google Cloud.
New Release EnvironmentÂ
Connectivity Type | Asset Class | Current Service URL | New Service URL (GC) | Port |
|---|---|---|---|---|
Internet (only) URL uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required. | All | fixstpnr.cmegroup.com | stpfix.api.uat.cmegroup.com | 443 |
Production Environment
This section describes enhanced connectivity options for CME STP FIX on Google Cloud compared to the current connectivity.
In the production environment CME STP FIX will operate in two regions, Eastern and Central United States.
Internet Connectivity
Clients have two different options of internet connectivity to CME STP FIX on Google Cloud.
Connectivity Option | URL | Usage |
|---|---|---|
Option 1 | stpfix.api.cmegroup.com | Clients only need to connect to a single service URL for all STP data that they are entitled to. CME Group will manage regional connectivity. |
Option 2 | stpfix-a.api.cmegroup.com stpfix-b.api.cmegroup.com | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. |
Service URL's use certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.
Dedicated line Connectivity
Clients who are on one of the specific Production Connectivity Options offered by CME Group can use CME STP FIX on their connectivity option using the below server destinations.
If clients cannot use a public DNS on their side, they should deploy a local DNS override (i.e. host-file entry). This will ensure that the server certificate name will match up with client requests and they can rely on standard certificate validation.
Connectivity Type | Asset Class | New Service URL (GC) - Region-a | New Service URL (GC) - Region-b | Usage | Port |
|---|---|---|---|---|---|
Dedicated connectivity - Futures and Options clients | All | stpfix-ll-fo-a.api.cmegroup.com (208.112.160.2) | stpfix-ll-fo-b.api.cmegroup.com (208.112.144.2) | Clients can connect to both regions in parallel providing flexibility and redundancy. Clients can subscribe to same or different STP trade data across regions based on their entitlements. Sequences of messages are not guaranteed to be the same across regions. | 443 |
Dedicated connectivity - BrokerTec FI clients | All | stpfix-ll-btec-a.api.cmegroup.com (208.112.164.2) | stpfix-ll-btec-b.api.cmegroup.com (208.112.148.2) | ||
Dedicated connectivity - EBS FX clients | All | stpfix-ll-ebs-a.api.cmegroup.com (208.112.168.2) | stpfix-ll-ebs-b.api.cmegroup.com (208.112.152.2) |
Service URL's use certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.
Irrespective of which Google Cloud URL is used, available trade data for a FIX session is determined by the entitlements of the API ID used by the client system.
Example: Client systems connecting to stpfix-ll-btec-a.api.cmegroup.com can receive Futures, Options and/or EBS FX trades if their API ID is entitled for those markets.
During the parallel period, the same trade data will be available on both current and new service URL's. Clients should take steps to avoid double booking trades within their systems.
CME STP FIX API Differences
There will be no changes to the CME STP FIX server and client message payload.Â
Automatic TCP/IP Disconnection
Client systems TCP/IP connectivity to Google Cloud Internet instances of CME STP FIX will be disconnected 24 hours from when the connection is established.
Dedicated connectivity clients are not expected to be affected by the 24 hour disconnect.
Regardless of the connectivity options used, Client systems are expected to reconnect, reestablish their FIX session and initiate a subscription when disconnected.
Google Cloud Regions and Resiliency
Information related to Session Layer Management, Trade Snapshot and Subscriptions including restarting a subscription along with duplicate message detection is available in CME STP FIX Core.
CME STP FIX requires clients to reset both outbound and inbound sequence number on establishing a FIX session using tag 141-ResetSeqNumFlag="Y" on their logon request.
When client systems detect a lost connection or session that is established with CME STP FIX, they are expected to login to reestablish the session and restart a new subscription.
Contact Information
For technical development support, contact Certification Support for Electronic Trading (CSET).
For production requests, contact the Global Command Center (GCC).
For all other inquiries, contact Global Account Management (GAM).
How was your Client Systems Wiki Experience? Submit Feedback
Copyright © 2024 CME Group Inc. All rights reserved.