Specific FID in Responses

Hi
We have need to get Specific FID of a RIC from TREP using RFA API. The scenario works like below
The first request to RIC would request for FID 1.In this case i expect the response to have FID 1
The Second request woudl request for FID 2. In this case i expect the response to have FID 1 and FID 2
Can you pls help me with the code which would help me to acheieve this
Best Answer
-
Hello @prakash.chellappa
You can use View/Dynamic View feature to specific fields (field
ids) that you want from TREP(ADS) in the request then TREP sends only fields specified in the request to your application as shown in the figure below:Please refer to the article How to request particular fields of an item (RIC) via RFA API which shows the example source code how to request with View in RFA to get specific fields in responses.
0
Answers
-
Thanks Pimchaya Wongrukun for the reponse. I am able to incorporate this out application. But have a followup question as i get some issues randomly. Our application works like below
1. Place a request for a RIC (Say RIC1)asking for FID1 as part of response. We create a Subscription and keep the handle
handle=consumer.registerClient(eventQueue, subscribeInterest, consumerClient, recordKey)
2. Some time later (Say 2-3 min) , we would need FID2 associated with RIC1. In this case, we get the existing from Step 1 above add FID1 and FID2 to it and do the below
consumer.reissueClient(subscription.handle, subscribeInterest);
We observed we dont get FID2 sometime in the responses. Are we doing this resubscription part correctly here or there are alternatives?
Appreciate your help on this
Thanks
Prakash0 -
Hello @prakash.chellappa
I have tested reissueClient(..) to add FID1 and FID2
and it worked properly. After reissuing, the application received FID2 as well.
It is possible that the feed does not provide FID2 in some responses; some
responses have FID2 but some does not have. In this case, the application receives
FID2 in the responses which the feed provides FID2. This is RFA expected behaviors;
RFA passes data responses as it receives from the feed. You can prove this
assumption by enabling RFAJ trace log to see what FIDs the feed sends to the
application.To enable RFAJ trace log file, please set ipcTraceFlags
= 7, traceMsgTypes =ALL, traceMsgDomains=NORMAL,mountTrace=true and specify logFileName
parameter of the RSSL connection node. The default location of the log file is in the application run directory.For example:
<node name="consConnection">
<map>
<entry key="connectionType" value="RSSL"/>
<entry key="serverList" value="ads"/>
<entry key="portNumber" value="14002"/>
<entry key="ipcTraceFlags" value="7"/>
<entry key="mountTrace" value="true"/>
<entry key="logFileName" value="D:\rfa.log"/>
<entry key="traceMsgDomains" value="NORMAL"/>
<entry key="traceMsgTypes" value="ALL"/>
</map>
</node>0 -
Hello @prakash.chellappa
If the feed sends FID2 in some responses indeed and you are wondering why
the feeds does not send FID2 in all responses, you can ask the feed/data team
directly by submitting the query to https://my.thomsonreuters.com/ .After you
log in, click "RAISE A CASE" then "Product Support". Then,
select your subject e.g. “I believe content is incorrect or incomplete”. At
“Select product”, select the feed i.e. “Thomson Reuters Elektron Real-Time”. If you cannot access the web site or submit the query, please send an email to rdc.administrator@thomsonreuters.com0
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛