F7 Trading System
29 Feb 2024

Eurex Repo F7 simulation v4.1 update

The Eurex Repo F7 simulation environment will close down at noon CET on Thursday, March 7th, 2024 for the update to F7 release 4.1. 


Eurex Repo will conduct internal tests on March 8th and the 4.1 Simulation period will commence starting Monday, March 11th 2024. With the start of the business day on Monday, March 11th the software version for Repo F7 simulation will be 004.130.000.

Release 4.1 is an internal upgrade focusing primarily on technical infrastructure and security. There are only minor F7 GUI enhancements and no changes to the F7 API or the F7 FIX Gateway that affect F7 customers.

For an overview of all details of Release 4.1 please view the document "F7 4.1 Release Notes" which has been published in the DBAG Member Section.


F7 GUI users are strongly recommended to clear the browser cache after the release introduction, to ensure that the newly introduced GUI functionalities behave correctly. 


The only acceptable API version number remains 4.0.


There are no changes to Eurex Repo Trading Interfaces in Relesae 4.1. F7 API, FIX Gateway and MTX documentation from Release 4.0 remains valid for Release 4.1


F7 system documentation for Repo F7 is available at: Deutsche Börse Member Section https://membersection.deutsche-boerse.com/


Resources > Eurex Repo > System Documentation 


Please note: while the F7 Simulation system is already on release 4.1, the F7 Advanced Simulation remains on the same software version as the F7 Production system: release 4.0.
 

Market Status

XEUR

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message. 

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.

An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.