We are using RFA8/C++ is it possible to provide parameter while calling rfa::sessionLayer::Sessio...
Best Answer
-
Hi @mktdata,
Not all properties are automatically configurable within the RFA configuration. The Login credentials are not available within the standard configuration definitions. However, you can easily define your own application-specific configuration properties to achieve your goals. For example, within your rfa configuration file, you can do something like this:
\App\Login\user = "John Doe"
\App\Login\appid = "255"
\App\Login\position = "127.0.0.1"These definitions will be included within the configuration database which you can access from code. Refer to the Examples/Consumer/ConsumerConfig.cpp for reference.
0
Answers
-
Hi @mktdata,
The Session::acquire does accept a string (name) parameter but I'm thinking you are asking for something else. It would be more helpful if you were to describe what you are trying to do.
0 -
We have requirement to add parameter applicationKey to the data connection and make it configurable. Similar to DACS_APP_NAME that is used on dacs connections. Right now we provide session name to Session::acquire and function takes only one parameter.
0 -
we have Linux RFA client with custom config file, have found sample:
./HybridApp/RDMConsumerClient.cpp
it uses MMT_LOGIN to send ApplicationId via rfa::message::AttribInfoelement.setName( rfa::rdm::ENAME_APP_ID );
RFA_String sAppId;
sAppId.set( "256", 3, false );elementData.setFromString( sAppId, DataBuffer::StringAsciiEnum );
element.setData( elementData );
elwiter.bind( element );
not sure that what we need, but will try. Thank you for your help.
0 -
For OMM interface, there is a concept of Login interface which the application has to send a new Login request to the Provider server. It needs to set the login information in AttributeInfo so that there is no RFA configuration to support your requirement. As Nick said, you have to create a separate application's configuration to set the login information and then read the values from RFA application and pass it to the Login AttributeInfo.
Anyway, in the new version of RFA such as 7.6.2 or 8.x, we have a simple RFA consumer example StarterConsumer which provide an application configuration in a file named "StarterConsumer.cfg". The user can set the login information in the file instead. If you want to see sample codes you can try the StarterConsumer example and see the implementation in StarterConsumer.cpp.
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
- 687 Datastream
- 1.4K DSS
- 622 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 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
- 674 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛