Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data in a Relational Database › Relational Databases as a Policy or Key Store

Relational Databases as a Policy or Key Store

The SOA Security Manager policy store is the repository for all policy–related information. All Policy Servers in a SOA Security Manager installation must share the same policy store data, either directly or through replication. SOA Security Manager is installed with tools that let administrators move policy store data from one storage facility to another.

When you install the Policy Server, you can automatically configure one of the following directory servers as a policy store:

• Sun Java System Directory Server Enterprise Edition (formerly Sun ONE/iPlanet)
• Microsoft ADAM
• Microsoft AD LDS

You can configure the Policy Server to use another LDAP directory server, a SQL Server database, or an Oracle database as a policy store after you have completed the Policy Server installation. Also, after installation, you can use the Policy Server Management Console to point the Policy Server to another policy store.

You can use a supported database to store SOA Security Manager policy store data. SOA Security Manager keys, audit logs, and session data can be stored in the policy store or in a separate database.

Storing keys in a separate database may be required to implement single sign–on functionality.

Note: For a list of supported CA and third-party components, refer to the SOA Security Manager Platform Support Matrix on the Technical Support site.

To locate the support matrix from the Technical Support site

1. Click Support By Product.
2. Select CA SOA Security Manager from the Select a Product list.
3. Click CA SOA Security Manager Platform Support Matrices under Product Status.

You can download the latest JDK and JRE versions at the Sun Developer Network.