Multiple servers and services in a single RFA configuration file
Hi everyone,
If we have just one RFA configuration file, is it possible to specify 2 different servers that provide 2 different feeds?
For example, is it possible to include the following details in one RFA configuration file:
# Connection to serverC to get feed C
connectionType = "SSLED"
PortNumber = 8201
serverList = "IP address of serverC that provides feed C"
serviceList = feed C
# Connection to serverX to get feed X
connectionType = "SSLED"
PortNumber = 8101
serverList = "IP address of serverX that provide feed X"
serviceList = feed X
And if this is possible, would someone kindly guide me on how to use RFA API to look at this single RFA file and the 2 feeds C and X?
For example, what parameters do we specify in the RFA methods, to distinguish between feed C and feed X etc
Thank you very much.
Best Answer
-
Hi @s0nny
Assuming that feed C and feed X are published using different service names, you can create two Connections and then reference those two connections in the Session that you acquire() in your code
e.g.
\Connections\Connection_SSLED1\PortNumber = 8101
\Connections\Connection_SSLED1\UserName = "<username>"
\Connections\Connection_SSLED1\ServerList = "<serverList>"
\Connections\Connection_SSLED1\connectionType = "SSLED"
\Connections\Connection_SSLED2\PortNumber = 8201
\Connections\Connection_SSLED2\UserName = "<username>"
\Connections\Connection_SSLED2\ServerList = "<serverList>"
\Connections\Connection_SSLED2\connectionType = "SSLED"
\Sessions\Session1\connectionList = "Connection_SSLED1,Connection_SSLED2"In your code
pSession = Session::acquire(RFA_String("Session1", 0, false));
Note that the serviceList parameter is normally only used for remapping service names e.g. if two servers are both publishing services with the same name.
0
Answers
-
Thank you very much Umer,
As i don't have access to the RFA folders belonging to other teams, would you share or let me know where to find the RFA Java document?
So as to understand more about the acquire() method.
I assume 0 means the first parameter in connectionList?0 -
Hi @s0nny
The RFA Java documentation is available at Documentation | Refinitiv Developers
However, as you are working with the Legacy SSLED interface, you may find you have to download an older RFA version and extract the documentation from the Legacy\Docs folder on the zip file.
The RFA config guide will contain further details on the config file parameters and the Developer guide will have more details on the Session::acquire usage.
The above config and code snippet I quoted was for RFA C++, for RFA Java the code would be something like:
_session = Session.acquire("Session1");
Not sure what you mean about first parameter in the Session list?
When you acquire a session, you are 'establishing a connection' between your application and both the servers. Once you acquire this single session, you can use that session to subscribe instruments from both services by setting the required service name in the MarketDataItemSub request.
If, however, you want to use separate sessions for each server - you are can do so, by defining 2 sessions - one for each connection and then acquiring each session individually.
1
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛