Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data Stores 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.

By default, the key store is collocated with the policy store. You can configure a separate key store.

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

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

• Microsoft SQL Server
• Oracle RDBMS

If you do not use the Policy Server installer to configure a policy store automatically, you can manually configure a policy store after installing the Policy Server. Additionally, after you install the Policy Server, you can use the Policy Server Management Console to point the Policy Server to an existing policy store.

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

In addition to policy store support, you can use a relational database to store SOA Security Manager keys, audit logs, and session data.

More information:

Locate the SOA Security Manager Platform Support Matrix