Error posting using Ema Consumer
Hi,
I am using example ex340_MP_OnStreamPost of EMA Java API to post data. I have made changes for testing with beta environment setup for our application.
Attached is the code and output which shows that I am able to view the data from custom page. From decoded data the datatype seems to be 'rmtes'.
So we made changes to post rmtes buffer to field Id 339. However it does not seem to posting. Are we using correct posting mechanism?
Thanks.
Answers
-
Thank you for reaching out to us.
You can't post messages directly to our real-time service, such as "IDN_RDF". You need to post messages to the Contribution Channel, then the data will be available through the real-time service.
For more information, please refer to this Contributing your data to Refinitiv article.
Would you mind clarifying your goal or objective?
0 -
Jirapongse,
Thanks for quick reply.
I have made slight change to code (see attached OnStreamPost.java_new) but most of it is same as per article.
Objective: We have existing page '1FHLBA1' where we post data using RFA 7.2 libraries. We are upgrading to EMA libraries and want to test posting data to same page. I am able to retrieve data from the page
'1FHLBA1' ' (see lines 45-82 in attached OnStreamPost.log). Next step is to test updating Fid #339 on
1FHLBA1 (refer to line 72 in OnStreamPost.log).
Error: Per lines 84-96 in the log file, I noticed AckMsg(s) with errors.
Please advice if we are using correct values in Service/ Name etc. and if the callbacks/flow we are using are correct for updating target page 1FHLBA1
Thanks!
0 -
You need the Contribution Channel in order to post data to the Real-Time network.
Please let me know if you have the Contribution Channel.
0 -
We don’t have contribution channel. We have been posting to service = DCS_MARKETLINK
0 -
Yes, you need to post to the MarketLink service.
Howerver, MarketLink is being replaced with Contribution Channel as the means of contribution.
0 -
Do you have sample program to test with?
How do we find configuration info required for this specific to our environment, for eg Channel Name?
0 -
Also, can we continue to use MarketLink service? Is there any timeline when Marketlink is going to be obsolete?
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 中文论坛