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
- 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
- 652 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 中文论坛