This topic describes client impacts for CME STP FIX API on Google Cloud.

Contents

CME STP FIX on Google Cloud will not require separate or additional client onboarding. 

• 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.

CME STP FIX on Google Cloud message recovery certification is required. To initiate certification, client systems should connect to Hostname: autocertstpfix.api.uat.cmegroup.com and Port: 443. For questions, contact Certification Support for Electronic Trading (CSET).

This section outlines CME STP FIX connectivity on Google Cloud.

The CME STP FIX service in New Release is accessible via the internet through the below referenced managed and regional connectivity options. Client systems are required to target the referenced hostname(s).

The New Release environment is used for testing new products and functionality prior to production launch.

• View new release environment Connectivity details (CME Group Login required) for Hostname, IP’s and Ports for managed and regional connectivity.

This section describes enhanced connectivity options for CME STP FIX on Google Cloud compared to the current On-Prem connectivity.

These additional CME STP FIX hosts on Google Cloud will be available in parallel to the current On-Prem host.

During the parallel availability, the same trade data will be available on both On-Prem and Google Cloud hosts. Clients should take steps to avoid double booking trades within their systems.

CME STP FIX on Google Cloud will operate in two regions, Eastern and Central United States.

To ensure that server certificate names match client requests, CME STP FIX host servers use certificates signed by a trusted Certificate Authority (CA). Client systems rely on standard certificate validation and additional certificates are not required.

The hostnames are publicly discoverable on the internet. Client systems must target the hostnames.

View CME STP FIX API on Google Cloud - Internet Connectivity (CME Group Login required) for Hostname, IP’s and Ports.

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 and options.

CME STP FIX host servers use certificates signed by an official trusted Certificate Authority (CA). Client systems establishing TCP/IP connections should use Transport Layer Security (TLS) 1.2. Clients should use the hostnames with Server Name Indication (SNI) extension during TLS handshake to ensure they can start and keep a session to CME STP FIX.

Clients have two different connectivity (transport) options: managed and regional.

With Managed Connectivity option, Clients only need to connect to a single publicly resolvable service host for all STP data that they are entitled to. CME Group manages regional connectivity.

View CME STP FIX API on Google Cloud - Managed Connectivity (CME Group Login required) for Hostname, IP’s and Ports.

With Regional Connectivity option, clients can connect to both regions in parallel or switch connections between regions individually, providing flexibility and redundancy. View CME STP FIX API on Google Cloud - Regional Connectivity for this service (CME Group Login required).

There will be no changes to the CME STP FIX server and client message payload. 

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.

Please see more details in CME STP FIX Session Layer topic.

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)