Can someone explain the significance of MARKET_DATA_ITEM_EVENT and TibMsg? Why we need to use Tib...
Best Answer
-
Hi @gaurav.mahajan,
Which API and version are you using? I'm assuming RFA 7.6.x or earlier given the group you posted in.
The rfa::sessionLayer::MarketDataItemEventEnum represents an event related to market data activity such as when you receive your initial data image and market data updates. The list of events is available within the Legacy section of the documentation:
You can also find example code segments within the Developers Guide.
This event is specifically related to the legacy message format: MarketFeed. The MarketFeed format is a text-based message format containing field/value pairs that is decoded using the TibMsg API. The basic idea is that you feed the raw message buffer into a TibMsg object and from there you can pull out the fields of interest. You can either use the .Get() method or pull out the fields using the TibField class. If you want to understand more, you can refer to the above screenshot and review the TibMsg programmers guide as well as review some of the examples.
All the above description is legacy reference and is no longer a strategic solution. Instead, TR replaced the Marketfeed format with the Reuters Wire Format (RWF) which is what OMM utilizes. The messages supported using this format have been completely rewritten to replace the legacy Marketfeed format.
Hope this helps.
0
Answers
-
Thanks much @nick.zincone for the detailed explanation! Yes, We are using the 7.6.0.E1 API version.
Upgrade to the Latest Reuters API is next in our List. With TibMsg and TibField, we noticed that in the absence of Reuters Price value it returns 0.0 instead of null. Is this limitation is addressed in new Reuters Wire Format (RWF) which OMM utilizes Or it is something not considered as an issue from the point of view of Reuters API?
0 -
Hi @gaurav.mahajan,
Yes, you can identify using our OMM market data APIs if a field is empty or blank if the data associated with a field is absent. You may also find it helpful to view the Webinar within the news section of the developer portal:
Webinar Recording: Why migrate from RFA to EMA API?
Hope this helps.
0 -
Thanks much Nick!
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
- 687 Datastream
- 1.4K DSS
- 622 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
- 254 ETA
- 557 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
- 276 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
- 672 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
- 229 TRKD
- 918 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
- 48 中文论坛