Configuration Guides › Directory Configuration Guide › OpenWave Directory Server 6.0.1 › Configure an OpenWave Directory Server as a Policy Store

Configure an OpenWave Directory Server as a Policy Store

You can configure an OpenWave directory server as a policy store by following the steps in this procedure:

1. Point the Policy Server to the OpenWave directory server.
2. Initialize the OpenWave directory server.
3. Create the policy store schema for r12.1.
4. Change the SiteMinder Super User password.
5. Import the base policy store data.

To configure an OpenWave Directory Server as a policy store

1. Point the Policy Server to the OpenWave directory by doing the following:
   1. In the Database drop-down menu, select Policy Store.
   2. In the Storage drop-down menu, select LDAP.
   3. In the LDAP policy store group box, configure the fields for an LDAP policy store.

      Sample values:

      • LDAP IP Address: 123.123.12.12:3500
      • Root DN: o=nete,c=us
      • Admin Username: cn=root
      • Password: masked_password

      Note: Refer to the Policy Server Administration Guide for a complete description of the LDAP settings.

   4. Click Apply.
   5. Click the Test LDAP Connection button.

   If the connection is successful, SiteMinder returns a confirmation. If it is not successful, SiteMinder returns an error message. If you receive an error message, verify that the values you entered are correct and that the OpenWave directory is running.

2. Copy the supplied file schema.txt from dir_config_home\openwave to policy_server_home\bin.
   • dir_config_home

     Specifies the Directory Configuration installation path.

   • policy_server_home

     Specifies the Policy Server installation path.

3. Navigate to policy_server_home\bin, and run the following command:

   smldapsetup ldmod -fschema.txt
   

   • -f

     Specifies the name of the schema file that is supplied with r12.1.

4. On the machine where the OpenWave directory server is installed, log in to the primary master directory server as the directory user.
5. For the supplied file dir_config_home\openwave\index.sql:
   1. Edit the file by changing the path for the tablespace creation.
   2. Place the file in the home directory.
6. Execute the following command:

   sqlplus /nolog
   

7. At the sql prompt, run the following commands:

   conn directory_user_name/directory_user_password
   @index.sql
   

8. Execute the following OpenWave command:

   imconfedit
   

9. Do the following:
   1. Find the configuration key /*/common/tableMapping.
   2. At the end of this key, add the contents of the supplied file:

      dir_config_home\openwave\tablemap.txt

10. Save the file and restart the directory server.
11. To check whether the server has started properly, execute the following command:

    imservping imdirserv
    

12. Run the following command:

    smldapsetup ldmod -fdir_config_home\xps\openwave\OpenWave.ldif
    

    • -f

      Specifies the path and name of the XPS schema file that is supplied with r12.1.

    • dir_config_home

      Specifies the Directory Configuration installation path.

    The policy store schema is created for r12.1.

13. On the Policy Server machine, change the SiteMinder Super User password by completing the following steps:
    1. Copy smreg from either \win32\tools or solaris/tools on the SiteMinder CD-ROM to policy_server_home\bin.
    2. Execute the following command:

       smreg -su superuserpassword
       

       superuserpassword

       Specifies the password for the SiteMinder Super User account.

       Note: Ensure there is a space between -su and the password.

    3. Delete smreg.exe.

       Note: Deleting smreg.exe prevents someone from changing the Super User password without knowing the previous password.

14. From policy_server_home/bin, import the basic SiteMinder objects required to set up a policy store by running:

    smobjimport -ipolicy_server_home\db\smdif\smpolicy.smdif
    -dsuperusername -wsuperuserpassword -v
    

    The base policy store data is imported.

    • superusername

      Specifies the Super User name of the SiteMinder administrator.

    • superuserpassword

      Specifies the password for the SiteMinder Super User.

    Note: If an argument contains spaces, use double quotes around the entire argument.

    Example:

    • Windows Systems

      smobjimport
      -i"C:\Program Files\Netegrity\siteminder\db\smdif\smpolicy.smdif" -d"SM Admin" -wPassword -v
      

    • UNIX Systems

      smobjimport
      -i$NETE_PS_ROOT/db/smdif/smpolicy.smdif -d"SM Admin" -wPassword -v
      

15. Run the following command:

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

    • -dsiteminder_super_user_name

      Specifies the name of the SOA Security Manager Super User account.

    • -wsiteminder_super_user_password

      Specifies the password for the SOA Security Manager 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 CA SiteMinder 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.

    The policy store is configured, and you can now log into the Policy Server User Interface.

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