Source Directory Update message processing by EMA Consumer application
We are writing a consumer application to connect to TREP:
- When a Source Directory Update message is received indicating AcceptingRequests=No, what should be done by the application when it needs to create a new item stream? (Should the application search for another service that provides the same Capabilities and use that service to send new item requests?)
- When a Source Directory Update message is received indicating Status = None, according to EMA30_RDMUsageGuideAPI fan out it to Status message for each item stream? Suppose we are using a service related to MarketPrice domain. Then does this mean, the application receives MarketPrice Status messages for each item stream that have been opened. If so, what will be the DataState and StreamState of each Status message received by the application?
Best Answer
-
For #1
I think your understanding is correct.
From section 4.4.2 ServiceState and AcceptingRequests
If the servicestate is up but acceptingRequests is No. The immediate provider is not accepting new
requests. However reissue requests on already open streams can be processed. In this case you want to send a
new item requests(not reissue), so you need to find another service that provide the capability you want to request and the new service must have ServiceState=Up and AcceptingRequests=Yes.For #2
As far as I understand,for the publisher/provider such as UPA/ETA provider, sending Status with directory is
equivalent to sending an RsslStatusMsg to each item. This status only applies to item streams that have received a refresh or status of stream state OPEN with data state OK(OPEN/OK). I think None in the Status is the status code inside Status object. Therefore EMA Consumer should receive stream state Open and Data state OK.0
Categories
- All Categories
- 6 AHS
- 37 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 中文论坛