RFA 7.8 SSLED message tracing (32 bit)

Hello,
we have an application subscribing price data via an old RFA SSLED connection to a TREP server using RFA V7.8 in 32 bit.
We have a requirement to setup message file tracing for performance measurement from the server operator.
I have tried several approaches suggested (one from this forum for verbose logging in SSLED) but nothing works as I would expect. When I add an sslapi.cnf file with
*messageTracingFlags: SSL_TRACE_IN SSL_TRACE_DATA
*messageTracing:20000000
*functionLogging:20000000
*eventLogging:20000000
I get a message trace, but on the terminal, not into a file.
QUESTION: What configuration changes do I have to make to get the trace into a file. Terminal logging is no option as we need to trace in the production environment.
Thank you very much in advance for any helpful suggestions.
Answers
-
Hello @Winfried1 Schleipen01,
RFA is a legacy API and the SSL protocol is the End of Life as per this product change notification. I would recommend that you look into migrating the app to a recent, supported SDK like RealtimeSDK for Java or C++. These SDKs are easier to program, compared with RFA, and your SSL based application will stop working, once the infrastructure is upgraded.
For your question, I didn't think that sslapi.cnf was applicable to RFA SDK. RFA has its own logger entries in the RFA configuration, under the section App Logger - which specify the filename, size etc. Please check the RFA Config Guide which is bundled with your RFA SDK package.
See this question for a basic usage of the App logger entries.
0 -
thanks for your response. I am aware that the RFA is legacy. Sometimes circumstances prevent you from changing to a newer proctol. So that will not change for the moment.
So I am looking for information on how to direct the message tracing, which is definitely switched on using the sslapi.cnf file, to a file instead of to the console. I have tried every configuration parameter I could find, nothing worked ...
M observations are from our live systems, I have tried to follow the RFA documentation first. The RFA Logging is documented for RSSL connections but we have to use SSLED, for which message tracing is apparently not controlled from the RFA configuration.
I have found another post in this forum (Verbose Logging SSLED) which detailed the switch on of tracing in SSLED and tried that. Also some settings suggested by the operators of the TREP server we connect to. To no avail, all tracing is done on the terminal, which is not what we need here.0 -
Hello,
I have found the cause of the tracing to the terminal. My application has no write permissions on its current working directory. I setup a test environment where it had those permissions and then it created an IPCTRACE{PID} file. It moves the file to IPCTRACE{PID}.old when 2MB size are reached.
Now I still would like to control where the file is written so I can use a directory with the correct permissions.0 -
Hello @Winfried1 Schleipen01,
It doesn't look like the output directory of the file can be configured. Here is what I found in an old SFC guide:
0 -
thank you very much for digging this old doc out. Will have to live with that for the moment. I really hope that we will migrate to something more modern in near time ...
Best regards,
Winfried
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
- 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 中文论坛