Connecting Data Center Security Server to migrated SQL database

Products

• Data Center Security Server Advanced
• Data Center Security Server
• Data Center Security Monitoring Edition

Issue/Introduction

The Data Center Security(DCS) database was migrated to a to a different server and the server.xml needs to be updated to connect to the new database

Environment

 

Resolution

After the DCS SQL database has been migrated to a new instance, the "server.xml" file needs to be updated with the new database info so that the manager can communicate:

Steps to modify the server.xml:

 

1. Stop the DCS manager services on all DCS managers in the environment

2. Navigate to the server.xml file in the default directory shown below:

"InstallDirectory":\Program Files (x86)\Symantec\Data Center Security Server\Server\tomcat\conf\server.xml"

3. Create a copy of the server.xml and save it somewhere outside of the tomcat folder

 

4. Open the server.xml with notepad

 

5.  There will be three lines in the server.xml file that each begin with a "<Resource auth=" tag

<Resource auth="Container" driverClassName="net.sourceforge.jtds.jdbc.Driver"
    factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" initialSize="25" logAbandoned="true"
    maxActive="75" maxIdle="50" maxWait="30000" minEvictableIdleTimeMillis="55000" minIdle="25"
    name="Database-Console" password="1234567890abcdefghijklmnopqrstuvwxyzABCD"
    removeAbandoned="true" removeAbandonedTimeout="300" testOnBorrow="true"
    timeBetweenEvictionRunsMillis="34000" type="javax.sql.DataSource"
    url="jdbc:jtds:sqlserver://192.0.2.223/SCSPDB;instance=scsp;integratedSecurity=false"
    username="scsp_ops" validationInterval="34000" validationQuery="SELECT 1"/>
<Resource auth="Container" driverClassName="net.sourceforge.jtds.jdbc.Driver"
    factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" initialSize="125" logAbandoned="true"
    maxActive="425" maxIdle="175" maxWait="30000" minEvictableIdleTimeMillis="55000"
    minIdle="125" name="Database-Agent" password="1234567890abcdefghijklmnopqrstuvwxyzABCD"
    removeAbandoned="true" removeAbandonedTimeout="300" testOnBorrow="true"
    timeBetweenEvictionRunsMillis="34000" type="javax.sql.DataSource"
    url="jdbc:jtds:sqlserver://192.0.2.223/SCSPDB;instance=scsp;integratedSecurity=false"
    username="scsp_ops" validationInterval="34000" validationQuery="SELECT 1"/>
<!-- UMC DB Resource -->
<Resource auth="Container" driverClassName="net.sourceforge.jtds.jdbc.Driver"
    factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" initialSize="34" logAbandoned="true"
    maxActive="277" maxIdle="233" maxWait="30000" minEvictableIdleTimeMillis="55000" minIdle="89"
    name="Database-UMC" password="1234567890abcdefghijklmnopqrstuvwxyzABCD"
    removeAbandoned="true" removeAbandonedTimeout="300" testOnBorrow="true"
    timeBetweenEvictionRunsMillis="34000" type="javax.sql.DataSource"
    url="jdbc:jtds:sqlserver://192.0.2.223/dcsc_umc;instance=scsp;integratedSecurity=false"
    username="umcadmin" validationInterval="34000" validationQuery="SELECT 1"/>

 

6. Update all of the entries showing the following "url" in the server.xml to reflect the new SQL server IP/Instance info

url="jdbc:jtds:sqlserver://192.0.2.223/SCSPDB;instance=scsp;integratedSecurity=false"

Note**In the above example the "192.0.2.223" entry will need to be updated to the new hostname/IP of the migrated database to reflect your environment

7. Save the server.xml to the default directory

8. Start the DCS manager services

9. Check to ensure there is database connectivity and that you can log into the UMC