Installation Guides › Policy Server Installation Guide › Installing the Policy Server on UNIX Systems › How to Install the Policy Server › Policy Store Considerations

Policy Store Considerations

Consider the following before running the Policy Server installer or the Policy Server Configuration wizard:

• The Policy Server installer and the Policy Server Configuration wizard can automatically configure one of the following as a policy store:
  • Microsoft^® Active Directory^® in Application Mode (ADAM)
  • Microsoft Active Directory Lightweight Directory Services (AD LDS)

    Note: Be sure that you have met the prerequisites for configuring ADAM or AD LDS as a policy store.

  • Oracle^® Directory Server Enterprise Edition (formerly Sun Directory Server Enterprise Edition)
  • Microsoft SQL Server^® (SQL Server)
  • Oracle RDBMS

  Important! The Policy Server installer and the Policy Server Configuration wizard cannot automatically configure a policy store that is being connected to using an SSL connection.

• (RDB policy store) The Policy Server installer or the Policy Server Configuration Wizard use specific database information to create the policy store data source. The Policy Server uses this data source to communicate with the policy store. Consider the following:
  • The name of data source is CA SOA Security Manager DSN.
  • (Windows) The installer saves the data source to the Microsoft ODBC Data Source Administrator tool, under the System DSN tab.
  • (UNIX) The installer saves the data source to the system_odbc.ini file, which is located at siteminder_home/db.

    siteminder_home

    Specifies the Policy Server installation path.

• (RDB policy store) Be sure that the database server that is to host the policy store is configured to store objects in UTF–8 form. This configuration avoids possible policy store corruption.
  • (Oracle) Be sure that the database is configured to store objects in UTF–8 form. Oracle supports unicode within many of their character sets. For more information about configuring your database to store objects in UTF–8 form, see your vendor–specific documentation.
  • (SQL Server) Be sure that the database is configured using the default collation (SQL_Latin1_General_CP1_CI_AS). Using a collation that is case sensitive can result in unexpected behaviors. For more information about configuring your database to store objects using the default collation, see your vendor–specific documentation.
• You manually configure any other supported directory server or relational database as a policy store after installing the Policy Server. Configuring a policy store manually is detailed in this guide.

More information:

ADAM/AD LDS Prerequisites

Configuring LDAP Directory Servers as a Policy or Key Store

Configuring SOA Security Manager Data Stores in a Relational Database