BI Publisher 11g Auditing

BI Publisher 11g Auditing

Create Audit Schema with RCU

Here are the steps:

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 new prefix, for example ‘BIP’, ‘KAN’, etc.
5. Select ‘Audit Services’ from the list of schemas.
6. Click Next and accept the tablespace creation.
7. Click Finish to start the process

After this, there should be following three Audit related schema created in your database.

• <prefix>_IAU (e.g. KAN_IAU)
• <prefix>_IAU_APPEND (e.g. KAN_IAU_APPEND)
• <prefix>_IAU_VIEWER (e.g. KAN_IAU_VIEWER)

Setup Datasource at WebLogic

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

• Connect to the Oracle WebLogic Server administration console:
  http://hostname:port/console (e.g. http://report.oracle.com:7001/console)
• Under Services, click the Data Sources link.
• 

• Click ‘Lock & Edit’ so that you can make changes

• 
• Click New –> ‘Generic Datasource’ to create a new data source.
• Enter the following details for the new data source:
  Name: Enter a name such as Audit Data Source-0.
  JNDI Name: jdbc/AuditDB
  Database Type: Oracle

• 
• Click Next and select ‘Oracle’s Driver (Thin XA) Versions: 9.0.1 or later’ as Database Driver (if you’re using Oracle database), and click Next.
• The Connection Properties page appears. Enter the following information:
  Database Name: Enter the name of the database (SID) to which you will connect.
  Host Name: Enter the hostname of the database.
  Port: Enter the database port.
  Database User Name: This is the name of the audit schema that you created in
  RCU. The suffix is always IAU for the audit schema. For example, if you gave
  the prefix as ‘BIP’, then the schema name would be ‘KAN_IAU’.
  Password: This is the password for the audit schema that you created in RCU.

• Click Next.
• Accept the defaults, and click Test Configuration to verify the connection.
• Click Next
• Check listed servers where you want to make this JDBC connection available.

• Click ‘Finish’ !

After that, make sure you click ‘Activate Changes’ at the left hand side top to take the new JDBC connection in effect.

Register your Audit Data Storing Database to your Domain

Finally, you can register the JNDI/JDBC datasource as your Auditing data storage with Fusion Middleware Control (EM). Here are the steps:

1. Login to Fusion Middleware Control
2. Navigate to Weblogic Domain, right click on ‘bifoundation…..’, select Security, then Audit Store.
3. Click the searchlight icon next to the Datasource JNDI Name field.

4.Select the Audit JNDI/JDBC datasource you created in the previous step in the pop-up window and click OK.

5. Click Apply to continue.
6. Restart the whole WebLogic Servers in the domain.

After this, now the BI Publisher should start feeding all the auditing data into the database table called ‘IAU_BASE’. Try login to BI Publisher and open a couple of reports, you should see the activity audited in the ‘IAU_BASE’ table. If not working, you might want to check the log file, which is located at $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

to see if there is any error.

Once you have the data in the database table, now, it’s time to visualize with BI Publisher reports!

BI Publisher

Register Auditing Datasource as JNDI datasource

First thing you need to do is to register the audit datasource (JNDI/JDBC connection) you created in the previous step as JNDI data source at BI Publisher. It is a JDBC connection registered as JNDI, that means you don’t need to create a new JDBC connection by typing the connection URL, username/password, etc. You can just register it using the JNDI name. (e.g. jdbc/AuditDB)

1. Login to BI Publisher as Administrator (e.g. weblogic)
2. Go to Administration Page
3. Click ‘JNDI Connection’ under Data Sources and Click ‘New’
4. Type Data Source Name and JNDI Name. The JNDI Name is the one you created in the WebLogic Console as the auditing datasource. (e.g. jdbc/AuditDB)
5. Click ‘Test Connection’ to make sure the datasource connection works.
6. Provide appropriate roles so that the report developers or viewers can share this data source to view reports.
7. Click ‘Apply’ to save.

Enable Auditing in BI Publisher

• Administration > Server ConfigurationThen click Apply.

Create New Audit Folder in BI Publisher Catalog

• New Folder

• Capital Delivery Audit

Create

Upload Resources

Click upload resource icon to upload .xdoz and report into the catalog/directory.

Upload

Repeat for .xdoz

Final Output