Configuring Support of OTC Trades(FIXML)
To support OTC trades via the FIXML Clearing API for EEX users, configure the following files on the Eurex Gateway :
- Windows hosts file
- aconfig_local.xml (for upgrades to 7.16.9)
Before configuring the Eurex Gateway, you must perform the following tasks:
- Create a FIXML account ID.
- Generate a self-signed SSL certificate for the account ID and export it to public and private key files.
- If the ones on the gateway are expired, download the FIXML public keys of the FIXML brokers from the exchange.
- Upload your public key file for your account ID to the exchange.
- Save the Eurex brokers’ public key and your private key in <root drive>:ttconfig on the Eurex Gateway.
TT recommends contacting your Technical Account Manager (TAM) for assistance in performing these tasks.
Creating a FIXML Account ID
Before creating and uploading FIXML OTC Router certificates, you must create a FIXML Account ID. You will need this account ID when generating your self-signed certificate and configuring the gateway.
The following guidelines apply to all account IDs created for connecting to the Clearing Interface via TT’s FIXML OTC Router:
- Account names (IDs) can be no more than 22 characters and only uppercase letters are allowed.
- Characters 1 through 5 are the Member ID of the Eurex member.
- Character 6 is always an underscore (_) separating the Member ID from the rest of the account name.
- Characters 7 through 11 identify the vendor, service provider, or the member who developed the trading application. For TT, this value is TTGXV.
- Characters 12 and 13 identify whether the application is a front, middle, or back office application. For TT, this value is FO (Front Office).
- Character 14 identifies the trade adjustment processing. For TT, this value is B (Automated / Manual).
- Character 15 identifies the give-up and take-up processing. For TT, this value is B (Automated / Manual).
- Characters 16 through 22 identify the member's application name or a combination of application name and location. For TT, these characters are optional and may contain up to 7 alphanumeric characters (no special characters allowed). For a member running multiple Eurex Gateways, the application names must be different to differentiate account IDs and avoid using the same account IDs on different gateways.
Examples of valid FIXML Account IDs:
|Example a TT account ID that connects to the exchange via the Eurex Gateway application.|
|Example a customer account ID for member “ABCFR” that connects to the exchange via a Eurex Gateway.|
Configuring aconfig_local.xml for OTC orders
For a new installation, the Eurex Gateway installs with the Block (66) and Vola (89) Order Restriction parameters configured in aconfig_local.xml.
For an upgrade to 7.16.9 from 7.14.1 or lower, you need to open the Aconfig utility and manually add the 66 and 89 parameter values to AConfig.Core.Server.Exchange-Specific.<Exchange-flavor>.GAL.Supported-Restriction-Codes
Network Interface for FIXML OTC Orders
The FIXML OTC Router uses the default NIC as determined by the binding order of the Windows OS on your machine. The NIC does not need to be configured specifically for the FIXML OTC Router connection.
Configuring ttchron.ini: FIXML OTC Router
FIXML OTC Router service start and stop times are configured in the [win32-svc-<EXCHANGE_FLAVOR>OTCRouter] section of ttchron.ini. By default, the Eurex Gateway installs with the FIXML OTC Router section commented-out.
To enable trading of OTC orders, open <root drive>:ttconfigttchron.ini in a text editor (e.g., Notepad) and remove the # signs from this section.
After an upgrade from a version with a VALUES-based OTC Router, you must remove the MISS start up and shut down sections from the ttchron.ini file.
|Example ttchron.ini sections for FIXML OTC trade support|
[win32-svc-EurexOTCRouter]## TO DO: Configure the following as appropriate...run_days=12345start_time=7:20end_time=22:47days_in_cycle=1holidays=holidays-DE1tags=Eurex
Configuring the FIXML OTC Router in hostinfo.cfg
To enable and configure FIXML OTC Router functionality on Eurex Gateway use the parameters in the [FIXML-SESSION-x] section and the [FIXML_ORDER_ROUTER] section in hostinfo.cfg.
To configure the FIXML OTC Router in hostinfo.cfg
- Open the Exchange-flavorhostinfo.cfg file in a text editor.
- Enable and configure the following parameters
in the [FIXML_ORDER_ROUTER] section
(parameters are enabled by removing the # symbol).
Parameter Description [FIXML_ORDER_ROUTER] By default, this section is commented-out. To enable this section, remove the # symbol. router_port
Sets the listening port for an OTC session. The FIXML OTC Router uses the router_port to listen for and accept OTC session connection requests on the machine running the Eurex Gateway, and the Order Server attempts to connect to the FIXML OTC Router at this port to establish an OTC session.
Enter a port number that is not in use on the machine running the Eurex Gateway. When configuring router_port, consider the following:
- The port is used locally per machine running the Eurex Gateway, so it does not interfere with other ports configured on other TT Gateways in your network (i.e., multiple Eurex Gateways with FIXML OTC Routers can use the same port).
- As long as the port is not in use as a listening port on the same machine running the Eurex Gateway, it is available to be used for the FIXML OTC Router.
By default, this parameter is commented-out and OTC functionality is disabled. This parameter is required when configuring the [FIXML_ORDER_ROUTER] section.
Sets the DNS hostname for the primary FIXML Clearing Interface to connect the FIXML OTC Router to for a FIXML session. The gateway uses a Windows host file to resolve IP addresses for connections to its FIXML Clearing API interface.
Sets the port of the FIXML Clearing Interface server where the FIXML OTC Router connects to the AMQP broker. Enter the value provided by Eurex in their exchange credentials.
broker_certificate_file Sets the path (<root drive>:ttconfig) to the Eurex public key file containing the SSL certificate for the AMQP brokers on the primary FIXML Clearing Interface. This path should be to the same as the FIXML OTC Router private key file location. There is a dependency between the host names and the brokers' host certificates, such that the host names should not be replaced with aliases. The certificate is installed in <root drive>:ttconfig during a clean or upgrade installation of the Eurex Gateway.
- Enable and configure the following parameters
in the [FIXML-SESSION-1] section
(parameters are enabled by removing the # symbol).
Parameter Description [FIXML_SESSION-1] For any member who wishes to support the FIXML OTC functionality, an individual FIXML OTC session must be configured with this section. member
Sets the exchange member (business unit) ID for the FIXML session that supports OTC trades for this business unit and all its traders. Only OTC trades for this particular member will be routed through this FIXML OTC session. Enter the exchanged-provided member ID. An exchange member can only have one FIXML session defined per Eurex Gateway.
Sets the FIXML account registered at the exchange and required for connecting to the AMQP brokers for sending OTC orders. To create a FIXML account ID for use with TT Gateways and Clients, refer to Creating a FIXML Account ID. You can also refer to the guidelines in Section 4.1 of the "Eurex Clearing FIXML Interface Specification Volume 2: Connectivity”.
client_certificate_file Sets the location of the private key file containing the SSL certificate for the member’s account ID. The private key file needs to be stored in the config directory. For example, set this parameter to <root drive:>ttconfigTTGXV_TTGXVFOBB.p12.
Note: The FIXML account ID used to generate the SSL certificate in the private key file must be the same FIXML account ID configured on the gateway and registered on the Exchange website.
Sets the password used for accessing the SSL certificate in the private key file.
Note: Set this parameter to the same password that you created when exporting the SSL certificate to the private key file.
The Eurex Gateway will not connect to the FIXML Clearing Interface if the password used for configuring this parameter does not match the password created when exporting your certificate to the private key file. Refer to the Eurex Clearing FIXML Account IDs and SSL Certificates Setup Guide for more details about creating this password.
- Save and close the Exchange-flavorhostinfo.cfg.
Example: FIXML OTC Router configuration
The following example shows an initial configuration.
|Example [FIXML_ORDER_ROUTER] and [FIXML-SESSION-x] sections|
Configuring the Windows hosts file
The host names for the AMQP brokers are configured in hostinfo.cfg, but their IP addresses are resolved using the Windows hosts file on the Eurex Gateway. The FIXML Order Router resolves the host name to open the AMQP connection.
The IP Addresses and host names for the Eurex FIXML / AMQP Brokers are configured in the Windows hosts file at WindowsSystem32driversetchosts
To configure the hosts file after a clean install or upgrade to 7.16.9 or higher, do the following:
- Open the WindowsSystem32driversetchosts file in a text editor (e.g., Notepad)
- Enter the IP address and host name provided by Eurex
The following example shows a host file configured on a Eurex Gateway.
Saving the Certificates on the Gateway
The FIXML connection also requires that the FIXML Order Router authenticates the server certificates of the Eurex AMQP brokers before the SSL sessions can be established. Eurex’s public key files for the exchange brokers are installed automatically on your machine during a Eurex Gateway install or upgrade.
To ensure that the private key file and Eurex’s public key are accessible to the FIXML Order Router, both certificates should be stored in the same location on the Eurex Gateway (e.g., <root drive>:ttconfig).
When configuring the FIXML OTC Router on the gateway, the location of the private certificate is set using the client_certificate_file parameter in hostinfo.cfg. The Eurex public certificates are installed in the config directory automatically during clean installs and upgrades.