Eurex Gateway

7.17.45.8

Released: Apr 29, 2014 File Size: 0
Package Contents:
No notes available.

Important Notes

All customers will need to upgrade to the new version of the gateway (Eurex 7.17.45) prior to the start of trading on 12 May. Prior versions of TT's Eurex Gateways will not be able to operate in the upgraded exchange environment.

Why Should I Upgrade?

Eurex Gateway 7.17.45 adds support for Eurex T7 2.1 API release and Eurex/TAIFEX Link. For further details refer to the Help Library.

System Requirements

Eurex Gateway 7.17.45 adds support for Eurex T7 2.1 API release and Eurex/TAIFEX Link. For further details refer to the Help Library.

Installation Notes

Enhancements

  1. Order Server
    1. Forward slash(/) sign is no longer required when configuring an exchange password for the gateway login credential in TT User Setup. (Ref 227404)

    2. Added support for Eurex/TAIFEX cooperation products. For further details refer to the Help Library. (Ref 227406)

    3. Full Regulatory ID field is passed to the Back Office FIX Adapter clients. For further details, refer to the TT Advisory CA022-14. (Ref 228134)

  2. Price Server
    1. Added support for Eurex's T7 2.1 API. (Ref 227690)

Fixes

  1. Order Server
    1. Held orders can be changed or deleted when the exchange is not available. Previously, synthetic held orders could not be managed when there was no connection established with the exchange. (Ref 164437)

Known Issues

  1. Order Server
    1. Log files can grow to a significant size if the gateway is misconfigured. (Ref 218444)

    2. Some spread legs fills can be reported incorrectly after the market reset event. (Ref 226114)

    3. Inquire button does not work when approving a Block trade for KRX or TAIFEX cooperation products. End users should inquire by using Inquire Order Block dialog box instead. (Ref 228296)

  2. Price Server
    1. Stale prices and cross markets can be displayed on the connected clients after the exchange product failover. The Price Server needs to be restarted to resolve the issue. (Ref 221969)

    2. Synthetic SE orders can incorrectly trigger when prices are not recovered correctly after a network disruption. (Ref 222692)