Installation and Upgrade Guides › SiteMinder Upgrade Guide › Planning an Upgrade

Planning an Upgrade

Component Versions in this Guide

This guide details the paths for upgrading a CA SiteMinder® environment to 12.52. An upgrade to 12.52 is supported from the following versions:

• r6.0 SP5 CR32
• r6.0 SP5 J
• r12.0 SP2
• r12.0 SP3
• r12.0 SP3 J
• r12.5

The component versions in this guide include:

• CA SiteMinder® Administrative UI upgrades from r12.x. In this guide:
  • r12.x is r12.0 SP2, r12.0 SP3, and r12.5
• Policy Server and policy store upgrades from r6.x and r12.x. In this guide:
  • r6.x is r6.0 SP5.
  • r12.x is r12.0 SP2, r12.0 SP3, and r12.5
• CA Business Intelligence Common Reporting component (Report Server) upgrades from r12.x. In this guide:
  • r12.x is r12 SP2 and r12.0 SP3 up to and including cr3.

    Note: If you installed and configured an r12.0 SP3 cr4 or higher Report Server, an upgrade is not required.

• Web Agent upgrades from r6.x and r12.x. In this guide:
  • r6.x is r6.x QMR 5.
  • r12.x is r12.0 SP2, r12.0 SP3, and r12.5.

Upgrade Paths

An upgrade consists of deploying 12.52 components to an existing CA SiteMinder® environment. Upgrading to 12.52 can be accomplished in two ways:

• Completing a migration.
• Configuring a parallel 12.52 environment next to an existing environment. Both environments use one or more key stores to maintain single sign–on.

Migration

A migration is the process of upgrading individual CA SiteMinder® components until your environment is operating at 12.52. Upgrading individual components consists of one or more steps during which you:

• Take a component offline.
• Upgrade the component.
• Bring the component online.

You upgrade individual components over an extended period to maintain system availability. A key to maintaining system availability is the order in which you upgrade components. 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 following diagram illustrates the concept of a migration. For more information about migrating from r6.x or r12.x, see the respective chapter:

Parallel Upgrade

A parallel upgrade is the process of configuring an 12.52 environment next to an existing environment. Configuring a parallel upgrade consists of multiple steps during which you:

• Leave the existing environment unchanged.
• Configure an 12.52 environment.
• Use a common key store or multiple key stores to enable single sign–on between both environments.

The following diagram illustrates the concept of a parallel upgrade. For more information about completing a parallel upgrade from r6.x or r12.x, see the respective chapter.