IProvider downloading dictionary and serviceName\serviceId parameter
Hi, I'm trying to implement the Dictionary downloading mechanism in an EMA C++ Interactive Provider.
To do so, I'm playing with the '350__Dictionary__Streaming' example of the EMA SDK.
I have a question regarding the following instruction: provider.registerClient(ReqMsg().name("RWFFld").filter(DICTIONARY_NORMAL).serviceName("DIRECT_FEED").domainType(MMT_DICTIONARY), appClient);
As far as I understood, any client registration in EMA where the serviceName is specified, requires that EMA knows such service in advance, otherwise the operation is rejected. For instance, a consumer that registers a client for a MarketPrice item on the service DIRECT_FEED will be able to perform the request only if the required info about the DIRECT_FEED service has been received previously on the DIRECTORY domain.
So my question is: where does the IProvider get this information to register a client on the MMT_DICTIONARY domain and specifying the service name?
So far, the only way I found to make EMA see the service is to declare the service among the ones provided by the IProvider itself. If I don't do it, EMA does not accept the registerClient(...) requests using that service, and a status message is received with text "Closed / Suspect / Source unknown / 'Service name of 'DIRECT_FEED' is not found.'".
Ps: to make some tests, I connected an ETA based NIProvider (able to handle dictionary requests) to my IProvider. I understand that this isn't a real use case, hoping that it isn't the root cause of my issue..
By the way, if I make the dictionary requests without specifying the service, and edit the NIProvider to send refresh without specifying the service, everything works well.
Please help me clarifying this.
Thanks
Paolo
Best Answer
-
I also cannot find a way for EMA IProvider to get service information available on connected ADH. Also as you mentioned, EMA allows only service that it have information to be registered, so, in this scenario, the application can only use the service name declared in DIRECTORY response sent by provider side.
I have also tested the dictionary request to ADH without service name specified, ADH can provide dictionary properly. From my understanding, this feature is to download dictionary from ADH component, not service.
1
Answers
-
Thank you for the analysis.
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 中文论坛