Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • RFA /
avatar image
REFINITIV
Question by LtDoolittle6 · Oct 17, 2017 at 08:48 PM · rfac++dacs-daemonpermissioningdacs_snkdmd

Is it possible to configure a RFAC++ application using the MD interface to connect to a remote dacs_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?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by moragodkrit.chumsri_1 · Oct 17, 2017 at 09:30 PM

@Rupert Schilling

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/tcp

2.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.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
REFINITIV
LtDoolittle6 · Oct 17, 2017 at 10:15 PM 0
Share

Thanks for the information. I have this working.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
6 People are following this question.

Related Questions

What does blank value during closing run interpret as?

Can I configuring RFA to use particular ethernet card?

How to get tick size of a FX instrument?

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges