Previous Topic: Upgrade an r6.x Policy StoreNext Topic: Install the Administrative User Interface for a r6.x Migration


Extend the Policy Store Schema

The existing r6.x policy store schema has not changed. The r12.5 migration requires that you extend the policy store schema for policy store for objects that r12.5 requires.

More information:

Extend the Policy Store Schema for Your Novell eDirectory Server

Extend the Policy Store Schema for Your Oracle Internet Directory Server

Extend the Policy Store Schema for Your OpenLDAP Server

Extend the Policy Store Schema for Your Siemens DirX Server

Extend the Policy Store Schema for Your Active Directory Server

Extend Policy Store Schema for Your Active Directory LDS Server

Extend Policy Store Schema for Your CA Directory Server

Extend the Policy Store Schema for Your IBM DB2 Server

Extend the Policy Store Schema for Your IBM Tivoli Directory Server

Extend the Policy Store Schema for Your Sun Java System Directory Server

Extend the Policy Store Schema for Your Microsoft SQL Server

Extend the Policy Store Schema for Your Oracle Server

Extend the Policy Store Schema for Your Red Hat Directory Server

Extend the Policy Store Schema for Your MySQL Server

Import the Policy Store Data Definitions

Importing the policy store data definitions defines the types of objects that can be created and stored in the policy store.

Follow these steps:

  1. Open a command window and navigate to siteminder_home\xps\dd.
    siteminder_home

    Specifies the Policy Server installation path.

  2. Run the following command:
    XPSDDInstall SmMaster.xdd
    
    XPSDDInstall

    Imports the required data definitions.

Import the Default Policy Store Objects

Importing the default policy store objects configures the policy store for use with the Administrative UI and the Policy Server.

The default policy store objects exist in the following XML files:

The smpolicy-secure.xml file provides more restrictive security settings than the smpolicy.xml file. Pick only one of the previous files to import the default policy store objects.

Either file configures a new policy store and upgrades an existing store. When imported as part of an upgrade, the file does not overwrite existing default objects that were modified. These objects include the default security settings in the default Agent Configuration Object (ACO) templates.

Importing either file makes legacy federation and Web Service Variables functionality available. These features are separately licensed. If you intend to use the Web Service Variables functionality, contact your CA account representative for licensing information.

Follow these steps:

  1. Open a command line window and navigate to siteminder_home\db.
  2. Import one of the following files:
    –npass

    Specifies that no passphrase is required. The default policy store objects do not contain encrypted data. No passphrase is required to import the default policy store objects.

    The policy store objects are imported.

Make the legacy federation Objects Available in the Administrative UI

If you manage your Federation Security Services (legacy federation) objects using the Policy Server UI, run the XPS sweeper utility to migrate these objects to the Administrative UI.

Follow these steps:

  1. Log in to the Policy Server host system.
  2. Run the following command to make your legacy federation objects available to the Administrative UI:
    XPSSweeper
    

    All legacy federation created using the Policy Server UI are available in the Administrative UI.

    You are ready to proceed to the next stage of the upgrade process, upgrading your Administrative UI.

Start all Policy Servers

Starting all Policy Servers resumes communication between all of the Policy Servers and the upgraded policy store.

Follow these steps:

  1. Log in to the Policy Server host system.
  2. Complete one of the following steps:
  3. Repeat this procedure for each Policy Server that is communicating with the policy store.

The policy store is upgraded.