Installation Guides › Upgrade Guide › Upgrading from r12 › How to Migrate from r12.0 › Upgrade an r12.0 Policy Server › Upgrade an r12.0 Policy Server on UNIX

Upgrade an r12.0 Policy Server on UNIX

You run the respective UNIX Policy Server installation executable to upgrade the Policy Server. The installation executables are in the SOA Security Manager kit available on the Technical Support site. They are the following:

• Solaris—ca-soasm-12.1-cr001-sol.bin
• Red Hat Linux—ca-soasm-12.1-cr001-linux.bin

To locate installation kits on the Support site

1. Click Technical Support.
2. Log into CA Support Online.
3. Click Download Center.
4. Search the Download Center for the installation kit you need.

Note: Extract all files and directories in the SOA Security Manager kit to a common location on a local drive and keep them together—the SOA Security Manager installer cannot run without the included supporting files.

If you do not have sufficient rights, add executable permission to the install file by running the following command:

chmod+x ca-soasm-12.1-cr001-os_version.bin

• os_version

  Specifies sol or linux.

Important! If you execute the SOA Security Manager installer across different subnets it can crash. To avoid this problem, install the Policy Server directly on the host system.

To locate installation kits on the Support site

1. Click Technical Support.
2. Log into CA Support Online.
3. Click Download Center.
4. Search the Download Center for the installation kit you need.

To upgrade the Policy Server

1. Exit all applications that are running.
2. Execute the following script in a ksh shell from the soa_home/siteminder directory:

   ../ca_ps_env.ksh
   

   Note: Ensure that there is a space between the periods (. .) when running the script.

   • soa_home

     Specifies the path to where the SOA Security Manager is installed.

3. Open a command window and navigate to where the install program is located.
4. Enter the following command:
5. Enter the following command in a UNIX shell:

   sh ./ca-soasm-12.1-cr001-os_version.bin
   

   Example: sh ./ca-soasm-12.1-cr001-sol.bin

   The SOA Security Manager installation wizard starts.

6. Consider the following when running the installer:
   • When prompted to select features to install, select CA SOA Security Manager Policy Server.
   • When prompted to select the components you want configured:
     • You must reconfigure components that had been previously configured for the environment. Ensure the respective check boxes are selected.
     • If you plan on using WS-Security SAML tokens, ensure that the Create SM Key Database/Change SM Key Database Password option is selected.
     • If you do not intend on configuring a new policy store, clear the Policy Store check box. You do not have to reconfigure existing policy store settings. The upgraded Policy Server retains the policy store settings. You manually upgrade an existing policy store.
   • If you selected the Create SM Key Database/Change SM Key Database Password check box:
     • Create a r12.1 smkeydatabase if you intend on migrating your existing smkeydatabase data into this repository.
     • Change the password if you intend on upgrading an existing smkeydatabase. Changing the password re-encrypts the database password and existing encrypted data using FIPS-compliant algorithms.
   • If you cut and paste path information into the wizard, you must also enter a character before the Next button is enabled.
7. Review the installation settings and click Install.

   The Policy Server and any selected components are installed and configured.

   Note: This may take several minutes.

8. Click Done and reboot the system.

   The Policy Server is upgraded.

   Note: The FSS Administrative UI is installed during the Policy Server upgrade. The FSS Administrative UI is for managing CA SiteMinder Federation Security Services and is required only if using WS-Security SAML tokens. If you need it, register the FSS Administrative UI with the Policy Sever after upgrading the policy store. More information on registering the FSS Administrative UI exists the in Policy Server Installation Guide.

If you experience problems during an installation or upgrade, you can locate the CA_SOA_Security_Manager_r12.1_InstallLog.log file in soa_home/install_config_info/

You can also refer to the ca-ps-details.log file located in soa_home/siteminder/install_config_info to check the status of the installer's auto-configuration of an ADAM or Sun Java System Directory Server policy store.

• soa_home

Specifies the path to where SOA Security Manager is installed.