Installation and Upgrade Guides › Policy Server Installation Guide › Installing Reports › How to Configure an Audit Database

How to Configure an Audit Database

A CA SiteMinder® audit database is required to run CA SiteMinder® audit–based reports.

Note: Although you can write audit information to a text file, you must store your audit information in a supported ODBC database to create and manage audit-based reports. For a list of the supported versions, see the CA SiteMinder® 12.51 Platform Support Matrix.

Complete the following steps to configure an audit database:

1. (Optional) If you have not already done so, configure a CA SiteMinder® audit database.

   Important! If you are configuring the audit database in Oracle, be sure that the user account you supply does not have the DB role. If the user account has the DB role, audit–based reports do not return correct results.

2. Register the audit database with the Administrative UI.
3. Configure connectivity between the audit database and the Report Server.

More information:

Locate the Platform Support Matrix

Register the Audit Database with the Administrative UI

You register the audit database with the Administrative UI to create a trusted connection between the components. Registering the audit database with the Administrative UI lets CA SiteMinder® administrators create and manage audit-based reports.

Note: The Administrative UI can have a trusted relationship with one or more Policy Servers. However, each trusted relationship only allows one audit database connection. If you must connect to a new audit database, either delete the current connection or connect to another Policy Server to configure the connection.

Follow these steps:

1. Log in to the Administrative UI.
2. Click Administration, Admin UI.
3. Click Report Connections, Create Audit Report Connection.

   The Create Audit Report Connection pane appears.

   Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.

4. Select the database vendor from the Database Vendor drop-down list.

   The vendor-specific fields appear.

5. Type the name of the connection in the Connection Name field.
6. Enter the audit database host system name or IP address in the Database Server Host field.
7. Enter the audit database data source information in the DSN field:
   • Oracle—Enter the Oracle Net Service name you specified when creating the audit database DSN.

     Note: The service name must be associated with the DSN you entered in the Data Tab of the Policy Server Management Console when configuring the audit database connection to the Policy Server. The service name must match the DSN you create on the Report Server.

   • SQL Server—Enter the DSN.

     Note: The DSN name must match the DSN you specified in the Data Tab of the Policy Server Management Console when configuring the audit database connection to the Policy Server. The DSN name must also match the DSN you create on the Report Server.

8. Enter the port on which the audit database server is listening in the Database Server Port field.
9. Complete one of the following steps:
   • Oracle—Re–enter the Oracle Net Service Name in the Service Name field.
   • SQL Server—Enter the audit database name in the Database Name field.
10. Enter administrator credentials for the audit database in the respective fields.

    Note: The administrator credentials must match the credentials that you specified in the Data tab of the Policy Server Management Console when configuring the audit database connection to the Policy Server.

11. Click Submit.

    The audit database is registered with the Administrative UI.

Audit Database and Report Server Connectivity

A Report Server connects to a CA SiteMinder® audit database to create audit-based reports. When an audit-based report is scheduled in the Administrative UI, the Administrative UI passes the following connection information to the Report Server:

• (Oracle) The Oracle Net Service Name that identifies the audit database
• (Microsoft SQL Server) The name of the:
  • Audit database
  • Data source used to connect to audit database
• The user account credentials required to access the audit database

To configure connectivity between the audit database and the Report Server, do one of the following:

• (Oracle) Be sure that the:
  • Oracle Net client is installed to the Report Server host system.
  • Oracle Net Service Name that identifies the audit database is present in the tnsnames.ora file on the Report Server host system.
• (Microsoft SQL Server) Be sure that the data source used to connect to the audit database is present on the Report Server host system.

Note: For more information about supported database drivers, see the 12.51 CA SiteMinder® Platform Support Matrix.

More information:

Locate the Platform Support Matrix

Start the Report Server

(Windows) Follow these steps:

1. Click Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.

   The Central Configuration Manager console appears.

2. Start the Apache Tomcat and Server Intelligence Agent Services.

   The Report Server is started.

(UNIX) Follow these steps:

1. Log in to the system as the non–root user that installed the Report Server.
2. Be sure that at least one of the following environment variables is set to a valid utf8/UTF-8 locale:
   • LC_ALL
   • LANG
   • LC_CTYPE
3. Navigate to report_server_home/CommonReporting3/external/scripts and run the following script:

   ../setupenv.sh
   

   report_server_home

   Specifies the Report Server installation path.

4. Be sure that:
   • The IAM_RPTSRV_HOME variable is set to report_server_home/CommonReporting3.

     report_server_home

     Specifies the Report Server installation path.

   • (Oracle report database only) The LD_LIBRARY_PATH variable is set as follows:

     $ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
     

     Example:

     export LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
     

5. Navigate to report_server_home/CommonReporting3/bobje

   report_server_home

   Specifies the Report Server installation path.

6. Run the following command:

   ./startservers
   

7. Run the following command:

   ./tomcatstartup.sh
   

   The Report Server is started.

Stop the Report Server

(Windows) Follow these steps:

1. Click Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.

   The Central Configuration Manager console appears.

2. Stop the Apache Tomcat and Server Intelligence Agent Services.

   The Report Server is stopped.

(UNIX) Follow these steps:

1. Log in to the system as the non–root user that installed the Report Server.
2. Be sure that at least one of the following environment variables is set to a valid utf8/UTF-8 locale:
   • LC_ALL
   • LANG
   • LC_CTYPE
3. Navigate to report_server_home/CommonReporting3/external/scripts and run the following command:

   ../setupenv.sh
   

   report_server_home

   Specifies the Report Server installation path.

4. Be sure that:
   • The IAM_RPTSRV_HOME variable is set to report_server_home/CommonReporting3.

     report_server_home

     Specifies the Report Server installation path.

   • (Oracle report database only) The LD_LIBRARY_PATH variable is set as follows:

     $ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
     

     Example:

     export LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
     

5. Navigate to report_server_home/CommonReporting3/bobje.

   report_server_home

   Specifies the Report Server installation path.

6. Run the following command:

   ./stopservers
   

7. Run the following command:

   ./tomcatshutdown.sh
   

   The Report Server is stopped.