UPA Consumer App connecting to multiple Providers simultaneously...

I am not clear about the Transport to Channel multiplexing. Does the Transport support multiple Channels each connecting to different providers? I would like to connect to different ADSes in one consumer App.
Best Answer
-
UPA supports multiple connections to ADSs. Application can create RSSL channel separately for each connection and also needs to perform separated set of the administrative domains (such as Login, Source Directory, and Dictionary) including item requests on each channel.
The rsslVAConsumer example is implemented to demonstrate the multiple connections handling. You can try the application with the following command line.
rsslVAConsumer.exe -tcp <ADS1's IP address>:14002 <service name on ADS1> mp:TRI -tcp <ADS2's IP address>:14002 <service name on ADS2> mp:.DJI
0
Answers
-
One consumer app can connect to different ADSs, when different providers are available from them, by connecting to multiple channel sessions and maintaining them. Please refer to EDFConsumer example in UPA kit, to see how multiple sessions are connected and maintained.
0 -
TREP is an infrastructure to present multiple service providers through a single fault-tolerant and reliable connection. Service providers are distinguished by a name and id tuple and are specified when subscribing to an item stream. The provider id is discovered at run time by enumerating a source directory response from the source infrastructure.
It is recommended to use TREP for provider aggregation as that is its primary purpose.
Connecting to multiple TREP infrastructures, or simply two ADS endpoints within a single TREP infrastructure is necessary to implement warm or hot standby whereby subscriptions would be submitted to both connections simultaneously.
Each RSSL connection requires its own RSSL channel and requires that the application perform the connection, login, optional directory and dictionary requests independently to each channel. This must be implemented by the application developer or one can take advantage of the ValueAdd RsslReactor library to provide an object and thread per channel.
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
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 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
- 275 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
- 652 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
- 228 TRKD
- 917 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
- 46 中文论坛