Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › Configure Policy, Key, Logging, or Session Stores › Configure a Database to Store Keys and Audit Logs

Configure a Database to Store Keys and Audit Logs

SiteMinder keys and audit logs can be stored in separate databases. Before configuring a separate database to store keys or audit logs, be sure that you have configured a separate database to function as the policy store.

Note: Storing keys in a separate database may be required to implement single sign–on functionality. For more information about key management, see the Policy Server Management Guide.

If you are working with a SQL Server database or an Oracle database, the following procedure assumes that you have imported sm_mssql_logs.sql or $NETE_PS_ROOT/db/sql/sm_oracle_logs.sql, respectively.

To configure SiteMinder to store keys or audit logs in different databases:

1. In the Policy Server Management Console, click the Data tab.

   Important! If you are accessing this graphical user interface on Windows Server 2008, open the shortcut with Administrator permissions, even if you are logged into the system as an Administrator. For more information, see the release notes for your SiteMinder component.

2. Select Key Store or Audit Logs from the Database list.
3. Clear the Use the policy store database check box and click Apply.

   The fields in the Data Source Information section become active.

4. In the Data Source Information field, enter the name of the data source.
   • (Windows) The name you enter must correspond to the name you entered in the Data Source field of the ODBC Driver Setup dialog.
   • (UNIX) The value you enter must match the first line of the data source entry in the system_odbc.ini file. This file is located in $NETE_PS_ROOT/db. Example: The first line of the default entry in the system_odbc.ini file is [SiteMinder Data Source], so you would enter SiteMinder Data Source in the Data Source Name field. If you modify the entry in the system_odbc.ini file, you would enter that value in the Data Source Information field.

     Note: When entering the data source name, do not include the brackets.

5. In the User Name and Password fields, enter the user name and password of the database account that has full access rights to the database.
6. In the Confirm Password field, re–enter the password.
7. Specify the maximum number of database connections allocated to SiteMinder. For best performance, retain the default of five connections.
8. Click Test Connection to verify connectivity to the database server.
9. Click Apply to save the settings.