Installation and Upgrade Guides › SiteMinder Upgrade Guide › Upgrading from r6.x › How the r6.x Migration Works

How the r6.x Migration Works

To upgrade a SiteMinder deployment with multiple Policy Servers and Web Agents, remove one of the Policy Servers and Web Agents from the SiteMinder environment. While these components are being upgraded, the remaining Policy Servers and Web Agents continue to protect your resources. Continue removing and upgrading SiteMinder components until all components are upgraded or operating in mixed-mode compatibility.

The following figures illustrate a simple r6.x environment and detail:

• The order in which existing components are upgraded
• The order in which new components are installed

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

  

1. In stage one, an r6.x Policy Server is upgraded to r12.0 SP3. The r12.0 SP3 Policy Server operates in compatibility mode. Consider the following:
   • The r6.x Web Agents continue to communicate with the r12.0 SP3 Policy Server.
   • The r12.0 SP3 Policy Server continues to communicate with the r6.x policy and key store.
   • The r6.x Policy Server continues to communicate with the 6.x policy and key store. You can continue to use the r6.x Policy Server User Interface to administer the r6.x policy store through the r6.x Policy Server.

   Important! The Policy Server installer replaces the r6.x Policy Server User Interface with the FSS Administrative UI during the upgrade. The r12.0 SP3 Policy Server continues to provide access control and generates log files that contain auditing information. However, you cannot administer the r6.x policy store through r12.0 SP3 Policy Server until the Administrative UI is installed.

2. In stage two, an r6.x Web Agent is upgraded to r12.0 SP3. Consider the following:
   • The r6.x Web Agent continues to communicate with the r6.x and the r12.0 SP3 Policy Servers.
   • The r12.0 SP3 Web Agent only communicates with the r12.0 SP3 Policy Server.
3. In stage three, the remaining Policy Server is upgraded to r12.0 SP3. The r12.0 SP3 Policy Servers operate in compatibility mode with the r6.x policy and key store.

   Important! Although the Policy Servers continue to protect resources and you have access to the Policy Server Management Console, you cannot administer the Policy Servers. The Policy Server installer replaced the Policy Server User Interface with the FSS Administrative UI during the upgrade. You cannot record policy information in the policy store until you have installed the r12.0 SP3 Administrative UI. Account for this time as you plan your migration.

   

4. In stage four, the r6.x policy and key store is upgraded to r12.0 SP3.
5. In stage five, the Administrative UI is installed and registered with a Policy Server. Consider the following:
   • You can install the Administrative UI before upgrading the policy store. However, you cannot register the Administrative UI until the policy store is upgraded. Installing the Administrative UI before the policy store upgrade minimizes the amount of time the Administrative UI is unavailable to the policy store.
   • An r6.x Web Agent is illustrated as an example of mixed-mode compatibility.
6. (Optional) The final steps, which are not illustrated, include the following:
   • Register each FSS Administrative UI with the respective Policy Server. The FSS Administrative UI is registered using the Administrative UI.
   • Install and register a Report Server.

     Note: For more information about registering a FSS Administrative UI and installing the Report Server, see the Policy Server Installation Guide.