Can I have a unique id for each update for a RIC across multiple subscriptions ?
All,
For resiliency, we need to have multiple applications running at the same time that use EMA API to subscribe for real time data updates for a same list of RICs. Is there a way to get a unique id for each update for a RIC across these multiple subscriptions/client applications ?
Client A gets an update for RIC with update id say abc1234, it writes the update to DB.
Client B gets the same update for RIC with the update id abc1234. It checks whether it is already in DB. If it is already there it just discards the update
Thanks in advance
Mani
Best Answer
-
Hi @Mani.A
You may be able to utilize some sort of identifier such as the sequence number. If you refer to the data dictionary or review the data model specs, this will provide you a list of fields based on which venue you plan to retrieve. You have to be aware that because the data is ultimately sourced from hundreds of different exchanges, not all may adhere to the same canonical format. However, the data feeds will attempt to normalize the data where they can.
I would suggest you reach out to the helpdesk - they should be able to bring in a content specialist who can provide/confirm if a standard field can be used. I would also suggest you narrow down your requirement by stating where you plan to retrieve your data.
0
Answers
-
Hi @Mani.A
Might be a bit of a long shot, but...
If you are able to develop your application using EMA-CPP then you may be able to use the WarmStandby functionality - as described in the EMACPP_DevGuide.pdf section 7. This could remove the need to implement the resiliency at the application code level - depending on your exact requirements...
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛