Archive

T7 Release 8.1

Eurex introduced T7 Release 8.1 in June 2020. An overview of the release content relevant for Eurex Trading Participants is available on this website. Expiry-dependent TES attributes, Eurex EnLight SMART trading capabilities, Eurex EnLight anonymous request and response, Mandatory PIN procedure for Trading on Behalf and other inquiries, Equity Bespoke Baskets, TES auto approval rules for clients, were the integrated functional enhancements by Eurex. 

Eurex provides a dedicated release simulation environment to give Trading Participants and Independent Software Vendors (ISVs) the opportunity to perform comprehensive testing. T7 Release 8.1 is available via the T7 Cloud Simulation since 6 April 2020. The T7 Cloud Simulation allows to test against the current T7 production and simulation software versions. For more information on the T7 Cloud Simulation, please refer to the T7 Cloud Simulation website.

Simulation start:   4 May 2020
Production start: 29 June 2020

System Documentation

Eurex Enhanced Trading Interface

Eurex FIX Gateway

  • T7 FIX Gateway FIX 4.2 and 4.4 Manual v.8.1
    Publication date: 15 Jun 2020
    The document provides information on the T7 FIX Gateway for both the Cash and Derivatives Markets and contains a detailed description of the concepts and messages used by the interface. This document describes the FIX 4.2 and 4.4 versions of the interface.
  • T7 FIX Gateway - Repository v.8.1
    Publication date: 15 Jun 2020
    The FPL (FIX Protocol Language) repository contains the XML representation of the T7 FIX Gateway version 4.2 and 4.4 for both the Cash and Derivatives markets.
  • T7 FIX Gateway - Fiximate v.8.1
    Publication date: 15 Jun 2020
    The package provides a browser-based representation of the repository for the T7 FIX Gateway versions FIX 4.2 + FIX 4.4 for both the Cash and Derivatives markets with navigation capabilities.

Eurex Trader and Admin GUI


  • T7 Disaster Recovery Concept 2020 - Interface Configuration Details
    Publication date: 04 Sep 2020
    This document provides an overview of Deutsche Börse’s disaster recovery concept for the T7 trading system. It contains the required technical background information as well as functional features and limitations to enable participants to continue trading in a DR situation.
  • N7 Network Access-Guide v2.0.55
    Publication date: 15 May 2020
    This document provides details on the network access options for T7 and Eurex Clearing's interfaces. It includes detailed technical background information, such as router equipment information and port numbers for the configuration of firewalls.

  • T7 Incident Handling Guide v.4.6
    Publication date: 30 Jul 2020
    This document provides a detailed description of the reaction of Deutsche Börse's T7 trading system to technical incidents and provides best practices for handling them. In addition the document provides references to the respective focus days in the T7 simulation environment which are intended to simulate such incidents. 

Circulars

Mandatory PIN procedure for Trading on Behalf and other inquiries

As part of the T7 Release 8.1 Eurex introduced the mandatory user attribute PINCode on 3 August 2020. This mandatory PIN authentication procedure applies for Trading on Behalf (ToB) and further inquiries and aims to improve the identification of requesting Exchange Participants. Newly set up Eurex users will thus require a dedicated PINCode upon T7 Release 8.1. Those Eurex user set ups that have been performed prior to T7 Release 8.1 are valid without the PINCode only until the mandatory PIN procedure is enforced.

Eurex Market Supervision enforced the mandatory PIN identification process starting Monday, 3 August 2020. All Eurex users are required to have a dedicated PIN and every requesting Exchange Participant must provide the PIN to Eurex Market Supervision for:

  • On-exchange on-behalf entries (order add / modify / delete / mass deletion)
  • TES on-behalf entries (trade add / approve / modify / delete)
  • Stop / Release User / Business Unit inquiries

In case the required authentication information is not provided effective Monday, 3 August 2020, Eurex Market Supervision will reject above mentioned inquiries. Therefore, it is crucial that all Eurex users should be aware of their PIN and know where to find it.

Please also keep in mind that all Eurex Exchange Participants are asked to review their internal escalation and compliance processes to incorporate potential changes to adhere to the new identification process due to the mandatory PIN procedure. Eurex user administrators should set up PINs for all Eurex users and directly communicate those to the individual traders in alignment with the internal departments and processes of the Exchange Participant.

For further details on ToB please refer to the following documentation

In case of any questions or your require further information, please contact us at client.services@eurex.com

Are you looking for information on previous releases? We have stored information about our previous releases in our Archive for you!

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.