Previous Topic: Migration ConsiderationsNext Topic: How to Migrate from r12.1 SP3


How the r12.1 SP3 Migration Works

To migrate a CA SOA Security Manager deployment with multiple Policy Servers and SOA Agents, remove one of the Policy Servers and SOA Agents from the CA SOA Security Manager environment. While these components are being upgraded, the remaining Policy Servers and SOA Agents continue to protect your resources.

Continue removing and upgrading CA SiteMinder® components until all components are upgraded or operating in mixed–mode compatibility.

The following figures illustrate a simple r12.1 SP3 environment and detail the order in which existing components are upgraded.

Note: Each figure depicts a single policy/key store. Your environment can use separate policy and key stores.

Diagram showing an overview of the first three migration stages

  1. In stage one, an r12.1 SP3 Policy Server is upgraded. The 12.52 Policy Server operates in compatibility mode. Consider the following items:
  2. In stage two, an r12.1 SP3 SOA Agent is upgraded to 12.52.
  3. In stage three, the remaining Policy Server is upgraded to 12.52. The 12.52 Policy Servers operate in compatibility mode with the r12.1 SP3 policy and key store.

    Graphic showing the last two stages of a 12.51 upgrade process

  4. In stage four, the r12.1 SP3 policy and key store is upgraded to 12.52.
  5. In stage five, the Administrative UI is upgraded.