How do read data dictionary config from EmaConfig.xml using EMA Java API ?
Hi All,
I have data dictionary xml in my EmaConfig.xml as below.
In the EmaConfig.xml
<Dictionary>
<Name value="Dictionary_2"/>
<DictionaryType value="DictionaryType::FileDictionary"/>
<RdmFieldDictionaryFileName value="./etc/RDMFieldDictionary"/>
<EnumTypeDefFileName value="./etc/enumtype.def"/>
</Dictionary>
I'm having trouble finding a sample on how to read the above config using EMA Java API.
I have the below to read consumer config from EmaConfig.xml
OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig().consumerName("Consumer_1").username("userid");
I'm looking something similar above to read the data dictionary config.
Please provide some pointers.
Thanks in advance.
Mani
Best Answer
-
Hi @Mani.A ,
The data dictionary part of config is used in creating the consumer and is used by EMA automatically. In the consumer block, just include a reference to the dictionary block that you plan to use like this:
<Consumer>
<Name value="Consumer_1"/>
<Channel value="Channel_1"/>
<Logger value="Logger_2"/>
<Dictionary value="Dictionary_2"/>
</Consumer>See the EMAconfig.xml examples here.
0
Answers
-
Thanks @Gurpreet
In my java code, how I can get access to data dictionary "Dictionary_2" configured for the Consumer_1 in the EmaConfig.xml ?
Currently I'm doing the below:
DataDictionary dataDictionary = EmaFactory.createDataDictionary();
dataDictionary.loadFieldDictionary("RDMFieldDictionary");
dataDictionary.loadEnumTypeDictionary("enumtype.def");0 -
@Mani.A ,
I am trying to understand why you need to do this? Once the dictionary is defined in the config file, it is automatically loaded either from the ADS or from local disk, and is available for use in the EMA application.You don't need an explicit access to data dictionary object.
0 -
@Gurpreet Initially, I had field ids hard coded as below. Our clients use field names not field ids.
OmmArray fieldAarray = EmaFactory.createOmmArray();
fieldAarray.fixedWidth(2);
fieldAarray.add(EmaFactory.createOmmArrayEntry().intValue(22)); //BID
fieldAarray.add(EmaFactory.createOmmArrayEntry().intValue(25)); // ASKLater I used the data dictionary api to get the IDs for the field names as below:
DataDictionary dataDictionary = EmaFactory.createDataDictionary();
dataDictionary.loadFieldDictionary("RDMFieldDictionary");
dataDictionary.loadEnumTypeDictionary("enumtype.def");
System.out.println(dataDictionary.entry("BID").fid());Is there a way to get the field ids for a field name ? Or any best practice for the above ?
Thanks in advance.
Mani
0 -
Unfortunately not. The EMA loaded data dictionary is only available in the context of the callback method. You can either continue to use filename to load your DD, or see the example ex332_Dictionary_Streaming for how to subscribe to dictionary from the network.
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 中文论坛