Web Services Security Guides › CA SiteMinder WSS Upgrade Guide › Upgrading from CA SOA Security Manager r12.1 SP3 › How the SOA Security Manager r12.1 SP3 Migration Works

How the SOA Security Manager 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.

1. In stage one, an r12.1 SP3 Policy Server is upgraded. The 12.51 Policy Server operates in compatibility mode. Consider the following items:
   • The r12.1 SP3 SOA Agents continue to communicate with the 12.51 Policy Server.
   • The 12.51 Policy Server continues to communicate with the r12.1 SP3 policy and key store.
   • The r12.1 SP3 Policy Server continues to communicate with the r12.1 SP3 policy and key store.
   • If an r12.1 SP3 Administrative UI is configured with the 12.51 Policy Server, the Administrative UI continues to communicate with the Policy Server to manage objects in the r12.1 SP3 policy store.
2. In stage two, an r12.1 SP3 SOA Agent is upgraded to 12.51.
   • The r12.1 SP3 SOA Agent continues to communicate with the r12.1 SP3 and the 12.51 Policy Server.
   • The 12.51 Web Agent only communicates with the 12.51 Policy Server.

     Note: You cannot configure a new 12.51 agent with a 12.51 Policy Server until the policy store is upgraded to 12.51.

3. In stage three, the remaining Policy Server is upgraded to 12.51. The 12.51 Policy Servers operate in compatibility mode with the r12.1 SP3 policy and key store.

   

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