Eurex
1. Introduction
On 1 February 2021, Eurex introduced its redesigned “Member Section” client portal. With a new look and the intention to offer new features and a continuously enhancing user experience, a “release version” strategy is now introduced. This will provide more transparency on improvements.
With this circular, Eurex announces the introduction of the next Member Section enhancements: Member Section Release 2.3, which will go live on Monday, 12 July 2021.
We would like to inform you that all upcoming changes within the Member Section will be introduced with "Releases". The following table shows all releases already implemented or planned for 2021 so far:
Please note that Member Section Releases 2.1 and 2.2 did not impact Trading Participants.
The Member Section Release 2.3 focuses on components of the Technical Connection. The following changes and enhancements will be introduced with Release 2.3:
Production start: 12 July 2021
All information related to this release, i.e. FAQs, guides, tutorial videos, will be made available in due course on the Eurex Support website for Member Section Release 2.3 under the following path:
Support > Initiatives & Releases > Member Section Releases > Release 2.3
2. Required action
Trading Members, Multi-Member Providers and ISVs are requested to get familiar with the new structure and design of the Member Section interface as well as the changes described under item 3.B.
Please note that login details for the Member Section as well as uploaded certificates/keys will not change with the introduction of Release 2.3.
3. Details
A. Implementation and communication schedule for Member Section Release 2.3
The production launch of the Member Section Release 2.3 is planned for 12 July 2021. Eurex is committed to informing the users about the changes introduced with this new release in order to support adequate planning and to ensure a successful migration. All documentation and tutorial videos will be published in the upcoming weeks on the dedicated Eurex Support website for Member Section Release 2.3 under the following path:
Support > Initiatives & Releases > Member Section Releases > Release 2.3
B. Overview of functional enhancements
This section provides an overview of the enhancements, which will be introduced with the Member Section Release 2.3:
Improved navigation structure
For a clear overview of the new navigation under the section “Technical Connection”, please refer to the “New Navigation” table. Based on their permission, users will no longer see all services but only those they are entitled to see and use.
Improved Technical/Responsible Line Contact concept
Since 1 February 2021, a new contact type is available via the Member Section: the “Technical” contact. With the introduction of the Release 2.3, the “Technical” contact will be needed when requesting connectivity. Therefore, Trading Participants are asked to have at least one company contact registered with the contact type „Technical“ before Release 2.3. This ensures a seamless processing of connectivity requests after the introduction of the new release.
Enhanced Requests & Configuration services
The major changes that are coming with the Member Section Release 2.3 are to enhance most of the features within the “Technical Connection” section, especially in the “Requests & Configuration” area, so that Trading Participants can benefit from:
Introduction of the API Hub
With Release 2.3, Eurex will introduce the “API Hub”, enabling easy upload and download services for customers. The API Hub is a new application which allows customers to subscribe to REST based APIs, which are provided by Eurex, using cloud infrastructure. These APIs can then be used in the Trading Participants' implementations to read or post data. With the API Hub, Trading Participants will benefit from:
Some services that are available today via the Download Agent will also be available via the API Hub starting 12 July 2021. The table below gives an overview of the services available via the Download Agent and the API Hub:
With just a few steps, users can consume the data via the API Hub. Further details on the API Hub usage are available in the Member Section 2.3 Technical Connection - User Guide.
Please note that, after a transition period, the API Hub will replace the Download Agent which is currently using the SOAP technology and will not be supported for much longer. Details about the decommissioning of the Download Agent will be communicated in a separate Eurex circular in due course.
Improved Incident Tickets handling permission concept
With Release 2.3, users will experience a better performance and more intuitive design of the interface. To access the Incident Tickets the newly introduced user permission “Incident Ticket Maintenance” is required. To request this permission, Trading Participants have to go to:
My Profile > Permissions > Technical Connection.
The request will need to be approved by the Central Coordinator or Deputy.
Further improvements of the “Technical Connection” section will be introduced with the next Member Section Releases. Detailed information will be communicated in due course.
Further information
Recipients: | All Trading Participants of Eurex Deutschland and Vendors, all users of the Member Section | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Contact: | member.section@deutsche-boerse.com, tel. +49-69-211-1 78 88 | |
Web: | Member Section | |
Authorized by: | Michael Peters |
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.