IT Documentation by type

The Optiq Programme will replace the current Euronext core trading applications (UTP/CCG/XDP) for the Cash (Regulated Market and Warrants) and Derivative markets. Following customer feedback, the migration to Optiq will start with the Market Data module for Cash and
Derivatives. As such, the new Optiq MDG will be connected to the Euronext Cash and Derivatives UTP matching engines in phase 1, and then to the Optiq matching engines for Cash (phase 2) and then Derivatives (phase 3)

This document provides the summary of changes for the MDG Derivatives segment change, and the associated technical details. This change is being done as a preparatory step for migration of the Derivatives markets to Optiq.

Following this change Euronext Derivatives markets segments will be split as below:

■ Equity Derivatives (EQD)

■ Index Derivatives (IDD)

■ Commodity Derivatives (COM)

■ Financial Derivatives (FID)

This change in advance of Phase 3 implementation willsimplify migration of the Derivatives markets to Optiq. While no major impact is expected, customers are recommended to ensure that no adjustment is required to the list of Services and Channels they subscribe to via SFTI. For more information, please contact your Relationship Manager. SFTI packages, bandwidth and form are not impacted by this change. This change will be transparent for the CCG, Drop copy & clearing, and will not result in any cancellation of overnight orders. This summary outlines impacts for clients consuming MDG for Derivatives markets. For full details of impacts please review the updated MDG documentation.

This document provides all multicast addresses required to access the Euronext Optiq® Market Data Gateway Production and Disaster Recovery (DR).

The Euronext Optiq® Market Data Gateway Production environment (PROD) is located in Basildon and the Disaster Recovery (DR) environment is located at St. Denis. The Production Primary (P) and Secondary (S) Source IP Address ranges are provided in this document for the live and standby systems as part of the High Availability mechanism.

Customers are requested to allow the Production Primary, Production Secondary and Disaster Recovery (DR) Source IP Address ranges through their Firewalls.

With the XML Standing Data files for the different Optiq Segments, customers will be able to map which instruments are available in which channel. The Optiq MDG feed configuration can be found at the end of each Standing Data file available and these will be provided on a daily basis in XML format. It is required to use the feed configuration details as part of the standing data files to connect to the feed on a daily basis.

In case a new partition is added to an Optiq Segment, customers are required to adapt to this type of change using the Optiq MDG Standing Data files that include the feed configuration details.

The purpose of this document is to describe all the specifications of Optiq™ Market Data Gateway.

The purpose of this document is to describe all the specifications of Optiq™ Market Data Gateway

This document provides guidelines on how to test applications against Euronext’s Optiq Market Data Gateway (MDG) publisher. The document outlines all required conformance steps, the organization of tests, the testing timelines.

This document provides additional information related to session management, order management, MDG high availability and Exchange business continuity.

This technical note intends to provide general information about the Snapshot Service for Optiq MDG. Describing the Snapshot kinematics, this document aims to familiarize developers how to implement this recovery functionality in their feed handler to recover from packet loss, or in case of an intraday/late start.

This technical note intends to provide general technical information about LZ4 compression on Optiq®.

The TRF Conversion Parameters files provide the following data to the members on a daily basis:
■ Contract referential data: Contract code, Maturity, Number of days to expiry, Daily Settlement Price,etc.
■ Pricing of Funding leg and Dividend leg: Daily accrued funding, Daily accrued dividend, Accumulated funding, Accumulated dividend, etc.

This document must be read by Euronext’s clients developing tools for retrieving and processing Market Data files.

This document sets out the file format specifications for Total Return Futures Conversion Parameters files and provides detailed field descriptions.

This technical note intends to provide general technical information about Euronext’s File Services (EFS), a file service mechanism that will be used during the implementation of OPTIQ.

Euronext’s UTP has a built-in protection mechanism that restricts the total number of messages (of all types) that a trading session can submit per second. In UTP-Derivatives, each session on the Common Customer Gateway (CCG) has a session limit of 100 msgs/s. Next to that, an inbound order throttle can be set at an individual contract level or for some contracts (product group). If the throttle for a contract is set to n messages per second, then the Trading Host will allow a maximum of n messages per second in a certain second for an ITM for that contract.

This document provides a functional overview of the Request for Cross (RFC) trading facility which is available for Euronext commodity, equity and index options.

Production & DR OEG Drop copy IP addresses for Cash OEG, OEG DC per Optiq Segment Name and Partition ID and for derivatives per CCG name.

Request For Cross (RFC) Frequently Asked Questions

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all derivative-related trading engines.

This document provides guidelines on how to write effective and efficient applications using the UTP protocols for Order Entry (Binary or FIX 5.0) and Market Data (XDP). It is important to be aware that this document is not a replacement for, but rather a complementary document to the UTP Reference Manuals (see related documentation below). Most of the points raised in this document are concerned with the most efficient, or Exchange friendly way of performing various tasks, and the Exchange requires application developers to adopt the recommendations given where relevant.

The purpose of this document is to set out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the binary format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.

The purpose of this document is to provide customers with a description of the UTP-Derivatives MiFID II order entry conformance script, with scenarios for functional data conformance tests using the new MiFID II fields. Conformance testing will begin on 11 September 2017 on the P-EUA environment until 27 October 2017.

This document provides the list of errors that can be issued from the UTP Matching Engine upon receipt of request messages. Indeed, when the Matching Engine receives a request, it performs several checks on this incoming request message, and may reject it. When it does, the error is identified in the response message sent back by the Matching Engine by an error code together with an associated text in the Text [58] field.

The purpose of this document is to provide customers with a detailed description of the guidelines to follow for testing UTP-Derivatives order entry with the new MiFID II fields.

P-EUA and V-EUA IP addresses for Derivatives per CCG name

Derivatives CCG Binary Header file - MiFID II

This document details the test cases to be performed by the client in order to certify its trading software following the RISKGUARD implementation on the EURONEXT Cash and Derivatives markets.

This document details the test cases to be performed by the client in order to certify its trading software for the Request for Cross functionality implemented on the Euronext Derivatives markets .

Euronext offers to market participants a range of liquidity provider incentive programs tailored to each market (Paris, Amsterdam, Brussels and Lisbon) and aimed at improving on-screen liquidity. Specific functionalities have been implemented within the UTP Matching Engine to support these programs:

■ Market Making Orders (Mass Quotes)

■ Market Maker Protections

These features are only available via the CCG Binary interface to designated Market Makers. This document provides a functional overview of the Market Making functionalities to Members intending to develop an application using the Binary Interface to the Common Customer Gateway (CCG).

This document describes the full conformance test script for order entry on UTP-D

This document describes the drop copy conformance test script for UTP-D

The primary audience for this document are Member Developers and/or ISV’s who want to conform their application/software for drop copy on UTP-D . The drop copy conformance test is mandatory before access to drop copy is granted on the production environment.

This document details the test cases to be performed by the client in order to certify its trading software for CCG Order Entry for EURONEXT Derivatives markets.

This document provides details of the high availability and business continuity for the UTP® trading chain components, including features and elements associated to the Common Customer Gateways (CCG) for the Exchange’s Cash Markets.

This document details the steps required to be provisioned with production access to the NYSE Liffe Common Customer Gateway (CCG).

The purpose of this document is to provide description of main functionalities and services offered by Optiq for Euronext Derivatives markets. This document strives to provide for each identified functionality or service the following elements:

1) Why it is present in our Market

2) Description of the service and its principles

3) Examples, where possible, of its use

4) Advantages & benefits of the services as well as recommendation of use

The aim of the document is to provide a practical overview of functionalities and approaches to Derivatives trading in Optiq. At the end of the document technical and architectural topics are also covered to provide a general overview. This document is the view of the expected implementation of Optiq for Derivatives markets. This document will be updated with further information providing additional details1 . In case of any functional changes they will be highlighted and communicated to clients in due course. A number of functionalities described in this document are subject to regulatory approval, and confirmation of implementation will be provided in due time.

This document outlines the migration guidelines for Phase 3 of Euronext’s implementation of Optiq: Order Entry Gateway (OEG) and Matching Engine (ME) for Euronext Derivatives markets, as well as the changes required to the Market Data Gateway (MDG) on Euronext Derivatives markets.

Scope and audience: This technical note intends to provide general technical information about SBE and specify the SBE implementation on Optiq®.
This document is meant to familiarize developers who will work with SBE for the first time and remind others the current rules of implementation.

This document details the Referential Data HTTPS Server for Euronext, to be used in conjunction with the Optiq MDG Client Specifications.

The Servers provide full referential data for the Euronext markets, as well as feed configurations and intraday trades with their MiFID II flags. Users of the Euronext market data feed should use the Servers to:

- Configure feed connections every day.

- Support the referential data that is disseminated on the feed.

- Complete their list of trades.

This purpose of this document is to provide guidance to Euronext Clients on the application of the requirements for Transaction Reporting (RTS 22) and Order Record Keeping (RTS 6), for the activity conducted on Euronext Regulated Markets.

TradeManagerAPI – 1.8.wdsl (Web Service File) – MiFID II

TradeManager – 1.8.xsd (Schema File) – MiFID II

The purpose of this technical note is to provide general information about the MiFID II technical changes on UTP Derivatives. More specifically, this document aims to describe the MiFID II technical changes with regards to new fields in order entry messages and familiarise developers with how to implement these changes for the respective order entry interfaces.

An Exchange for Physical (EFP) is a transaction involving the simultaneous exchange of a futures position for a basket of shares.

EFPs based on index futures are transactions made on the basis of the difference between the index futures price and the spot price of the index. Currently, the futures leg of these transactions can be reported on Euronext’s Basis Trade Facility, with reference to a cash leg. Euronext’s new Exchange for Physical Facility enables members to trade EFPs on the CAC 40® and AEXIndex® by simultaneously exchanging index futures for the corresponding basket of underlying component securities of the index. The new EFP solution will be available for trading in a regulated environment by means of a transparent central order book supported by a liquidity-providing scheme. Trading of EFPs takes place by means of a fully automated straight-through-process, eliminating operational burdens and facilitating post-trade reporting obligations. In addition, it reduces execution risk thanks to the guarantee of the central counterparty.