Repeat these steps to upgrade each SiteMinder Policy Server and the CSP console. These steps identical if you are upgrading a Disaster Recovery site.
Follow these steps:
/opt/CA/saas/repo/application/
If this directory has an upgradeBackupList.sh file, it includes a BACKUP_LIST environment variable. 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.
cd / unzip -o CAM-SMPS_kit-version.zip
jboss-eap-5.1.2.zip
diff /serverkit/properties.sh /tmp/properties.sh
JAVA64_KIT=/root/jdk-7u40-linux-x64.tar.gz; export JAVA64_KIT JAVA32_KIT=/root/jdk-7u40-linux-i586.tar.gz; export JAVA32_KIT _jce_zip_file=/root/UnlimitedJCEPolicyJDK7.zip; export _jce_zip_file
JBOSS_EAP_PATCH="/root/JBPAPP-8693.zip"; export JBOSS_EAP_PATCH
JBOSS_KIT="/root/jboss-eap-5.1.2.zip"; export JBOSS_KIT
For a high-availability deployment, do not include the host name on which you are currently installing. Enter the host name where you installed the first SiteMinder Policy Server.
Note: If you have three or more instances of SiteMinder Policy Server, separate the entries with commas. For example: PolicyServer2, PolicyServer3.
If you configured load balancing for the Policy Server at the application tier, set _ps_ha_hosts to the Policy Server load balancer VIP.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|