Upgrading Shared-Disk Instances

Upgrade an SAP Control Center server instance (one of several SCC servers and SCC agents running from a single installation on a shared disk) by copying key files in the repository.

Prerequisites

Install the latest version of SCC before upgrading.

If you are running multiple SCC server instances, install the latest version of SCC into a different directory from the earlier version. When you upgrade from SCC 3.2.x (that is, any 3.2 version) to SCC 3.3, the installer creates a new directory for SCC 3.3 by default.

If you used the earlier version of SAP Control Center to manage and monitor more than one type of resource (Adaptive Server, Data Assurance, SAP Sybase Event Stream Processor, SAP Sybase IQ, Replication Server, Replication Agent, Mirror Replication Agent), install the same set of product module plug-ins with the new version of SCC.

Task
  1. Enable shared-disk mode in the new installation directory. In SCC-3_3\bin, enter:
    sccinstance -enable
  2. In the new installation directory, deploy instances corresponding to those deployed in the earlier version. For example, enter this in SCC-3_3\bin to deploy a server instance called Boston:
    • Windows –

      sccinstance -create -server -instance Boston -service

    • UNIX –

      sccinstance -create -server -instance Boston

    For more information on deploying instances, see Get Started > Deploying an Instance from a Shared Disk Installation in the online help.

  3. Shut down all instances of SCC—both old and new versions.
  4. Navigate to the installation location of the earlier version of SCC on the shared disk.
  5. Copy the earlier-version scc_repository.db, scc_repository.log, and service-config.xml files from the Repository directory. For example:
    Windows –
    • %SYBASE%\SCC-3_2\instances\<instance-name>\services\Repository\scc_repository.db
    • %SYBASE%\SCC-3_2\instances\<instance-name>\services\Repository\scc_repository.log
    • %SYBASE%\SCC-3_2\instances\<instance-name>\services\Repository\service-config.xml
    UNIX –
    • $SYBASE/SCC-3_2/instances/<instance-name>/services/Repository/scc_repository.db
    • $SYBASE/SCC-3_2/instances/<instance-name>/services/Repository/scc_repository.log
    • $SYBASE/SCC-3_2/instances/<instance-name>/services/Repository/service-config.xml
  6. Paste the copied files into the corresponding instance directory of the latest installed version. For example:
    C:\Sybase\SCC-3_3\instances\<instance-name>\services\Repository.
  7. Copy the earlier-version service-config.xml file from the SccSADataserver directory. For example:

    Windows – %SYBASE%\SCC-3_2\instances\<instance-name>\services\SccSADataserver\service-config.xml

    UNIX – $SYBASE/SCC-3_2/instances/<instance-name>/services/SccSADataserver/service-config.xml

  8. Paste the copied files into the corresponding instance directory of the latest installed version. For example:
    C:\Sybase\SCC-3_3\instances\<instance-name>\services\SccSADataserver.
  9. Determine whether, in the earlier version of SCC, you changed the truststore or keystore password in this file:

    Windows – %SYBASE%\SCC-3_2\instances\<instance-name>\services\EmbeddedWebContainer\service-config.xml

    UNIX – $SYBASE/SCC-3_2/instances/<instance-name>/services/EmbeddedWebContainer/service-config.xml

    If so, copy the file into the corresponding directory of the latest installed version.
  10. Determine whether, in the earlier version of SCC, you modified this file (to add a password for the sccadmin account, for example):

    In SCC 3.2.5 or earlier: SCC-3_2/conf/csi.properties

    In SCC 3.2.6 or later: SCC-3_2/conf/csi_config.xml

    If you did, make the same changes to SCC-3_3/conf/csi_config.xml in the latest version. Note that in SCC 3.2.6, the name and format of the CSI file changed and the sccuser account was removed.
    Note: SAP recommends that you not use login accounts defined in csi_config.xml in a production environment. See the Get Started > Setting up Security section of the SAP Control Center online help for instructions on configuring authentication through LDAP or the operating system.
  11. Start each instance of the new version of SCC.
    When you start the latest-version server with the earlier-version repository, the repository automatically migrates to the most current version.
Parent topic: Upgrading SAP Control Center