Previous Topic: Upgrade to CA SiteMinder® Federation Standalone 12.52 on WindowsNext Topic: Migrate to CA SiteMinder® Federation Standalone 12.52


Upgrade to CA SiteMinder® Federation Standalone 12.52 on UNIX

On a UNIX system, you can upgrade directly to CA SiteMinder® Federation Standalone 12.52 on the same operating platform and the same database.

If you are running your existing system on an operating system that is not supported in 12.52, migrate the configuration; you cannot directly upgrade.

Run the 12.52 CA SiteMinder® Federation Standalone installer. The upgrade preserves your previous configuration.

If the installer detects the smkeydatabase file, the installer performs the following actions:

Important! If the smkeydatabase migration fails, do not return system back to the original environment because this action causes all transactions that require the certificate data to fail.

These instructions are for GUI and Console Mode installations on UNIX systems. The steps for the two modes are the same, with the following exceptions for Console Mode:

Important! Be aware of the following installation restrictions:

Run the 12.52 CA SiteMinder® Federation Standalone installer to upgrade CA SiteMinder® Federation Standalone. Select the installer for your platform.

To locate installation kits on the Support site

  1. Log onto the CA Technical Support site.
  2. Click Download Center.
  3. Search the Download Center for the installation kit you need.

To upgrade CA SiteMinder® Federation Standalone

Important! Do not run the upgrade as the root user. If you try to install as root, the installation aborts and you receive an error message. Instead, create a new user account to install CA SiteMinder® Federation Standalone.

  1. Exit all applications that are running.

    Note: You do not need to deactivate your partnerships before upgrading.

  2. If necessary, add executable permissions to the installation file by running the chmod command, for example:

    chmod +x ca-fed-executable-sol.bin

  3. Navigate to the folder where you plan to run the installation program.
  4. Copy the installation binary to the folder.
  5. Enter one of the following commands in a command window:

    Example (GUI mode): ./ca-fed-executable-sol.bin

    The installation wizard starts.

  6. Go through the installation.
  7. Review the installation settings and click Install (GUI mode) or enter Y to install (Console mode).

    The CA SiteMinder® Federation Standalone installation program runs and then restarts the services.

  8. Rename the AssertionGeneratorFramework.properties file so that the system uses the new file created by the upgrade.
    1. Navigate to federation_install_dir\siteminder\config\properties.
    2. Rename the existing AssertionGeneratorFramework.properties file to preserve it, such as AssertionGeneratorFramework.properties.old.
    3. Remove the .new extension from the AssertionGeneratorFramework.properties.new file, which the upgrade creates.
  9. After the upgrade is complete, clear all temporary files in the browser so that the correct CA SiteMinder® Federation Standalone files load.

Note: If you upgrade from an environment with the CA SiteMinder® Connector is enabled, partnerships that use the Connector continue to work without requiring any changes. You can enable or disable the Connector on a per-partnership basis after the upgrade is complete. If the Connector was not enabled before an upgrade, enable and configure it for use with a given partnership.

Actions to Take if an Upgrade Error Occurs

In case of database upgrade failure, CA SiteMinder® Federation Standalone displays an error message that instructs you to run the policy_store_upgrade script. The upgrade script (policy_store_upgrade.sh) is located in federation_install_dir/install_config_info.

If you experience other problems during the installation, review the installation log file CA_Federation_Standalone_Install_date_time.log and the upgrade log file CA_Federation_policy_store_upgrade.log. Both files are the directory federation_install_dir/install_config_info.

Important! If the smkeydatabase migration fails, do not return system back to the original environment because this action causes all transactions that require the certificate data to fail.