F7 General FAQ

The "7" denotes it is part of the Deutsche Börse Group "7" platform technology suite, where “F” stands for funding and financing.

No reports for Eurex Repo trading are intended and therefore a connection to the CRE is not needed. Business reports (billing) can be accessed via the Member Section available via www.eurexrepo.com.

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 (ie. 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.

No, not all documentation is provided in the public section (e.g.) Documentation regarding the F7 API is only available in the Member Section.

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 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.

The Microsoft Internet Explorer, even in the newest versions, implements HTML5 in a significantly different way compared to other browsers (i.e. Chrome, Firefox).
At this point in time, the Microsoft Internet Explorer is not supported by Eurex Repo’s F7 Trading GUI.

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

User group profiles are planned for a later F7 release.

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. Reference Data is available within the Trading GUI or can be received via the F7 API. In addition, Market Data is published via Market Data Providers as today.

The F7 API relies on AMQP for message transfer. To establish a connection, participants need to provide self-signed x.509 certificates for authentication and encryption of the traffic.

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

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

As part of the F7 end of day processing, the master data for the next business day will be prepared and published to the master data broadcast topic, and will thereafter be available for the clients to retrieve prior to starting the next business day. The emergency master data broadcast request is only to be used in exceptional situations to inquire a new master data snapshot if it is lost during the trading hours.

As soon as a client application has picked up a message from a queue or topic, the message is no longer available for the client application. Messages that have not been consumed so far remain available in the AMQP broker; the client application can re-request the master data using the Emergency function at any time.

The development of an individual feed file is possible using the F7 API, or an alternative product from an ISV can be acquired. A list of ISVs working on F7 platform services can be found on http://www.eurexrepo.com/repo-en/support/f7/vendors/

Eurex Repo's F7 is accessible via leased line and via Internet. Leased line connections will be provided by Eurex Repo and have to be ordered in advance from Eurex Repo. Both F7 API and GUI will make use of SSL 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 x.509 certificate creation.

Yes. Eurex Repo’s F7 uses self-created and self-signed x.509 certificates for authentication and encryption. Please refer to the document “Eurex Repo’s F7 Connectivity Guide” for details about x.509 certificate creation.

Customers must create their certificates themselves. Please refer to the document “Eurex Repo’s F7 Connectivity Guide” details about x.509 certificate creation.

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 beside 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).

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 both, GUI and API via the same channel. However, a separate leased line for Eurex Repo API can be ordered.

For GUI and API 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 by design. Please consider our CN /User name conventions for this, i.e. [MEMBERID]+[GUI|API]+[..freetext...] as explained in the "Eurex Repo F7 Connectivity Guide"

Either one certificate for an entire organization (=participant certificate), or an individual certificate for each users can be created.

Two separate "technical user accounts" for the Simulation and Production environment need to be setup to upload corresponding certificates in the Member Section.

The F7 platform supports self-signed x.509 certificates by design only. According to this, the security check is fulfilled when the client owns the certificate to the corresponding public key uploaded into our platform.

Either openSSL or the Java key tool. Please refer to the document “Eurex Repo’s F7 Connectivity Guide” for details about x.509 certificate creation.

The x.509 certificates can have a maximum validity of three years.

The F7 API servers have COMODO certificates in place and these are server specific certificates.