Previous Topic: Review the Upgrade OrderNext Topic: Provisioning Server and CA IAM Connector Server Upgrade


CA Directory Upgrade

Upgrade the CA Directory server before you upgrade other servers in your deployment. If you have multiple CA Directory Servers in a high availability environment, upgrade the primary CA Directory first.

Follow these steps:

  1. SSH into the system to be upgraded.
  2. Navigate to this directory.
    /opt/CA/saas/repo/application/
    

    If this directory has an upgradeBackupList.sh file, it includes a BACKUP_LIST environment variable. It is an array enclosed in parentheses. This variable defines files that are backed up before the upgrade and restored after the upgrade.

    You can add or remove file names from this list as necessary. Insert the filenames in each set of quotes separated by spaces and inside the parenthesis.

  3. Verify that a backup of the /tmp/properties.sh file from the previous version exists.
  4. Unzip the new kit for the system being upgraded into the root file system folder. For example, enter the following commands:
    cd /
    unzip -o CAM-DIR_kit-version.zip
    
  5. Update the /tmp/properties.sh file in the kit with information from the backup version of properties.sh:
    1. Diff the backup file of the previous install and /tmp/properties.sh by entering the following command:
      diff /serverkit/properties.sh /tmp/properties.sh
      

      The preceding command assumes that backup files are located in the /serverkit folder.

    2. Make appropriate changes to the /tmp/properties.sh file.
    3. If you have downloaded the Java kit to upgrade Java before the CA CloudMinder upgrade, modify the property "JAVA64_KIT" to use "jdk-7u40-linux-x64.tar.gz" instead of "jdk-6u45-linux-x64.bin" as in this example:

JAVA64_KIT=/JDK-Installation-Directory/jdk-7u40-linux-x64.tar.gz; export JAVA64_KIT

  1. Run the upgrade by entering the following commands:
    cd /opt/CA/saas/repo/application/
    ./appliance_local.sh   config
    

Verify the upgrade

Verify all DSAs and DSA services, such as the Dxagent Webservices, are running. Enter the following commands:

su - dsa
dxserver status
exit
ps -ef|grep dx