question

Upvotes
Accepted
36 4 3 14

DACS is not available

Greetings All

We currently encountered an issue on RFA client, seems something wrong on DACS authentication, the logs is as below:

2016-08-09 14:28:14 [com.abchina.sdc.pe.RFAEventClient]-[INFO] Received CONNECTION_EVENT: _Default::SSLConn { state: UP, code: NONE, text: "p2ps2"}
2016-08-09 14:28:14 [com.abchina.sdc.pe.RFAEventClient]-[INFO] Received MARKET_DATA_SVC_EVENT: MARKET_DATA_SVC_EVENT, Service Name = ATS_TEST, Data Dictionary List = {MarketFeed}, Quality Of Service List = {(Unspecified, Unspecified) - 1}, Service Status = { state: UP, code: NONE, text: "Service Up"}

2016-08-09 14:28:14 [com.abchina.sdc.pe.RFAEventClient]-[INFO] Received MARKET_DATA_SVC_EVENT: MARKET_DATA_SVC_EVENT, Service Name = IDN_SELECTFEED, Data Dictionary List = {MarketFeed}, Quality Of Service List = {(Unspecified, Unspecified) - 1}, Service Status = { state: UP, code: NONE, text: "Service Up"}

2016-08-09 14:28:14 [com.abchina.sdc.pe.RFAEventClient]-[INFO] Received MARKET_DATA_ITEM_EVENT (status), service = IDN_SELECTFEED, msgType = STATUS, item = DKKCNY7D=, status = { state: CLOSED, code: NO_PERMISSION, text: "DACS is not available for dbuser+256+10.233.81.87/VL-Dev-2269.localdomain: {1}"}

Also, the configuration xml is as attached:

Any suggestion to debug please?

treprfarfa-apiDACS
icon clock
10 |1500

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

Upvotes
Accepted
9.5k 10 5 7

The error can happen when RFA Java cannot connect to DACS system e.g. DACS server may be down. There are 2 ways to fix the problem

A)If the client is migrating from RTIC to ADS, the client should disable RFA to connect to DACS system. Normally, ADS does this; the entitlement is performed at ADS site. On the other hand, when RFAJ connects to RTIC, RFAJ connects to DACS system; the entitlement is performed at RFA site.To disable entitlement done by RFA process(let ADS perform this), all dacs_xxx configuration parameters are false as example below:

<node name="SSLConn"> 
   <map>         
	<entry key="connectionType" value="SSL"/>         
	...        
	<entry key="dacs_CbeEnabled" value="false"/>        
	<entry key="dacs_GenerateLocks" value="false"/>        
	<entry key="dacs_SbePubEnabled" value="false"/>         
	<entry key="dacs_SbeSubEnabled" value="false"/>         
        <entry key="dacs_NewsCbeLogEnabled" value="false"/>         
        <entry key="dacs_NewsCbeEnabled" value="false"/>      
    </map> 
</node> 

B) If the application connecting to ADS works with entitlement done by RFA before; RFA connects to DACS system and entitlement is performed at RFA site. The client should contact to DACS system admin to verify why RFAJ cannot connect DACS system e.g. DACS server goes down or not. If DACS system is owned by Thomson Reuters, the client should contact the account team otherwise he should contact his DACS system admin.

icon clock
10 |1500

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

Upvotes
36 4 3 14

Hi Pimchaya

Thank you for your reply, we confirmed the DACS has just been disabled from upstream, in order to make any user access data without limit.

According to your suggestion, seems we have to add below configuration items for RFA client? Am I right?

<node name="SSLConn"> 
   <map>         
	<entry key="connectionType" value="SSL"/>         
	...        
	<entry key="dacs_CbeEnabled" value="false"/>        
	<entry key="dacs_GenerateLocks" value="false"/>        
	<entry key="dacs_SbePubEnabled" value="false"/>         
	<entry key="dacs_SbeSubEnabled" value="false"/>         
        <entry key="dacs_NewsCbeLogEnabled" value="false"/>         
        <entry key="dacs_NewsCbeEnabled" value="false"/>      
    </map> 
</node> 
icon clock
10 |1500

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

Yes. You should set all dacs_xxx parameters to be false as my example configuration. For more details of SSL configuration parameters, please refer to section SSL Connection in RFAJ_ConfigLoggingGuide.pdf