Find
Apr 08, 2014

Eurex

Eurex Exchange’s T7: Mandatory installation of Java Runtime Environment 1.7 required for Release 2.1 production introduction

As previously announced in Eurex Exchange’s T7 Release 2.1 release announcement (Eurex Circular 276/13) and the accompanying Release Notes for T7 Release 2.1, the installation of Java Runtime Environment (JRE) 1.7 on the participants’ side is mandatory. Participants must therefore ensure that they have installed the necessary JRE 1.7 version prior to the production launch of Eurex Exchange’s T7 Release 2.1 on 12 May 2014.

From T7 Release 2.1 onwards, the Eurex T7 Trader GUI and Eurex T7 Admin GUI make use of features only provided with JRE 1.7 and therefore the usage with older JRE versions will no longer be possible. In the event that the correct JRE version is not installed, the respective Eurex T7 Trader GUI and Eurex T7 Admin GUI will not start and the corresponding error message will be displayed. Please also be aware that Oracle also terminated support (including provision of security updates) for all JRE 1.6 versions in February 2013.

For more details on the minimum and recommended JRE 1.7 versions, please refer to the document “Eurex Trader GUI & Eurex Admin GUI - Installation Manual” which is available for download on the Eurex website under:

Technology > Eurex Exchange’s T7 > System documentation > Release 2.1 > Eurex GUI Solutions

If you have any questions or require further information, please contact your Trading & Clearing Services Key Account Manager.

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.