RFA Configuration: Need rfa.cfg to connect to two SSL sources simultaneously App built with rfa 7.6

I'd very much appreciate your help! I would like to know how to configure my rfa.cfg file to subscribe to two SSL sources.
Details:
Collocated ADH/ADS server with C++ RFA 7.6 32-bit application configured as subscriber (createMarketDataSubscriber) on a route which is sink-driven. I have two Interactive providers supporting routes 1 & 2. Each route (route1 & route2) is configured for SSL.
The application works fine when it is configured to connect to either of the two routes, Session1 or Session2. However, as soon as two routes are specified within the application runtime, data from only one of the sources comes through. I've stepped through the code and can see that the application executes subscription requests on both routes,
Here is what I have:
I have guessed that my issue relates to "horizontal scaling" and so I have added the line "Adapter\SSLED_ADAPTER\singleton = false" but this is a complete guess based on an answer to a similar question relating to RSSL in this community and it doesn't seem fix my issue.
ADHMON & ADSMON tells me i have the routes active:
I have been told that the application has connected to both routes simultaneously and successfully but that was in a configuration where there were two instances of ADH/ADS running on separate machines and distinct from the machine hosting the application.
Any help or insight would be much appreciated!
Best Answer
-
After more investigation, it turned out that the RFAREC source was not publishing RICs with the expected names and so the subscription string was not matching. I misinterpreted the failure for the subscriber to receive data as a problem with the configuration of ADH/ADS and the subscribers rfa configuration. Once the RFAREC PROVIDER was corrected everything worked as expected.
0
Answers
-
Thanks for reaching out to us.
Instead of using multiple sessions, you can add another connection into the connectionList configuration instead.
\Sessions\Session1\connectionList= "Connection_SSLED, Connection_SSLED2"
With this configuration, Session1 will create connections to tfd-redhat1:8101 and tfd-redhat1:8201 and the application can subscribe to any services available on those servers.
0 -
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 中文论坛