Installation and Upgrade Guides › Directory Configuration Guide › Siemens DirX 6.0 D00 Directory Server › Configure a DirX 6.0 D00 Directory Server as a Policy Store

Configure a DirX 6.0 D00 Directory Server as a Policy Store

You can configure a Siemens DirX 6.0 D00 Directory Server as a SiteMinder r12.0 SP2 policy store on a Windows 2000 SP4 Advanced Server.

To configure a Siemens DirX 6.0 D00 Directory Server as a policy store

1. Install DirX 6.0 D00, and accept all of the defaults during installation.

   Note: If you do not have an existing database, install the sample database.

2. Copy the following files from dir_config_home\dirx to

   DirX_install_path\scripts\security\Netegrity\SiteMinder:

   • dirxabbr-ext.SiteMinderR12sp2
   • schema_ext_for_SiteMinderR12sp2.adm
   • subschema_ext_for_SiteMinderR12sp2.cp
   • bind.tcl
   • l-bind.cp
   • _setup.bat
   • setup.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

3. 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
4. Rename the following files:
   • schema_ext_for_SiteMinderR12sp2.adm to schema_ext_for_SiteMinder.adm
   • subschema_ext_for_SiteMinderR12sp2.cp to subschema_ext_for_SiteMinder.cp
5. Copy the following files to DirX_install_path\client\conf:
   • dirxabbr-ext.SiteMinderR12sp2
   • dirxabbr-ext.XPS
6. Rename dirxabbr-ext.SiteMinderR12sp2 to dirxabbr-ext.SiteMinder.
7. Stop and restart the DirX service.
8. 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
9. Run setup.bat, and check the resulting log file, setup.log, for errors.
10. Rebind to the DSA using the DirXmanage tool.

    Note: Watch for errors.

11. Create the base tree structure using the DirXmanage tool:
    1. Under o=PQR, create ou=Netegrity.
    2. Under ou=Netegrity, create ou=SiteMinder.
    3. Under ou=SiteMinder, create ou=PolicySvr4.

    The policy store schema is created for r12.0 SP2.

12. Navigate to policy_server_home\bin.
    • policy_server_home

      Specifies the Policy Server installation path.

13. Run the following command:

    $ smobjimport -ipolicy_server_home\db\smdif\smpolicy.smdif -v
    

    • -i

      Specifies the path and name of the import file.

    • -v

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

      Note: You can output to a log file and check for errors.

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

    Note: To import data from an existing policy store, see the section on migrating policy store data in the Policy Server Installation Guide.

14. Run the following command:

    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 SiteMinder Super User account.

    • -wsiteminder_super_user_password

      Specifies the password for the SiteMinder Super User 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 SiteMinder. If you intend on using the latter functionality, contact your CA account representative for more information on licensing.

15. Run the following command:

    smreg -su password
    

    The administrator's password is set.

16. Point the Policy Server to the DirX Directory Server by using the Data tab on the Policy Server Management Console.

    Sample values:

    • LDAP IP Address: 123.456.7.8
    • Root DN: o=pqr
    • Admin username: cn=admin,o=pqr
    • Admin password: ********

    The DirX Directory Server is configured as a policy store.

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