How to Audit and Monitor BI Publisher Reports Access

Enable Auditing related properties in BI Publisher configuration file

1.     Open xmlp-server-config.xml file, which is located under $BI_HOME/ user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Configuration directory.

2.    Set the following three properties values to ‘true’.

·  AUDIT_ENABLED

·  MONITORING_ENABLED

·  AUDIT_JPS_INTEGRATION

The ‘AUDIT_JPS_INTEGRATION’ is not in the file as default, so you need to add this. Here is an example of how it looks for the xmlp-server-config.xml file after the modification.

 <?xml version="1.0" encoding="UTF-8" standalone="no"?><xmlpConfigxmlns="http://xmlns.oracle.com/oxp/xmlp">

<property name="SAW_SERVER" value="adc6160510"/>

<property name="SAW_SESSION_TIMEOUT" value="90"/>

<property name="DEBUG_LEVEL" value="exception"/>

<property name="SAW_PORT" value="7001"/>

<property name="SAW_PASSWORD" value=""/>

<property name="SAW_PROTOCOL" value="http"/>

<property name="SAW_VERSION" value="v6"/>

<property name="SAW_USERNAME" value=""/>

<property name="SAW_URL_SUFFIX" value="analytics/saw.dll"/>

<property name="MONITORING_ENABLED" value="true"/>

<property name="MONITORING_DEFAULT_HISTORY_SIZE" value="30"/>

<property name="AUDIT_ENABLED" value="true"/>

<property name="JSESSION_RESET_DISABLED" value="true"/>

<property name="SECURITY_MODEL" value="ORACLE_AS_JPS"/>

<property name="AUDIT_JPS_INTEGRATION" value="true"/>

</xmlpConfig>

 

Copy component_events.xml file to Audit Framework’s location

There is a Audit related configuration file provided by BI Publisher that needs to be copied to the Audit Framework location.

1.     Go to the following directory.

$BI_HOME /oracle_common/modules/oracle.iau_11.1.1/components

Create a directory called ‘xmlpserver’

Copy component_events.xml file from

/user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Audit

To

the newly created ‘xmlpserver’ directory.

Enable Auditing Policy with Fusion Middleware Control (EM)

Now you can set a level of the auditing for each BI Publisher’s auditing type by using Fusion Middleware Control (a.k.a. Enterprise Manager).

1.     Login to Fusion Middleware Control UI

http://hostname:port/em (e.g. reporting.oracle.com:7001/em)

2.     Access to Audit Policy configuration UI from the menu

Under WebLogic Domain, right-click bifoundation_domain, select Security and then click Audit Policy.

 

3.     Set Audit Level for BI Publisher.

While you can select ‘Custom’ to set a customized level of Auditing for each component, I’m selecting ‘Medium’ for this exercise.

Restart WebLogic Server

After all the above settings, now you need to restart the WebLogic Server instance in order to take those changes in effect. If you’re on Windows you can simply do this by selecting ‘Stop BI Servers’ and ‘Start BI Servers’ from the Start menu.

If you’re on Linux then you can run ‘stopWebLogic.sh’ and ‘startWebLogic.sh’, which can be found under $BI_HOME/user_projects/domains/bifoundation_domain/bin

Start Auditing!

Now assuming that you have completed the above steps successfully, then from this point on any reporting activity should be audited and stored in the auditing log file, which can be found at $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/auditlogs/xmlpserver/audit.log

or 

$BI_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/auditlogs/xmlpserver/audit.log