Modernization of C7 FIXML Interface: Update to Eurex Clearing Circular 085/24 

With this circular, Eurex Clearing announces the modernization of C7 FIXML Interface as an update to Eurex Clearing Circular 085/24 under 3. Details of the initiative regarding Connection Test and Fallback Approach.

1. Introduction 
 
Eurex Clearing is committed to providing a reliable and secure clearing environment. As part of this ongoing effort, Eurex Clearing will update the C7 FIXML interface. This update will involve two key improvements: 

• Enhanced Technology: Java Runtime Environment version 17 is now supported, offering improved performance and stability.
• Strengthened Security: The Deutsche Börse Public Key Infrastructure (PKI) will be used for a more robust security posture.  

2.   Required action
  

The migration to the new process is scheduled for Q2 2025: 

•  23 May 2025: The new process will be mandatory for testing in the SIMU environment. 
•  14 June 2025: The new process will be mandatory in the PROD environment.  

The migration will follow a cut-over approach, with no parallel run available.
  

Eurex Clearing recommends Clearing Members to prepare for the required actions and review the documentation and video tutorials available on the Support page on the Eurex website www.eurex.com under the link:  
 
Support > Technology > C7 > Supporting Documents > Messaging Interfaces Connectivity
  

Clearing Members can contact their dedicated Technical Key Account Manager in case of any questions.  

3.   Details of the initiative 
 

• New Self-Certification Process: A new self-certification process for the C7 FIXML interface will be established. Clearing Members can find detailed instructions in the "Eurex Clearing Messaging Interfaces Connectivity A: Connectivity" document, available for download on the above-mentioned Eurex Support page under Supporting Documents. All Clearing Members are required to create new accounts and generate new certificate via self-service in new title in the Member Section as described in the reference documentation. Participants should NOT delete the accounts on the current FIXML Broker on Migration date to ease fallback, in case this is required.  The deletion will be done on the Member Section of Deutsche Börse AG, when the migration is completed by all participants. 

Additionally, video tutorials will be available on the Eurex website for clear guidance under: Support > Technology > C7 >Tutorial Videos. 

• Java 17 Compatibility: Java version 17 does not support certain elliptic curves. A complete list of the obsolete ciphers is available here: JDK-8251547. Clearing Members who are using Java 17 must ensure that their systems avoid these ciphers. The supported cipher suite is mentioned in Eurex Clearing Messaging Interfaces Connectivity guide. 
• Host Names and Port Numbers: Clearing Members must use the host name and port number of their FIXML broker.  Please refer to the table below for quick reference:  
   

Clearing Members will be contacted by their TKAM if their port number or migration timeline differs. 
 

• Connection Test: The New FIXML certificates can be verified before the Migration Date. We advise doing this test up to two weeks prior to Migration Day. If the certificate is not correct, clients will receive SSL or TLS error. If certificate is correct, then connection will be denied with the following statement: 

Permission PERFORM_ACTION(connect) is denied for : VirtualHost 'default' on VirtualHostNode 'default' [condition = amqp:not-allowed] 
 

On Migration days participants are requested to test connectivity and confirm via email.  A Migration will be performed regardless of any positive feedback.   
 

As Clearing activities in Production environment are only possible on Monday morning, we also advise to monitor interaction via FIXML in the early morning hours and to report issues as soon as possible. In this case a fallback to the current FIXML Broker is possible. More details will follow in the next chapter.
 

• Fallback Approach: We prepare for two possible fallback scenarios in production environment (fallback is not foreseen in simulation environment).  

a.    The first scenario covers fallback to current FIXML Broker on Migration Day. In case of a unsuccessful connection test when issues cannot be resolved on that day, a fallback to the current FIXML Broker will be initiated.

b.    In the unlikely event of having unresolvable issues with the New FIXML Broker even after successful connection test, the rollback to the Classic Broker will be performed. In this scenario, messages which will be already sent via New FIXML Broker, can be resent to the current FIXML Broker. However, the message sequence of resent messages will not be in chronological order. Please contact you TKAM in case your software has a known limitation with consuming messages out of sequence. 
 

It is strongly advised to perform regular activities in production environment early that day to ensure smooth operations and to reduce the number of messages in the event of a rollback. Support is available, in case issues need to be resolved. 
 
Unless the context requires otherwise, terms used and not otherwise defined in this circular shall have the meaning ascribed to them in the Clearing Conditions or FCM Clearing Conditions of Eurex Clearing AG, as applicable. 
 

Further information