Configuring an Audit Repository

Perform this procedure to configure an audit repository to store your auditing data collected by the Fusion Middleware Auditing Framework in database tables rather than a log file.

To set up the audit database in WebLogic Server:

  1. Create the audit schema using RCU.
  2. Create a data source in your WebLogic server.
  3. Register the audit database to your domain.

Creating the Audit Schema Using RCU

You use the Repository Creation Utility to create the audit schema.

To create the audit schema:
  1. Go to $RCU_HOME/bin and execute the rcu command.
  2. Choose Create at the starting screen and click Next.
  3. Enter your database details, and click Next.
  4. Choose the option to create a prefix, and enter a prefix; for example: BIP.
  5. Select Audit Services from the list of schemas.
  6. Click Next and accept the tablespace creation.
  7. Click Finish to start the process.

When the Repository Creation Utility process finishes, the following audit-related schemas are created in your database:

  • <prefix>_IAU (for example: BIP_IAU)

  • <prefix>_IAU_APPEND (for example: BIP_IAU_APPEND)

  • <prefix>_IAU_VIEWER (for example: BIP_IAU_VIEWER)

Creating the Data Source in WebLogic Server

After you create a database schema for your auditing data, next create a JDBC connection on your WebLogic Server so the Audit Framework can access the database schema that was created with the RCU in the previous step.

To create the JDBC connection:

  1. Connect to the Oracle WebLogic Server Administration console: http://hostname:port/console (e.g. http://example.com:7001/console).
  2. Under Services, click the Data Sources link, as shown below.
  3. Click Lock and Edit.
  4. On the Summary of JDBC Data Sources page, click New and then click Generic Data Source.
  5. Enter the following details for the new data source:
    • Name

      Example: Audit Data Source-0

    • JNDI Name

      Example: jdbc/AuditDB

    • Database Type

      Example: Oracle

    The figure below shows the example entries:

  6. Click Next and select the database driver. Choose "Oracle's Driver (Thin XA) Versions: 9.0.1 or later" if you are using Oracle database, and click Next.
  7. In the Connections Properties page, enter the following:
    • Database Name: Enter the name of the database (SID) to which to connect.

    • Host Name: Enter the hostname of the database.

    • Port: Enter the database port.

    • Database User Name: Enter the name of the audit schema that you created in RCU. The suffix is always _IAU for the audit schema. For example, if you supplied the prefix as "BIP"', then the schema name would be "BIP_IAU".

    • Password: Enter the password for the audit schema that you created in RCU.

    The figure below shows the Connection Properties page:

  8. Click Next. Accept the defaults, and click Test Configuration to verify the connection.
  9. Click Next. Select the listed servers where you want to make this JDBC connection available.
  10. Click Finish and then click Activate Changes in the Change Center.

Registering the Audit Storage Database to Your Domain

Register the JNDI/JDBC data source as your auditing data storage with Fusion Middleware Control (Enterprise Manager).

To register the audit storage database to your domain:
  1. Log on to Fusion Middleware Control.
  2. Navigate to the WebLogic Domain, right-click bifoundation_domain, then select Security, and then Security Provider Configuration.
  3. On the Security Provider Configuration page, under Audit Service, click Configure..
  4. On the Audit Service Configuration page, locate your Data Source JNDI Name by clicking Search datasource, as shown below.
  5. From the Select Data Source dialog, select the data source you created and click OK.
  6. Click Apply to continue.
  7. Restart WebLogic Server.

When the WebLogic Server is restarted, BI Publisher stores all auditing data in the database table called "IAU_BASE". To verify this procedure, try logging on to BI Publisher and opening a few reports. You should see the activity audited in the "IAU_BASE" table. If not, check the log file for possible errors. The log file is located under the Oracle BI Domain Home, for example:

ORACLE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

Once the data is successfully loading to the database tables, you can design your own auditing reports using BI Publisher.