Configuration Guides › Directory Configuration Guide › Siemens DirX 6.0 D00 Directory Server › Upgrade a 5.5 Policy Store

Upgrade a 5.5 Policy Store

You can can upgrade a Siemens DirX 6.0 D00 Directory Server that is configured as a 5.5 policy store to a r12.1 policy store.

To upgrade a 5.5 policy store

1. Copy the following files from dir_config_home\dirx to

   DirX_install_path\scripts\security\Netegrity\SiteMinder:

   • dirxabbr-ext.SiteMinder55ToR12sp1
   • schema_ext_for_SiteMinder55ToR12sp1.adm
   • subschema_ext_for_SiteMinder55ToR12sp1.cp
   • bind.tcl
   • l-bind.cp
   • _setup-upgrade.bat
   • setup-upgrade.bat
   • GlobalVar.tcl
   • dir_config_home

     Specifies the Directory Configuration installation path.

   • DirX_install_path

     Specifies the DirX installation path.

     Example: C:\program files\siemens\dirx

   Note: Do not delete the following schema files already in the folder:

   • dirxabbr-ext.SiteMinder55
   • schema_ext_for_SiteMinder55.adm
   • subschema_ext_for_SiteMinder55.cp
2. Copy the following files from dir_config_home\xps\dirx to

   DirX_install_path\scripts\security\Netegrity\SiteMinder:

   • dirxabbr-ext.XPS
   • schema_ext_for_XPS.adm
   • subschema_ext_for_XPS.cp
3. Copy the following files to DirX_install_path\client\conf:
   • dirxabbr-ext.Siteminder55toR12sp1
   • dirxabbr-ext.XPS
4. Stop and restart the DirX service.
5. Edit GlobalVar.tcl to update the global variables that the DirX scripts reference.

   Default values:

   • LDAP port: 389
   • Root DN: o=pqr
   • Admin username: cn=admin,o=pqr
   • Admin password: dirx
6. Run setup-upgrade.bat, and check the resulting log file, setup-upgrade.log, for errors.
7. Rebind to the DSA using the DirXmanage tool.

   Note: Watch for errors.

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

8. Navigate to policy_server_home\bin.
   • policy_server_home

     Specifies the Policy Server installation path.

9. Run the following command:

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

   • -i

     Specifies the path and name of the import file.

   • -v

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

   • -f

     Overwrites duplicate SOA Security Manager objects.

   The base policy store data is imported from the file sm_upgrade_55_to_r12sp1.smdif, and the directory server is configured as a r12.1 policy store.

10. 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.

    smobjimport imports the policy store objects. These objects are automatically imported to the appropriate locations.

    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.

11. Point the Policy Server to the 5.5 policy store on which the schema was upgraded.

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