Is it possible to configure a RFAC++ application using the MD interface to connect to a remote da...

...cs_snkd?
Is it possible to configure
a RFAC++ application using the MD
interface to connect to a dacs_snkd on another system for permissioning. I
believe this can be configured using the DACSMUXNAME environment variable and
an ipcroute file. Can you provide the instructions how to do this?
Best Answer
-
Applications
can configure to connect to a DACS Sink Daemon (dacs.snkd) that does not reside
on the localhost with the application. This
is useful in cases where installing a local DACS daemon is not appropriate,
with the understanding that performance will be degraded.Ensure
that you have configured RFA to use a remote DACS daemon. This requires
the following steps:1.Add
the following to the services file:dacs_lib
8211/tcp2.Two
environment variables must be set correctly.- The DACSMUXNAME
environment variable is used to inform the DACS Library that the DACS daemon is
located on a different machine then the DACS Library. Define this variable and
set it equal to "dacs_lib.sink" so that it may be used in the
ipcroute file to specify the location of the DACS daemon.
For example (on a UNIX machine)
DACSMUXNAME="dacs_lib.sink"
- The DACSMUXPING
environment variable is used to inform the DACS Library that heartbeat messages
should be sent between the DACS Library and the DACS daemon. This option should
only be used when the DACSMUXNAME option is being used.
DACSMUXPING="true"
3.
Once the above variables have been successfully configured, add the following
line to your ipcroute file to complete the configuration. (If the ipcroute file
doesn't already exist, you will need to create one.)dacs_lib.sink:<localhost>:<host_with_dacs_daemon>
Note that this line can
contain a space separated list of <host_with_dacs_daemon> just like when
listing multiple Sink Distributors to which an SSL application can connect.dacs_lib.sink:local_hostname:remote_dacs_hostname1, remote_dacs_hostname2
The ipcroute file should be in the
working directory of the application, or in another location where it will be
found by SSL lib used by RFA.If
the connection to remote_dacshostname1 fails, RFA
will attempt a connection to remote_dacs_hostname2.0 - The DACSMUXNAME
Answers
-
Thanks for the information. I have
this working.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 中文论坛