RFA application connecting to multiple DAC daemons
Hello,
We are using RFA 8.1 C++ api's to consume market data. One of our mutual client checking on possibility of connecting same RFA application to multiple DAC daemons. This is because they have multiple DACS site set up based on the region. Is it possible? Can you point me to sample application which does that?
Best Answer
-
Thanks for reaching out to us.
You need to use OpenDACS API to acquire multiple DACSMC.
You can refer to the dacsMultiConnectSubscribeClient example in the OpenDACS C++ package. This example demonstrates how to use OpenDACS API multiconnection feature to connect with several DACS sink daemons that locate in different hosts (or the same host as the example).
I hope that this information is of help.
1
Answers
-
@Jirapongse Thank you. I will give it a try and let you know.0
-
@Jirapongse Our mutual client is planning to use two separate DAC daemon sites. They have provided us two different ports 8211 & 8230 where RFA application should connect. How can I configure it? Should I have two entries in /etc/services? Until now we followed below steps for single DAC daemon site but not sure how can we do it for multiple DAC Daemon sites.
0 -
The RFA itself can't connect to multiple DACS Daemon sites at the same time. It can connect to one DACS Sink Daemon at a time. To connect to multiple DACS Daemon, you need to use OpenDACS API instead.
0 -
@Jirapongse Yes we plan to use Open DACS C++ api to do so. I understand DACMC feature of Open DACS api. It allows specifying list of ip addresses while acquiring connection to DAC Daemon. It will get locked with first IP that has DAC Daemon processes running and login will be sent to that DAC site.
Our requirement is different. We want to connect to multiple DAC Daemon sites one by one until we find out a DAC site where given user is authorized. Consider following example -
- Let's say we have user "PT1".
- There are two DAC sites, "Site A" & "Site B".
- We will acquire "Site A" connection first and try logging in "PT1" user with "Site A" but it gets logged out as "PT1" is not authorized on "Site A"
- We then acquire "Site B" connection and try logging in "PT1" user with "Site B" and it gets logged in there.
Is this possible?
Also out of two DAC sites, one intend to use non standard port(other than 8211) so is it possible?
0 -
Yes, you can have multiple AuthorizaionSystem MC instances. Each instance connects to a DACS Sink Daemon. You can specify the hostnames (IP addresses) and TCP port in the parameter.
Then, create AuthorizationAgent instances from each AuthorizaionSystem instance. Next, create AuthorizationAgent instances to log in to the AuthorizaionSystem instances.
The diagram looks like this:
0 -
@Jirapongse So what you suggest is I should try connecting "PT1" to "Daemon1 (on port 8211)" first. If "PT1" gets logged out then I should try connecting to "Daemon2 (on port 8230)"?
If at all I will be connecting to each connection one by one then why it needs to be "DACSMC" , "DACS" should work right?0 -
Yes, DACSMC is able to connect to one DACS sink daemon.
As I know, the "DACS" AuthorizationSystem instance connects to a DACS sink daemon running on the local machine unless the DACSMUXNAME environment variable has been set.
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 中文论坛