Policy Server Guides › Policy Server Administration Guide › Configuring Policy Server Data Storage Options › Configure a Separate Database for the Audit Logs

Configure a Separate Database for the Audit Logs

The audit log database is where the Policy Server stores audit logs containing event information. These settings may reduce Policy Server performance. If this is a problem, configure auditing data logs in a text file instead of database.

To configure a separate database for audit logs

1. Choose Audit Log from the Database drop-down list.
2. Choose an available storage type (ODBC or Text file) from the Storage drop-down list.
3. Specify Storage Options appropriate for the chosen storage type.
4. Click Apply to save your settings, or click OK to save the settings and exit the Console.

When deciding whether to store the Policy Server audit logs in an ODBC database or text file, you should consider the following factors:

• SiteMinder Reporting requires that the audit logs are written to an ODBC database. Reporting will not function if the audit logs are written to a text file.
• SiteMinder audit logging to an ODBC database and to a text file supports internationalization (I18N).
• If your Policy Server will operate under heavy load, you should consider logging to a text file rather than an ODBC database. However, if you do log to an ODBC database, you should set the following registry key values in the HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Database\ registry location to prevent loss of auditing data under heavy load:
  • ConnectionHangwaitTime

    Set to 60 seconds for heavy loads. The default is 30 seconds.

  • QueryTimeout

    Set to 30 seconds for heavy loads. The default is 15 seconds.

  • LoginTimeout

    Set to 30 seconds for heavy loads. The default is 15 seconds.

  Note: The value of ConnectionHangwaitTime should always be at least double the value of QueryTimeout and LoginTimeout.