LSE Gateway Documentation
- TT Gateway And The Exchange
- Installing And Upgrading
- Configuring Global Settings
- Configuring Market Data
- Configuring Order Management
- Disaster Recovery
HSVF Market Data Configuration
TT Gateway Subscription Process
To subscribe to the market data on the HSVF feed, the LSE Gateway uses the following:
- Hostinfo.cfg parameters: The gateway uses ExchangeFeed parameters for HSVF product subscriptions.
- LSEProductGroup.cfg file: This configuration file contains connection information specific to LSEG product subscriptions.
At startup, the Price Server reads the hostinfo.cfg file to determine the product groups that it must download as specified by the ExchangeFeed parameters.
After identifying these product groups, the Price Server refers to the LSEProductGroup.cfg file to connect to the HSVF market data interface and obtain the unicast product group data.
To assist with price data subscriptions, the LSE Gateway uses the LSEProductGroup.cfg file.
This additional configuration file aids in managing price data; however, it does not require manual updates. Do not edit this configuration file.
The LSEProductGroup.cfg is simply an index file that maps connectivity information to the product groups that the exchange sends messages for via the HSVF feed. The LSEProductGroup.cfg file stores connection information for product group data in unique channel sections.
By default, the LSE Gateway does not automatically download all of the feeds configured in the MulticastGroups.cfg file. To download the feed for a particular group, you must enable the corresponding ExchangeFeed=<product group> line to the [PriceServer] section in hostinfo.cfg file.
For details on this parameter, refer to Configuring Product Subscriptions ).
By default the LSE Gateway installs with a LSEProductGroup.cfg file configured to download all futures and options on futures products available on the LSE, IDEM, and Oslo Bors exchanges. If LSE adds a new product group (i.e., set of product information) at a later time, TT will send out a Customer Advisory informing customers what changes they may need to make.
This is the section title. All sections in the LSEProductGroup.cfg file use this section title; there are no variables.
Sets the product group name for the data that the LSE Gateway can request. To request this data, you must include an ExchangeFeed parameter in the [PriceServer] section of the hostinfo.cfg with this product group as its value.
A variable number, starting at 1, that uniquely identifies the [<Product Group>] section.
This parameter sets the IP address and port that the exchange uses to broadcast the product group data (as specified in the product group parameter). For purposes of disaster recovery, each [<Product Group>] section can contain multiple AddressFeed* parameters. The exchange specifies these values.
* is a wildcard and uniquely identifies a feed for the data that the specified IPAddress:Port distributes.
You include the line item AddressFeedA=184.108.40.206:10012
This sets the TT Gateway to obtain unicast product group data from IP Address 220.127.116.11 and port 10012. This feed is labeled FeedA for purposes of routing.
The Price Server is configured by default to connect to the exchange’s HSVF Market Data interface IP addresses at startup. If you do not want to connect to a specific HSVF feed, you can comment-out the corresponding ExchangeFeed parameter in the [PriceServer] section of hostinfo.cfg.
TCP Message Recovery
The LSE Gateway order book is updated incrementally with market data per contract. The HSVF feed begins the trading day with sequence number “1” for each market data message and updates these numbers incrementally by one.
When connecting late or if it has to be restarted in the middle of the day, the Price Server first downloads products and then starts processing from the last available sequence number. If this occurs, the order book will be incomplete until it gets built by subsequent price updates.
Verifying Price Server Connectivity
To verify that the Price Server is connected and receiving market data updates, refer to Verifying Connectivity.