Upgrade Guide › How to Upgrade CA CloudMinder › Upgrade the CA SiteMinder Policy Server and CSP console

Upgrade the CA SiteMinder Policy Server and CSP console

After you upgrade the Provisioning Server and CA IAM Connector Server, upgrade the CA SiteMinder Policy Server and the CSP Console.

Note: Repeat these steps to upgrade each SiteMinder Policy Server as well as your CSP console. You use the same kit to upgrade both the CSP console and the SiteMinder Policy Server.

Follow these steps:

1. SSH into the machine to be upgraded.
2. Verify that a backup of the /tmp/properties.sh file exists for SiteMinder Policy Server and for the CSP console.
3. Enter the following commands on the system where the CA SiteMinder Policy Server or CSP console is installed.

   su - root
   

   mv /dev/random /dev/random.orig 
   

   ln -s /dev/urandom /dev/random
   

4. If it is running, stop the RiskMinder case manager using the following sub-steps:

   ps -ef|grep arrfcasemgmtserver
   

   If the preceding command shows any running processes, stop it using the following command:

   cd /opt/CA/AdvancedAuth/bin
   ./casemanagementserver stop
   

5. Set the following properties in the backup version of properties.sh:

   _hco_name=DefaultHostSettings; export _hco_name # Host Configuration Object

6. Unzip the new kit for the machine being upgraded into the root file system folder. For example, enter the following commands:

   cd /
   unzip -o CAM-SMPS_kit-version.zip
   

7. Update the tmp/properties.sh file in the kit with information from the backup version of properties.sh:
   1. Diff the original properties.sh file and the tmp/properties file by entering the following command:

      diff -y /serverkit/properties.sh /tmp/properties.sh
      

   2. Make appropriate changes to the /tmp/properties.sh file as required.

   _hco_name=DefaultHostSettings; export _hco_name # Host Configuration Object

8. Run the upgrade by entering the following commands:

Note: If the following directory has a file named upgradeBackupList.sh, it will have an environment variable named BACKUP_LIST. This variable is an array of file names that will be backed up before the upgrade, and then restored after the upgrade. You may add or remove file names from this list as necessary.

cd /opt/CA/saas/repo/application/

./appliance_local.sh   config

Verify the Upgrade

1. Verify dxserver status
   1. su – dsa
   2. dxserver status

      Verify that one "tenantname-tenant-router started" message exists for each tenant in the environment.

   Note: Only perform the next step for the CSP Console.

2. Verify that the CSP Console is working properly by making sure the tenant and container tasks exist by issuing the following command:

   ps -ef | grep ui
   

   If working properly, you should see a message similar to the following:

   00:00:00 /bin/sh /opt/CA/siteminder/adminui/jboss-as/bin/run.sh

3. Restart the CA SiteMinder Policy Server or CSP console.

Reset the Audit Logs

Perform the following steps for SiteMinder Policy Server. These steps are not necessary for the CSP console.

1. From the server console, navigate to /opt/CA/siteminder/bin.
2. Start the smsconsole, and select the Data tab.
3. Select Audit logs from the label Database.
4. Select ODBC from the menu against the label Storage.
5. Select the checkbox Use Policy Store Database and click Apply.