Previous Topic: UNIXNext Topic: How to Uninstall Reporting


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 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.

To register the audit database with the Administrative UI

  1. Log into 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.

    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:
  8. Enter the port on which the audit database server is listening in the Database Server Port field.
  9. Complete one of the following:
  10. Enter administrator credentials for the audit database in the respective fields.

    Note: The administrator credentials must match the credentials 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 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:

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

Note: For more information about supported database drivers, see the r12.0 SP3 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:
  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:
  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:
  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:
  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.