ServiceDiscovery connector showing isSystemUp() returned false
search cancel

ServiceDiscovery connector showing isSystemUp() returned false

book

Article ID: 225186

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

ServiceDiscovery connector is showing error 

Connector error occurred: Connector is reporting problem interfacing with the domain manager. isSystemUp() returned false

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Resolution

The problem with the ServiceDiscovery connector error was due to the \soi\ServiceDiscovery\connectivityContext.xml file not having the correct DB connection values.

<property name="driverClassName" value="@samstore_driver@" />
<property name="url" value="@samstore_url@" />
<property name="username" value="@samstore_login@" />
<property name="password" value="@samstore_password_crypted@" />

 

To fix problem,  

Take the values from section <tns:dataSource inj:injID="dbconfig"> in the  \soi\tomcat\registry\topology\physical\node0\sor\sorapp.xml

<tns:url>jdbc:jtds:sqlserver://hostname:1433/SAMStore;instance=;socketKeepAlive=true;</tns:url>
<tns:username>Username</tns:username>
<tns:password>EncryptedPassword</tns:password>
<tns:driverClassName>net.sourceforge.jtds.jdbc.Driver</tns:driverClassName>

 

edit connectivityContext.xml and fill in the missing values 

 

<property name="driverClassName" value="net.sourceforge.jtds.jdbc.Driver" />
<property name="url" value="jdbc:jtds:sqlserver://hostname:1433/SAMStore" />
<property name="username" value="Username" />
<property name="password" value="EncryptedPassword" />

 

Stop/Start CA SAM Integration Services