NIP needs to download the dictionary before the service is UP

I'm developing a Non Interactive Publisher with the Electron API.
I publish to and ADN into a service named "MY_PUB".
In order to publish, I need a dictionary. I want to download this dictionary from the ADH (or from an ADS). But if my NIP is not already publishing, the service MY_PUB is absent on the ADH and I have the below error message:
12:44:14.777 [pool-9-thread-1] INFO c.h.f.t.s.ReutersPlatformService - Dictionary status message received: provider=Provider_2_4, serviceName=MY_PUB, itemName=RWFFld, itemState=Closed / Suspect / None / 'Service name of 'MY_PUB' is not found.'
12:44:14.778 [pool-9-thread-1] INFO c.h.f.t.s.ReutersPlatformService - Dictionary status message received: provider=Provider_2_4, serviceName=MY_PUB, itemName=RWFEnum, itemState=Closed / Suspect / None / 'Service name of 'MY_PUB' is not found.'
How am I supposed to download the dictionary?
Best Answer
-
Unless you want to explicitly query the Dictionary and check the list of field present in the dictionary, you should not need to download the dictionary in order to publish data from your NI Provider.
For instance, if i take the simplest NIProvider example100, modify it with your Service Name, amend the EMAConfig.xml <Directory_1> entry to reflect your servicename and run it - it should just work. This is because EMA is downloading the dictionary behind the scenes to use when it does all the encoding etc for you behind the scenes.
You will note from the example100 source code that it does not download the dictionary.
0
Answers
-
Hi @nicolas.roux,
As a provider, your application defines the fields it publishes to the infrastructure. You will need to acquire an appropriate dictionary from your TREP administrator as a text file that you will load and parse within your application. You can refer to the details outlined within the EMA NI Provider - Publishing our first Market Price tutorial.
In order for you to download the dictionary within your application, I believe you my be able act as a consumer to your infrastructure to download the dictionary.
0 -
What is the best practice regarding the dictionary?
I thought that I was supposed to download the dictionary from the ADH/ADS in order to get the latest version. Then use it with my NIP.
But according to your answer, I'm supposed to get a dictionary from my TREP admin. Copy it locally. Then use it with my NIP. Is that correct?
Isn't it a problem if the dictionary changes on the TREP infrastructure, while I'm still using an old local copy with my NYP?
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 WebSocket API
- 37 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.8K Refinitiv Data Platform
- 622 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛