DACS recoverability using RFA
Hello,
I am using RFA 7.0.1.E4 in order to access DACS. I would like to know if/how it is possible to handle DACS recoverability.
To be more precise on my question, I need two things:
- get - in real time - the DACS status (up, down...): if DACS falls, I need to be informed, when DACS becomes up once again, I need to be informed as well
- I need to handle automatic reconnection when DACS becomes up
To do so, do I have to check periodically the connection to DACS? (this may be done with a thread running in background)
Or can it be handled automatically and transparently via RFA?
(To my modeste knowledge, Elektron is not able to work with DACS: if I am wrong and Elektron is able to work with DACS and if Elektron is able to handle recoverability with DACS, another possibility for me would be switch from RFA to DACS)
Thanks for help
Philippe
Best Answer
-
Open DACS will reconnect to DACS when the connection is down. As I know, there is no event fired to the application when the DACS connection state is changed. Therefore, the application needs to regularly check the daemon connection state to verify the connection.
RFA is able to connect to TREP or Elektron feed to consume real-time data. RFA itself is unable to connect to DACS. An API that can connect to DACS is Open DACS. However, Open DACS relies on the event distribution mechanism in RFA so using Open DACS requires RFA.
RFA and Open DACS are different APIs but they can be used together because they rely on the same event distribution mechanism.
When you mentioned Elektron in the question, I assume that it is Elektron API, such as EMA or ETA. Like RFA, the Elektron API can connect to TREP or Elektron feed to consume real-time data. It is unable to connect to DACS.
In theory, you can use Open DACS with Elektron API. You can refer to this thread.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛