Installation and Upgrade Guides › SiteMinder Upgrade Guide › Planning a CA SiteMinder® Upgrade › Upgrade Paths

Upgrade Paths

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

• Completing a migration.
• Configuring a parallel 12.52 SP1 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 SP1. 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 SP1 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 SP1 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.