Customization and Maintenance › Communication Port Maintenance › Change the JDBC Port Number

Change the JDBC Port Number

You can change the JDBC port number for communicating with the SA Store database. The JDBC port number is 1433 by default.

Follow these steps:

1. Stop all CA SOI services on the SA Manager and UI Server.
2. Open the following files on the SA Manager system, change the portnumber value in the listed sections, and save the changes:
   • SOI_HOME\tomcat\common\classes\hibernate.cfg.xml

     <session-factory>
           <!-- Database connection settings -->
           . . .
           <property name="connection.url">jdbc:jtds:sqlserver:
           //server:portnumber/SAMStore;instance=;
           </property>
           . . .
     </session-factory>
     

   • The following files located at SOI_HOME\tomcat\registry\topology\node0\sor:
     • restserver.xml
     • sorapp.xml
     • ssaserver.xml
     • ssaweb.xml

       <tns:persistenceManager inj:injID="pm">
       . . .
             <tns:dataSource inj:injID="dbconfig">
             <tns:url>jdbc:jtds:sqlserver://server:portnumber/
             SAMStore;instance=;socketKeepAlive=true;</tns:url>
       

   • SOI_HOME\ServiceDiscovery\connectivityContext.xml

     <bean id="dbSettings" class="com.ca.ssa.servicediscovery.loader.DBSettings">
           <property name="driver" value="net.sourceforge.jtds.jdbc.Driver" />
           <property name="url" value="jdbc:jtds:sqlserver://server:portnumber/SAMStore" />
     

     Note: Make this change in the '<!-- connectivity to the persistence store database -->' and the '<!-- connectivity to the SSA database -->' sections.

   • (Optional) SOI_HOME\tomcat\webapps\sam\thinuiconf\custom_metric_definition.xml

     Change the port number in the CONNECTION_URL property for each custom metric. This is only required if you have added custom Dashboard metrics that communicate on the same port as the SA Store.

   All SA Manager files contain the new JDBC port number.

3. Copy the SOI_HOME\tomcat\common\classes\hibernate.cfg.xml file on the SA Manager to <tomcat_path>\webapps\SpectrumSA on the report server, remove the <!DOCTYPE...> element at the top of the file, and save and close the file.

   Note: tomcat_path refers to the default BusinessObjects Tomcat installation directory of C:\Program Files\CA\SC\CommonReporting3\Tomcat55.

4. Select Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.

   The Central Configuration Manager dialog opens.

5. Select Apache Tomcat 5.5.20 and Server Intelligence Agent, click Stop, and then click Start when the services stop.

   The JDBC port number is changed on the report server.

6. (Optional) Open the SOI_HOME\SamUI\webapps\sam\thinuiconf\custom_metric_definition.xml file on the UI Server, change the port number in the CONNECTION_URL property for each custom metric, and save the changes.

   This step is only required if you have added custom Dashboard metrics that communicate on the same port as the SA Store.

7. Start the CA SOI Manager service on the SA Manager system.
8. Run registryloader.bat located at SOI_HOME\tomcat\registry. Ignore any "log4j:WARN" messages.

   The Registry loads an updated record of all CA Catalyst files in which you changed the port number.

9. Restart the CA SOI Manager service.
10. Change the port number in the listed sections of the following files on the SA Manager:
    • SOI_HOME\wso2registry\repository\conf\registry.xml

      <dbConfig name="wso2registry">
            <url>jdbc:jtds:sqlserver://server:portnumber/SAMStore;instance=
            </url>
      

    • SOI_HOME\wso2registry\repository\conf\user-mgt.xml

      <Configuration>
      . . .
            <Property name="url">jdbc:jtds:sqlserver
            ://server:portnumber/SAMStore;instance=</Property>
      

    The files used to load the CA Catalyst Registry contain the new port number.

11. Start all CA SOI services on the SA Manager and UI Server.

    The port number change takes effect.