Installation and Upgrade Guides › Policy Server Installation Guide › Prerequisites for Running Reports Using Crystal Reports › Next Steps › Configure a Database to Store Audit Logs

Configure a Database to Store Audit Logs

Before configuring an Oracle or SQL Server database to store audit logs, ensure you have created the database for schema logging and configured an ODBC logs data source.

Details on creating a database for schema logging exist in:

• Create the Oracle Database Schema For Logging
• Create the SQL Server Database Schema For Logging

Details on configuring an ODBC logs data source exist in

• Configure an Oracle ODBC Logs Data Source
• Configure a SQL Server ODBC Logs Data Source

To point the Policy Server to store audit logs in a database

1. In the Policy Server Management Console, click the Data tab to move it to the front.

   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. In the Database drop-down list, select Audit Logs.
3. In the Storage drop-down list, select ODBC.
4. (If necessary) Clear the Use Policy Store database check box and click Apply.

   The fields in the Data Source Information group box become active.

5. In the Data Source Information field, enter the name of the data source, which should be SiteMinder Logs Data Source.

   Note: This name must correspond to the SiteMinder Logs Data Source name you entered in the Data Source Name field when you configured your ODBC logs data source.

6. In the User Name and Password fields, enter the user name and password of the user who administers the Policy Server’s logging database.
7. In the Confirm Password field, re-enter the password.
8. Specify the maximum number of database connections allocated to SiteMinder. For best performance, retain the default of 5 connections.
9. Click Test Connection to verify connectivity to the database server.
10. Click Apply to save the settings.