Configuration Guides › Directory Configuration Guide › Oracle Internet Directory Server 10g 9.0.4 › Upgrade the 5.5 Policy Store

Upgrade the 5.5 Policy Store

You can upgrade an existing 5.5 policy store by creating and importing an LDIF file containing r12.1 schema.

Note: Use this procedure to upgrade a 5.5 policy store to a r12.1 policy store only.

To upgrade an existing 5.5 policy store

1. Point the Policy Server at the Oracle Internet Directory configured earlier by using the Data tab on the Policy Server Management Console.

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

2. Navigate to policy_server_home/bin on the system where the Policy Server is installed.
   • policy_server_home

     Specifies the Policy Server installation path.

3. Run the following command:

   smldapsetup ldgen -ffile_name.ldif -u -v
   

   • -f

     Specifies the name of the schema file that you are creating.

   • -u

     Specifies the creation of a schema file for an upgrade.

   • -v

     Turns on tracing and outputs error, warning, and comment messages.

4. Run the following command using the same values as you used when creating the upgrade schema file, but without the "-u" option:

   smldapsetup ldmod -ffile_name.ldif -v
   

   • -f

     Specifies the name of the schema file that you created.

5. Run the following command:

   ldapmodify -hhost -pport -dAdminDN -wAdminPW
   -c -fdir_config_home/xps/oid_10g/OID_10g.ldif
   -Z -Pcert 
   

   • -h host

     Specifies the IP address of the LDAP directory server.

     Example: 123.123.12.12

   • -p port

     Specifies the port number of the LDAP directory server.

     Example: 3500

   • -d AdminDN

     Specifies the name of the LDAP user who has the privileges needed to create a new LDAP schema in the LDAP directory server.

   • -w AdminPW

     Specifies the password of the administrator specified by the -d option.

   • -c

     Specifies continuous mode (do not stop on errors).

   • -f

     Specifies the path and file name of the XPS schema file provided with r12.1.

   • dir_config_home

     Specifies the Directory Configuration installation path.

   • -Z

     Specifies an SSL-encrypted connection.

   • -P cert

     Specifies the path of the directory where the SSL client certificate database file (cert7.db) exists.

     Example:

     If cert7.db exists in app/siteminder/ssl, specify:

     -Papp/siteminder/ssl.
     

   The policy store schema is extended to include the objects introduced by r12.1.

6. Run the following command:

   smobjimport
   -ipolicy_server_home\db\smdif\sm_upgrade_55_to_r12sp1.smdif -f -v
   

   • -i

     Specifies the path and name of the import file.

   • -f

     Overwrites duplicate SiteMinder objects.

   • -v

     Turns on tracing and outputs error, warning, and comment messages.

   The base policy store data is imported from the file sm_upgrade_55_to_r12sp1.smdif.

7. Run the following command:

   Important! Do not re-import ampolicy.smdif if it has been previously imported into the policy store.

   smobjimport -ipolicy_server_home\db\smdif\ampolicy.smdif
   -dsiteminder_super_user_name -wsiteminder_super_user_password -f -v -l -c
   

   • -i

     Specifies the path and name of the import file.

   • -dsiteminder_super_user_name

     Specifies the name of the SOA Security Manager administrator account.

   • -wsiteminder_super_user_password

     Specifies the password for the SOA Security Manager administrator account.

   • -f

     Overrides duplicate objects.

   • -v

     Turns on tracing and outputs error, warning, and comment messages in verbose format so that you can monitor the status of the import.

     Default value: stdout

   • -l

     Creates a log file.

   • -c

     Indicates that the smdif input file contains unencrypted data.

   Note: Importing ampolicy.smdif makes available Federation Security Services, Web Service Variables, and eTelligent Rules functionality that is separately licensed from SOA Security Manager. If you intend on using the latter functionality, contact your CA account representative for more information on licensing.

Note: You can now import the policy store data definitions.