A member of
Eurex
With circular 300/11 Eurex Group published an overview of functional and technical enhancements for the first half of 2012. With this circular Eurex Clearing provides additional details about the development of the Eurex Clearing FIXML Interface that are planned for the first half of 2012.
Eurex Clearing plans to provide VALUES API requests currently used by member applications as FIXML messages by the end of the second quarter 2012. From this point onwards, members will be able to decommission VALUES API as a clearing interface. Support of the MISS architecture will ultimately be withdrawn in the second quarter 2013, after which the Eurex Clearing FIXML Interface will be the only available clearing interface. The Eurex Clearing FIXML Interface supports the FIXML industry standard. Eurex recommends that members begin their migration activities as early as possible.
For those members with an existing WebSphere MQ infrastructure, Eurex Clearing will also offer WebSphere MQ as an alternative to AMQP as the transport layer in the third quarter 2012.
The implementation of the FIXML Interface uses an incremental development methodology which allows earlier delivery of new features to the members, independent from releases. As a result, the individual features will be delivered to the members over an extended period of time.
The exact dates when functionality will be made available in the Eurex Release 14.0 simulation and Eurex Release 14.0 production environments will be announced in separate Eurex circulars.
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.