RICs/Chain cannot be returned with RFA API
Client is using RFA to retrieve below chain/single RIC(Tried both ways) to their new downstram system but found one strange thing.
RICs or chain cannot be returned(Snapshot one) but when client added one RIC they used before(Like AUD=), new RIC/Chain can be returned properly(Snapshot two)
Can you please take a look and share us why this happened? Below is sample chain/RICs
0#AAACDBMK=
AAA6MCD=R
AAA1YCD=R
AAA2YCD=R
AAA3YCD=R
AAA4YCD=R
AAA5YCD=R
AAA7YCD=R
AAA10YCD=R
AAA20YCD=R
AAA30YCD=R
Best Answer
-
Hello @Hao.Tang
The list of RICs that the API sends the item request messages to the server is the following
- AAA6MCD=R
- AAA1YCD=R
- AAA2YCD=R
- AAA3YCD=R
- AAA4YCD=R
- AAA5YCD=R
- AAA7YCD=R
- AAA10YCD=R
- AAA20YCD=R
- AAA30YCD=R
All RICs above received the Refresh message successfully. I cannot find any AUD= in the RFA trace file.
0
Answers
-
Hello @Hao.Tang
I am assuming that the client is using the RFA Java with the OMM interface, could you please confirm?
What is the version of RFA Java that encounters the problem?
If the client can replicate the issue on demand, please ask the client to enable the RSSL trace log and share the log file in this forum.
The client can configure the following RFA Java configurations to enable the log file
- <namespace>/Connections/<Connection Name>/ipcTraceFlags = 7
- <namespace>/ Connections/<Connection Name>/mountTrace = True
- <namespace>/ Connections/<Connection Name>/logFileName=<path to log file>
0 -
Thanks for helping me out. Rfa Java 1.0
rfa-1.0.jar
Rssl log I am checking with client on it
0 -
Can you take a look at below log if it is the required one
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
<log>
</log>
0 -
Hello @Hao.Tang
RFA Java version:
There are two ways to get the RFA Java version:
- Via the Context.getRFAVersionInfo().getProductVersion() statement
- Upzip the "rfa.jar" library jar file, then check the MANIFEST.MF file in the META-INF folder. The RFA Java version will be shown in package_Version property of the MANIFEST.MF file.
RFA log file:
The given rfa-rssl0.txt is just an empty XML file. How the client config the RFA configurations? Could you please ask the client to share the Configurations (or XML configuration file?)
If the client uses XML configuration, the client can configure the following RFA Java configurations to enable the log file
- <namespace>/Connections/<Connection Name>/ipcTraceFlags = 7
- <namespace>/ Connections/<Connection Name>/mountTrace = True
- <namespace>/ Connections/<Connection Name>/logFileName=<path to log file>
This is my example Configurations:
My example RFA log file is the following: RFA_RSSL0.txt
0 -
Thanks and attached log should be proper one this time
0 -
Yes, occur at client test TREP environment
They do not need to subscribe AUD=, but if they only retrieve other 9 RICs they really need then no RICs was returned, however when add AUD= (They retrieved before), then all RICs can be returned properly
Can configure error they made? Strange thing is that this is not new set-up, they use RFA API for many downstream system but when they configure new RIC for new system, error occur
0 -
Thanks so much and I will ask client to try again today or Monday
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
- 688 Datastream
- 1.4K DSS
- 624 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
- 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
- 692 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛