F7 General FAQ

N7 is a Deutsche Börse Group Network Solutions product which provides customers connectivity to our platforms, such as Eurex Repo F7. 

No fields on the form need to be filled out for connectivity (i.e. leased line, or internet details) in the "N7 Service Order". In this case only the business parts are relevant.

The "Certificate Access Fee" applies to customers with internet connections only or with connectivity via service providers. The monthly certificate access fees permits the use of 20 concurrent certificates (GUI, API or other). Additional capacity is available on request. For customers having leased line channels to F7 in place, additional access via internet certificate is included, i.e. a customer can use internet in addition to a leased line connection without any additional cost. 

Business reports (billing) can be accessed via the Eurex Repo Member Section available via www.eurex.com. The Member Trade eXtractor (MTX) can be used to automatically create trade files (reports) with extended details of your firm’s trades that you can retrieve from Deutsche Börse’s Common Report Engine (CRE).

No, not all documentation is provided in the public section (e.g.) System documentation, for example F7 API manual, is only available in the Member Section.

As a regulated exchange, all interfaces of Deutsche Börse Group are subject to penetration tests performed by changing third parties. Deutsche Börse Group takes care that all state of the art measures, mechanisms, and procedures are in place to ensure security of the web portals and platforms it operates and ensures that all applied functionality is compliant with relevant regulatory and government directives and policies.

The Eurex Repo F7 GUI is a pure browser based application. No software needs to be installed. Please refer to the release notes for a list of compatible web browsers.

No, the F7 GUI uses non-standard ports 8443 and 9443 for simulation and production.

Google Chrome, Microsoft Edge and Mozilla Firefox browsers are tested and supported for the Repo F7 GUI. 

It is recommended to update your browser to the latest version available at all times.

The F7 GUI and API/FIX are completely server based and hosted on the DBAG platform including the individual user profiles.

The Repo F7 GUI user can be provided with the appropriate URL by means of desktop shortcuts, browser favorites or a landing page.

Market Data is provided via the Trading GUI or the F7 API/FIX. Reference Data is available within the Trading GUI or can be received via the F7 API/FIX. In addition, Market Data is published via Market Data Providers.

The F7 API relies on AMQP for message transfer. To establish a connection, participants need to providea DBAG signed client certificate for authentication and encryption of the traffic. DBAG signed client certificates can be created easily in the DBAG Member Section. 

They can be found in the DBAG Member section under each release with an API upgrade.

They can be found in the DBAG Member section under each release with a FIX upgrade. 

The MTX manual can be found in the DBAG Member section under each release with an MTX change. 

The certificate can be found in the DBAG Member section under: https://member.eurexrepo.com -> "Repo Resources > Trading System F7 > System Documentation > Release 1.0 > Eurex Repo Trading Interfaces"

Eurex Repo's F7 is accessible via leased line and via Internet. Leased line connections will be provided by Eurex Repo and must be ordered in advance from Eurex Repo. Both F7 API/FIX and GUI will make use of TLS encryption for data transfer on leased line and on Internet connections. Please refer to the document “Eurex Repo’s F7 Connectivity Guide” for IP addresses, URLs, and details about the required DBAG signed client certificates.

Each client, GUI, API, or FIX must present a client certificate signed by the DBAG Certificate Authority. Such DBAG signed client certificates can easily be created in and downloaded from the DBAG Member Section. Please refer to the document “Eurex Repo’s F7 Connectivity Guide” for details about the required DBAG signed client certificates.

Yes, on request. (depending on location)

Yes, for colocation customers, leased line pricing of Tier A (Frankfurt) is applicable.

A managed "fail-over" service between leased lines and internet is not supported. However, customers can deploy an internet connection besides their active Repo F7 leased lines connectivity as part of a BC/DR solution. In this case, the clients (GUI/API) need to be provided with a separate URL for BC/DR cases since the URLs and IPs are different for Leased line, and internet.

A managed "fail-over" service between leased lines and internet is not supported. However, customers can deploy an internet connection besides their active Repo F7 leased lines connectivity as part of a BC/DR solution. In this case, the clients (GUI/API) need to be provided with a separate URL for BC/DR cases since the URLs and IPs are different for Leased line, and internet.

Since this is specific to the individual 3rd party software solution, the software vendor must be contacted directly.

Yes, a separate dedicated MemberLAN for Eurex Repo F7 services will be assigned (provided enough bandwidth is available).

No, this is not possible by design since Repo F7 platform serves all, GUI, API and FIX via the same channel. However, a separate leased line for Eurex Repo API can be ordered.

For GUI and API/FIX encrypted SSL over TCP/IP is in place.

The F7 setup is redundant, i.e. the platform is hosted in two separate DBAG data centers, with redundant network topology.

Yes, the F7 System requires separate certificates for GUI and API/FIX by design. Please consider our CN /User name conventions for this, i.e. [MEMBERID]+[GUI|API|FIX]+[..free text...] as explained in the "Eurex Repo F7 Connectivity Guide".

Either one client certificate for an entire organization (=participant certificate), or an individual client certificate for each users can be created. It is recommended to create individual client certificates for each client application and user. 

Two separate "technical user accounts" for the Simulation and Production environment need to be setup to download corresponding client certificates in the Member Section. Client certificates can only be used in the environment for which they were created. 

The F7 platform supports certificates by design only.

When creating a DBAG signed client certificate a validity of either one or two years can be selected.

The F7 API/FIX servers have  server certificates signed by a well-known certificate authority (CA) in place. At the time of writing this FAQ the signing CA is “DigiCert” using DigiCert’s G2 or G5 root certificate.