Installation and Upgrade Guides › SiteMinder Upgrade Guide › Upgrading from SiteMinder r6.x › How to Migrate from r6.x › Upgrade an r6.x Policy Store

Upgrade an r6.x Policy Store

Upgrading the policy and key store is the third step in the migration process. The following sections detail how to upgrade an r6.x policy and key store to r12.5.

Options for Upgrading a Policy Store

Two paths exist for upgrading an r6.x policy store to r12.5. You can:

• Upgrade the existing policy and key store to r12.5.
• Create an r12.5 policy and key store and import the existing policy and key store data into the new instance.

This guide details the steps for upgrading an existing policy and key store.

If you want to migrate an existing policy store to a r12.5 policy and key store, follow these steps:

1. Export the policy and key store data using the r6.x version of smobjexport.

   Note: For more information, see the Policy Server Installation Guide for r6.x.

2. Create an r12.5 policy and key store.

   Note: For more information, see the Policy Server Installation Guide.

3. Import the policy and key store data into the r12.5 policy and key store using the r12.5 version of smobjimport.

   Note: For more information, see the Policy Server Administration Guide.

Options for Upgrading a Key Store

Two paths exist for upgrading an r6.x key store to r12.5. You can:

• Upgrade the existing policy and key store to r12.5.
• Create a stand–alone r12.5 key store and import the existing agent keys in to the new instance.

This guide details the steps for upgrading an existing policy and key store.

If you want to create a stand–alone r12.5 key store:

1. Use the r6.x version of smobjexport to export only the agent keys that are stored in the policy store.

   Note: For more information, see the r6.x Policy Server Installation Guide.

2. Create an r12.5 key store using the default policy store schema.

   Note: For more information, see the Policy Server Installation Guide.

3. Use the r12.5 version of smobjimport to import the agent keys in to the r12.5 key store.

   Note: For more information, see the Policy Server Administration Guide.

4. Use the Policy Server Management Console to point the Policy Server to the stand–alone key store.

   Note: For more information, see the Policy Server Management Console Help.

How to Upgrade an r6.x Policy Store

To upgrade an r6.x policy store to r12.5, complete the following procedures:

1. Stop all Policy Servers that are communicating with the policy store.
2. If you have not extended the policy store schema to facilitate a smkeydatabase migration during a Policy Server upgrade, extend the schema.
3. Import the policy store data definitions.
4. Import the default policy store objects.

   Note: If you are upgrading a legacy federation environment, there is no change to the Policy Server Option Pack (PSOP) schema.

5. If you managed your r6.x legacy federation environment using the FSS Administrative UI, run the XPS sweeper utility to complete the migration of your legacy federation objects.
6. Start all Policy Servers that are communicating with the policy store.

Stop all Policy Severs

Stopping all of the Policy Servers that are communicating with the policy store helps to prevent policy store corruption during the upgrade.

Follow these steps:

1. Log in to the Policy Server host system.
2. Complete one of the following steps:
   • (Windows)
     1. Open the Policy Server Management Console and click Stop.
     2. Click OK to close the console.
   • (UNIX) Use the following supplied script:

     install_path/siteminder/stop-all
     

     install_path

     Specifies the Policy Server installation path.

3. Repeat this procedure for each Policy Server that is communicating with the policy store.