Previous Topic: Download the SOA Security Manager Schema Files

Next Topic: Import the Policy Store Data Definitions

Configure a DirX EE 2.0 Directory Server as a r12.1 SP3 Policy Store

To configure a Siemens DirX EE 2.0 Directory Server as a r12.1 SP3 policy store

  1. Install DirX EE 2.0.
  2. Open the DirX EE Manager and create the following base tree structure to hold the policy store data:
    1. Under o=MyCompany, create ou=netegrity.
    2. Under ou=netegrity, create ou=Siteminder.
    3. Under ou=Siteminder, create ou=PolicySvr4.
    4. Under ou=PolicySvr4, create ou=XPS.
  3. Copy the following files from path\dirxee20

    to DirX_EE_install_path\scripts\stand_alone\extensions:

    path

    Specifies the path to the schema files extracted from the tier 2 directory zip.

    DirX_EE_install_path

    Specifies the DirX EE installation path.

  4. Copy the following files from path\xps\dirxee20 to DirX_EE_install_path\scripts\stand_alone\extensions:
  5. From the command prompt, change to the following directory:

    DirX_EE_install_path\scripts\stand_alone\extensions

  6. Run the following command:

    dirxmodify -f DirXEE20_SMR12sp3_Schema.ldif -D cn=admin,o=MyCompany -w dirx

    -f

    Specifies the name of the LDIF file.

    -D

    Specifies the bind DN.

    Example: cn=admin,o=MyCompany

    -w

    Specifies the password.

    Example: dirx

    -h

    (Optional) Specifies the host.

    Default: localhost

    -p

    (Optional) Specifies the port number.

    Default: 389

  7. Run the following command:

    dirxadm add_PS_Indexes.adm

  8. Run the following command:

    dirxmodify -f XPS_SchemaExt.ldif -D cn=admin,o=MyCompany -w dirx

  9. Run the following command:

    dirxadm add_XPS_Indexes.adm

    The XPS schema is created.

  10. Open the Policy Server Management Console, click the Data tab, and specify the following information in the fields on the tab:

    The Policy Server points to the DirX EE policy store.

  11. Run the following command:

    smreg –su password

    The SOA Security Manager administrator password is set.

  12. Run the following command:

    smobjimport –ipolicy_server_home\db\smdif\smpolicy.smdif –v

    -dsiteminder_super_user_name -wsiteminder_super_user_password

    policy_server_home

    Specifies the Policy Server installation path.

    -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 to the DirX EE policy store.

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

    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

You can now import the policy store data definitions.