Skip to content
CA Service Operations Insight - 4.0 CU1, SP2
Documentation powered by DocOps

Move the SA Store to a Remote Database Server

Last update September 1, 2015

As an administrator, you can move the SA Store database to a different database server as long as the new database server allows the same Microsoft SQL Server user name and password for database access. After moving the database, you edit various configuration files to help ensure that product components communicate with the database at its new location.

Follow these steps:

  1. Stop all CA SOI services.
  2. Perform a full backup of the SA Store database and restore it to the remote Microsoft SQL Server.
  3. Open the <SOI_HOME>\ServiceDiscovery\connectivityContext.xml files on the SA Manager, change the database server name in the ssaDB.url property, and save the file.
  4. Change the database server name in the following SA Manager files and save them:
    <SOI_HOME>\tomcat\lib\hibernate.cfg.xml
    <SOI_HOME>\tomcat\registry\topology\physical\node0\sor\restserver.xml
    <SOI_HOME>\tomcat\registry\topology\physical\node0\sor\sorapp.xml
    <SOI_HOME>\tomcat\registry\topology\physical\node0\sor\ssaserver.xml
    <SOI_HOME>\tomcat\registry\topology\physical\node0\sor\ssaweb.xml
    <SOI_HOME>\wso2registry\repository\conf\registry.xml
    <SOI_HOME>\wso2registry\repository\conf\user-mgmt.xml 

    Note: For the changes in the regitsry files to take effect, execute the registryLoader.bat file in <SOI_HOME>\tomcat\registry.
  5. Start the CA SOI services.
    The changes are applied.
  6. Locate the <Tomcat_HOME>\webapps\SpectrumSA\hibernate.cfg.xml file on the report server, change the database server name in the connection.url property, and save the file.
  7. Change the database server name in the following files and save them:
    <SOI_HOME>\wso2registry\repository\conf\registry.xml
    <SOI_HOME>\wso2registry\repository\conf\user-mgmt.xml

  8. Select Start, Programs, BusinessObjects XI 3.x, BusinessObjects Enterprise, Central Configuration Manager.
    The Central Configuration Manager dialog opens.
  9. Select Apache Tomcat and Server Intelligence Agent, click Stop, and then click Start when the services stop.
    The database server name is changed on the report server.
  10. Open the <SOI_HOME>\Reports\samreports.xml file on the report server, update the database server name, and save the file.
    Future report redeployments will use the new database connection password.
  11. Change the database server name in the following files and save them:
    <SOI_HOME>\Reports\samreports.xml 
    <SOI_HOME>\Reports\deploy\hibernate.cfg.xml

  12. (Optional) Do the following to reenable custom prompt pages:

    Note: This step is only necessary if you have previously enabled custom report prompt pages.
    1. Select Start, Programs, BusinessObjects XI 3.x, BusinessObjects Enterprise, 32-bit Data Source (ODBC).
      The ODBC Data Source Administrator dialog opens.
    2. Select the System DSN tab, select SAMStore, update the database server name, and apply the change.
      The ODBC connection uses the correct database server name.
    3. Select Start, Programs, BusinessObjects XI 3.x, BusinessObjects Enterprise, Central Configuration Manager.
      The Central Configuration Manager dialog opens.
    4. Select Apache Tomcat and Server Intelligence Agent, click Stop, and then click Start when the services stop.
    5. Enter the following URL in a web browser:

      http://localhost:<BOServer_port>/SpectrumSA/CustomSSA.jsp
      

      The Spectrum SA Report Initialization page opens.

    6. Enter the correct information and click Update Reports.
      This sets the CA SOI report type to SI_CA_REPORT_TYPE. A confirmation page opens and custom parameter pages now display when you run CA SOI reports if the operation was successful.
    All product components can now communicate with the moved SA Store database.
Was this helpful?

Please log in to post comments.