Not getting data while using user_dispatch mode in EMA?
Dears @nick.zincone.1,@Umer Nalla, @Olivier DAVANT
While using USER_DISPATCH mode, i am not getting the market price data. I tried While referring to few of the samples in MarketPriceStepByStepExample and replaced it with our service name. I am getting the below error while using this :-
>>> Dispatching events until <Item Name> is complete
ERROR - OmmConsumer event dispatching failed: The enum value 1 for the Field ID 6513 does not exist in enumerated type definitions
Could someone suggest what i am missing here?
Best Answer
-
Hi @gaurav.mahajan,
The error you are seeing may be a result of outdated dictionary files within the ADS you are connected to. I would first try on the step by step EMA Java tutorials (Step 2) that uses the default operation model: API_DISPATCH and check your results. There shouldn't be a different between the 2 operation models. If you suspect it could be the ADS dictionaries are out of date, you can try to use local dictionaries. For this, you will have to utilize a configuration file which includes a Dictionary Group which allows you to use local dictionary files. Local dictionary files are included within your EMA package within the subdirectory: Ema/etc.
Just to make sure were in sync in terms of what I did, I took the above Step 2 tutorial and modified it to use the USER_DISPATCH operation model. Sections I changed:
consumer = EmaFactory.createOmmConsumer(
config.host("elektron:14002")
.username("user")
.operationModel(OmmConsumerConfig.OperationModel.USER_DISPATCH)
);
...
// Instead of a sleep, I did this:
long startTime = System.currentTimeMillis();
while (startTime + 60000 > System.currentTimeMillis())
consumer.dispatch(10);After running this, I received the expected results.
Try some of these suggestions and let us know what you find.
thanks.
1
Answers
-
@gaurav.mahajan
Seems like you are using an old data dictionary. Can you verify that it is latest, or if you are downloading from TREP, it is the latest version.
This problem should not be related with EMA dispatch mode.
1 -
Thanks much @nick.zincone.1 and @Gurpreet.! That helps, i was using old dictionary.
0
Categories
- All Categories
- 6 AHS
- 39 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛