EMA Programatic Configurition

Having below warning. Would like to confirm if I am missing anything to configure.I am using Programatic configurition to connect to MDS.
WARN OmmConsumerImpl [main]: loggerMsg
ClientName: EmaConfig
Severity: Warning
Text: no configuration exists in the config file for consumer dictionary [DictionaryGroup|DictionaryList]. Will use dictionary defaults if not config programmatically.
loggerMsgEnd
Best Answer
-
Hello @vikas.chaudhary
Thank you for the information. I can replicate the same warning message after I renamed the EmaConfg.xml file and ran the ex421_MP_ProgrammaticCfg example with EMA Java 3.6.0 and EMA Java 3.6.6 The result is shown below:
2022-12-16 14:03:54.999 WARNING com.refinitiv.ema.access.ConfigErrorTracker log
loggerMsg
ClientName: EmaConfig
Severity: Warning
Text: no configuration exists in the config file for consumer dictionary [DictionaryGroup|DictionaryList]. Will use dictionary defaults if not config programmatically.
loggerMsgEndHowever, when I tested with EMA Java 3.6.7, the message has been changed to the INFO level instead as follows:
2022-12-16 13:54:58.644 INFO com.refinitiv.ema.access.ConfigErrorTracker log
loggerMsg
ClientName: EmaConfig
Severity: Info
Text: no configuration exists in the config file for consumer dictionary [DictionaryGroup|DictionaryList]. Will use dictionary defaults if not config programmatically.
loggerMsgEndI do believe that it is related to the following change in the EMA Java 3.6.7 (please see more detail in the CHANGELOG.md file)
EMA Java 3.6.7.L1 Issues Resolved
[RTSDK-6417] - EMA log shows messages that should be "Info" as "Error"Is version 3.6.7 behavior match your requirement?
About the "Is there any way to check if my dictionary is configured corrected programmatically." question. If you enable the API log in TRACE/FINEST level, the following message is shown.
loggerMsg
ClientName: DictionaryCallbackClient
Severity: Trace
Text: Successfully loaded local dictionaries:
RDMFieldDictionary file named C:\drive_d\Project\APIs\EMA_Code\EMA_Java_207L2_Maven\etc\RDMFieldDictionary
EnumTypeDef file named C:\drive_d\Project\APIs\EMA_Code\EMA_Java_207L2_Maven\etc\enumtype.def
loggerMsgEnd0
Answers
-
Hello @vikas.chaudhary
Thank you for contacting us.
Besides this warning message, can the application connect and consume data successfully?
Did your application source code set the DictionaryGroup and its related parameters? You can find the example in the EMA API Consumer example ex421_MP_ProgrammaticCfg (Java) and Con421 (C++).
Additionally, you may check my colleague's answer in this old post too.
0 -
Application can connect and consume data successfully. Is there any other way to suppress warning provided that programatic Config has all configurition.
innerElementList.add(EmaFactory.createElementEntry().ascii("DictionaryType", "DictionaryType::FileDictionary"));
innerElementList.add(EmaFactory.createElementEntry().ascii("RdmFieldDictionaryFileName", EMA_RDM_DICTIONARY_DEFAULT_PATH));
innerElementList.add(EmaFactory.createElementEntry().ascii("EnumTypeDefFileName", EMA_ENUM_DICTIONARY_DEFAULT_PATH));
innerMap.add(EmaFactory.createMapEntry().keyAscii( getDefaultDictionaryName(), MapEntry.MapAction.ADD, innerElementList));
innerElementList.clear();
elementList.add(EmaFactory.createElementEntry().map( "DictionaryList", innerMap ));
innerMap.clear();
configMap.add(EmaFactory.createMapEntry().keyAscii( "DictionaryGroup", MapEntry.MapAction.ADD, elementList ));
elementList.clear();
0 -
Hello @vikas.chaudhary
Could you please let me know the version and edition of the EMA API that you are using?
I cannot replicate the same warning message in the EMA Java 3.6.6 L1 (RTSDK 2.0.6 L1) and EMA Java 3.6.7 L3 (RTSDK 2.0.7.L3) versions.
I tested with the ex421_MP_ProgrammaticCfg example, it can connect and consume data without any warning messages.
0 -
I am using ema-3.6.0.0.jar and eta-3.6.0.0.jar. Is there any way to check if I dictionary is configured corrected programatically. I am not getting this warning when using EmaConfig.xml.
0 -
I am using ema-3.6.0.0.jar and eta-3.6.0.0.jar. Is there any way to check if I dictionary is configured corrected programatically. I am not getting this warning when using EmaConfig.xml.
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 中文论坛