Upgrade product to the current version.
Upgrade Methods
You can perform one of the following upgrades:
In-place Upgrade
An in-place upgrade lets you upgrade individual components in-place until your environment is operating at the latest release. Upgrading individual components consists of one or more steps:
  • Take a component offline.
  • Upgrade the component.
  • Bring the component online.
Upgrade individual components over an extended period to maintain system availability. The order in which you upgrade the components is the key to maintain system availability. During a migration, specific components that have been upgraded can continue to communicate with prior versions. This type of communication is known as mixed-mode support.
The step-by-step details are described in Migration Upgrade from r6.x and Migration Upgrade from r12.x.
Parallel Upgrade
A parallel upgrade involves setting up a new environment at the current product version next to an existing environment. A parallel upgrade is an alternative to an in-place upgrade and it eliminates upgrades of existing components.
 Configuring a parallel upgrade consists of the following general steps:
  • Leave the existing environment unchanged.
  • Configure a new environment.
  • Use a common key store or multiple key stores to enable single sign-on between both environments.
The step-by-step details are described in Parallel Upgrade from r6.x and Parallel Upgrade from r12.x.
Upgrade Process
The following diagram describes the upgrade process:
How to Upgrade to 12.52 SP1
How to Upgrade to 12.52 SP1
Perform the following steps to upgrade your environment:
  1. Determine the upgrade path.
  2. Perform in-place upgrade or parallel upgrade of the components.
  3. (Optional) Migrate your environment to use FIPS-compliant algorithms.
  4. (For 12.5 or 12.51) Upgrade the audit scheme to use enhanced auditing.
  5. Upgrade your web agents or 
    CA Access Gateway
  6. Upgrade SOA Manager.
Upgrade Simple Test Environments
If your test environment does not require single sign-on or failover, the most efficient way to upgrade is to:
  1. Install an 12.52 SP1 Policy Server.
    Install a new Policy Server. Do not upgrade the existing Policy Server. 
  2. Do one of the following:
    • If you are upgrading from r6.x, use smobjexport to export data from the r6.x policy store.
    • If you are upgrading from r12.x, use XPSExport to export data from the r12.x policy store.
  3. Do one of the following:
    • If you are upgrading from r6.x, use smobjimport to import the r6.x policy store data into the 12.52 SP1 policy store.
    • If you are upgrading from r12.x, use XPSImport to import the r12.x policy store data into the 12.52 SP1 policy store.
  4. Uninstall r6.x or r12.x.
When moving policies from one environment to another, as part of an upgrade or a policy migration, some objects that are environment-specific are in the export file. Examples of these objects include:
  • Trusted hosts
  • HCO Policy Server settings
  • Authentication scheme URLs
  • Password services redirects
  • Redirect responses
Depending on the mode you select when using XPSExport, these objects can get added to the new environment or can overwrite existing settings. Be sure that you do not adversely affect environment settings when importing the objects.