RFA configuration for MRN_STORY
Hello Dev Team,
We are using RFA C++ 8.x (OMM) Linux API to retrieve real news (MRN_STORY).
Below is the configuration in our RFA.cfg file
\Connections\Connection_RSSL\connectionType = "RSSL"
\Connections\Connection_RSSL\rsslPort = "14002"
\Connections\Connection_RSSL\hostName = "new_adsA"
And below is the output of RFA log:
===============================
streamState : Open
dataState : Ok
statusCode : None
statusText : Login accepted by host s6xxxx..
serviceName : IDN_SELECTFEED
symbolName : MRN_STORY
streamState : Closed
dataState : Suspect
statusCode : NotFound
statusText : *The record could not be found.
===================================
To retrive MRN_STORY are additional parameters required in the RFA configuration file? Please advise.
Thank you.
Best Answer
-
The developer should implement this in the application. There is no RFA configuration for the domain name. The domain name could be specified as application configurations.
For example, the StarterConsumer example in the RFA package has two configuration files.
- ExampleRFA.cfg which contains RFA configurations for a connection such as hostName and rsslPort
- StarterConsumer.cfg which contains application configurations for a service name, and item name
The StarterConsumer example uses the RFA configuration database class to load StarterConsumer.cfg.
On the other hand, the example in the tutorial 11 reads application configurations from the command-line parameters.
Therefore, you can develop an application that loads the domain name configuration from the local file (StarterConsumer.cfg) like the StarterConsumer example by defining a new application configuration for the domain name type.
For more information, please refer to the StarterConsumer code in the StarterConsumer:Init(...) function.
//Load the application configuration data
if (!InitConfig(fileConfig)) return false;
ReadConfig(appCfgDataBase.ConfigTree);
LogConfig();0
Answers
-
It could be a domain type. The domain for MRN_STORY is the News Text Analytics domain, not the Market Price domain. Please refer to Tutorial 11 - Request and Decode Machine Readable News for more information.
0 -
Hello Jirapongse,
Thank you for the reply.
I checked the tutorial and downloaded the source code.
The MRN example is under "step 11" directory. And the "exampleRFA" here does not contain reference to NTA domain.
In which file should the NTA domain be specified?
Thank you.
0 -
In the Build and Run section of the tutorial, the domain is specified in the command-line parameters.
Command-line parameters:
-u <userName> : Permissioned user name (Mandatory)
-app <appId> : Permissioned application Id (Optional default = 256)
-pos <position> : Permissioned position (Optional, default=127.0.0.1/net)
-m <rdmModel> : name of the RDM model to request (Mandatory)
-s <serviceName> : Service name to subscribe from (Mandatory)
-i <itemName> : symbol to request (Mandatory)
-fd <rdmFieldDict> : Full path and filename of the RDM Field Dictionary
-ed <enumDict> : Full path and filename of the Enum Tables Dictionary
For News use "nta" for the "-m" parameter
Valid values for "-i" include MRN_TRNA, MRN_TRSI and MRN_STORY
Examples:
rdmexample -u j.smith -m nta -s EMEA_SAND_ERT_EDGE -i MRN_STORY
rdmexample -u j.smith -m nta -s EMEA_SAND_ERT_EDGE -i MRN_TRSI -fd "./RDMFieldDictionary" -ed "./enumtype.def"0 -
Hello Jirapongse,
Thanks very much for the example.
However, for a RFA C++ application that reads connection parameters from RFA configuration file, is there a way to specify the domain name in RFA configuration file or some other file? If so, what is the format of the parameter?
Thanks.
0 -
Hello Jirapongse,
Thank you for the information to resolve this matter. The application was using the default MarketPrice domain, after we changed to NTA, MRN news was able to retrieve.
0
Categories
- All Categories
- 6 AHS
- 37 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 中文论坛