Parsing View Response Data
Hello, am having issues parsing trep api response data and would appreciate any help.
Currently, am using view and requesting data for ric "IBM.N". The requested fields are "ASK", and "BID". I would like to extract the BID and ASK data and put them into a map.
I would be grateful for a code snapshot of how to extracted these two fields into a map from the response data.
Regards
Best Answer
-
Hello @josa
RFA Java package provide the
GenericOMMParser which is used to read and initialize dictionaries and parse any
OMM message. Hence, you may modify GenericOMMParser to get your preference
fields from the response and update the values in the map. The example source
code is here://create new method in GenericOMMParser.java to parse data and update map for BID and ASK field
public static final void parseOMMData(OMMData data, HashMap<String,Double> fieldsMap)
{
if(CURRENT_DICTIONARY==null) //make sure that RDMdictionary is loaded already
CURRENT_DICTIONARY = getDictionary(1);
for (Iterator iter = ((OMMIterable)data).iterator(); iter.hasNext();)
{
OMMEntry entry = (OMMEntry)iter.next();
if(entry.getType()==OMMTypes.FIELD_ENTRY) {
OMMFieldEntry fe = (OMMFieldEntry)entry;
FidDef fiddef = CURRENT_DICTIONARY.getFidDef(fe.getFieldId());
OMMData aValue = null;
if(fe.getFieldId() ==22 || fe.getFieldId()==25) {
aValue= fe.getData(fiddef.getOMMType());
if(!aValue.isBlank()) {
String key;
if(fe.getFieldId() ==22)
key = "BID";
else
key = "ASK";
fieldsMap.put(key, Double.parseDouble(aValue.toString()));
}
}
}
}
}
//in your application at the method to process data(item events)
public void processEvent(Event event)
{
OMMItemEvent ie = (OMMItemEvent)event;
OMMMsg respMsg = ie.getMsg();
...
GenericOMMParser.parseOMMData(respMsg.getPayload(),fieldsMap);
System.out.println("In the map BID is " + fieldsMap.get("BID"));
System.out.println("In the map ASK is " + fieldsMap.get("ASK"));
...
}0
Answers
-
Also: You may want to consider how you store values of type OMM Real (i.e. BID and ASK fields). Storing them in a Double is one choice (possible loss of precision!) and storing them in a BigDecimal (no loss of precision) is another choice. It all depends on your needs. Sometimes using Double (or double) as in the example above is 'good enough'. Anyway, you'll need to cast the aValue variable in the example to OMMNumeric. This will give you direct translation into double, BigDecimal and so on. No need to first convert to String and then to Double as in the example.
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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛