Find
Aug 08, 2012

Eurex

Eurex Exchange’s New Trading Architecture: Ordering of sessions for the Enhanced Trading Interface and FIX Gateway, Upload of public keys for the Eurex Trader GUI and Eurex Admin GUI

Eurex Exchange will introduce its new trading architecture on December 3, 2012. Prior to the production launch, the first simulation phase will commence from September 3, 2012.

Eurex Exchange’s new trading architecture will provide two session-based interfaces, the Eurex Enhanced Trading Interface (Eurex ETI) and the Eurex FIX Gateway. In addition, two new graphical user interfaces (Eurex Trader GUI and Eurex Admin GUI) will be provided.

To interact with the Eurex ETI and Eurex FIX Gateway interfaces, trading participants are required to order new sessions via the “Requests & Configuration” option in the “Technical Connection” section of the Eurex Member Section. Eurex ETI supports two different session types: high-frequency (HF) and low-frequency (LF) sessions. Both session types differ in throughput limit and functionality.

The Eurex FIX Gateway also supports two types of FIX sessions: trading and back-office FIX sessions. Separate FIX sessions are required to access products on the existing system and on the new trading architecture.

For additional security purposes, participants using either of the graphical user interfaces via internet connectivity are also required to upload public keys via the “Eurex Exchange GUIs” option in the “Technical Connection” section of the Eurex Member Section.

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.