Is there any way to limit my incoming payload on basis of fid in RefreshMsg java construct in EMA...
Best Answer
-
Hello @rkumar
You can use Views feature to limit incoming payload of Refresh and Update messages containing only your preference fids. Using a view, a consumer requests a subset of fields. Then, only the requested fields are sent to EMA application as the diagram shown below:
For more details, please refer to Section 3.2.3 Views in API Concept Guide
Note: ADS supports only field numbers(field names are not supported) and Level 1 data(Market Price) domain for Views feature.
You can find the example of using Views feature in consumer.series300.example360__MarketPrice__View application shipped with Elektron SDK Java package. The example output running the application to request fid no.22(BID) and no.25(ASK):
Hope this help.
0
Answers
-
One aspect of using views that sometimes surprises: you may see update messages but the fields have not changed value.
This can happen when an update message contains a change to a field value that is not in your view but the message also includes a field that is in your view (but its value has not changed): e.g.:
View : FID 22(BID), FID 25(ASK)
A full update might include: BID= 236.95, BIDSIZE= 11396
Application receives update : BID=236.95
because BID is in the view specification:
Subsequent update includes: BID=236.95, BIDSIZE=9696
Application receives another update : BID=236.95
because BID is in the view specification but the value is the same.
0 -
is there any proper documentation about EmaFactory ,OmmArray and EmaRdm and other utility classes to use them as per requirement . i basically want to use view and batch functionality .i took help from elektron sdk but its not exactly what i want .
0 -
@rkumar There are EMA tutorials and online API documentation at: https://developers.thomsonreuters.com/elektron/elektron-sdk-java/learning
For EMA Java, if you click on Documentation -> expand Development -> "Message API - Java: Development and Configuration Guides with Examples" it will launch the doc bundle. Within the bundle, expand the Java Reference Manual to launch the JavaDoc for API.
Easiest mechanism would be to look at code sample in:
example360__MarketPrice__View
and
example370__MarketPrice__Batch
bundled with EMA SDK.
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 中文论坛