How does RTRSSLRTRecordService processes the serverList
I wanted to know the behavior of RTRSSLRTRecordService. How does it processes the serverList.
For instance i have serverList as : 192.168.107.132 192.168.107.133 192.168.107.130
How will it process this list.
Best Answer
-
Yes, you will see a log in SSL.log for each fail connection.
But printing connected server require some work.
Right now, you probably doing something like this:
service = new RTRSSLRTRecordService(appId, servicename, "192.168.107.132 192.168.107.133");
In the above case, RTRSSLRTRecordService is creating and managing a RTRSSLConnection for you. RTRSSLConnection class encapsulates a connection to an upstream, and it allows you to add client for connection event.
But since you want to know the server that you have connected, you need to received connection event, which also means you have to create and manage RTRSSLConnection yourself.
connection = new RTRSSLConnection(appId, "sslDispatcher");
connection->userName("user");
connection->serverList("192.168.107.132 192.168.107.133");
connection->port(8101);
service = new RTRSSLRTRecordService(appId, servicename, *connection);Instead of passing serverList, you have to create and pass RTRSSLConnection to RTRSSLRTRecordService.
Then, you have to add a client to RTRSSLConnection and connect.connection->addClient(*client);
connection->connect();The client class must inherits RTRMDConnectionClient and implements
void processConnected(RTRMDConnection &)
and
void processNotConnected(RTRMDConnection &)
Finally, in processConnected, you can call RTRMDConnection.host() for host name.
0
Answers
-
Hi @vsharma
The list is a failover list. SFC will process the list in order. When a connection to one of the server fail, SFC attempts to connect to the next server in the list.
But please note that failover only occurs when the connection to a server breaks. It do not occur when server reject login.
As a result, the redundant server in the list should have identical sets of user interests; i.e. user entitlements, available services(s), service capabilities, item availabilities, etc.
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 中文论坛