How does subscription recovery work for an Eta application?
I am using ElektronSDK/Cpp-C/Eta client API to build a real-time market data handler. Consider the following scenario
- The handler is up, client API is connected to remote ADS, subscribed to a bunch of items, and receiving update msgs
- Now we have a network outage and the client API gets disconnected from ADS
- At some point later client API reestablishes connection to ADS
From the handler application perspective, expectation is that all previously subscribed items will automatically recover their streams, will get refresh msgs, followed by updates. The client API takes care of it and It is not the responsibility of handler to resubscribe.
Is this expectation correct? Is there anything special to be done at code or config level in the handler to make it happen? Is this a client API feature or ADS feature or both together? If this is not working then how does one go about troubleshooting this?
Best Answer
-
There are two ways to use ETA.
1. The application directly uses ETA, as shown in the Consumer example. In this way, the application needs to handle everything, such as ping mechanism, connection recovery, and item recovery
2. The second way is using the value-added library (Reactor), as shown in the VAConsumer example. The Reactor will handle the ping mechanism, and connection recovery. However, to do item recovery, you need to enable WatchList in the Reactor, as shown in the WatchListConsumer example
0
Answers
-
Hi, thank you for your reply. I tried to follow WatchListConsumer in my code but encountered API and behavior issue. So I decided to handle this in application code: after reconnection, on channel ready event, I resubmit subscription requests for all RICs the app had been subscribed to. Do you see any issue with this approach? Thank you. -- Rajiv
0 -
I think the application should resubmit subscription requests when the service is up. If you need to perform item recovery at the application, please make sure that the watchlist is disabled.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 650 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛