Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher (Oracle Fusion Applications Edition) Release 11g (11.1.1) Part Number E20837-01

Contents

Previous

Next

Diagnostics and Performance Monitoring in Oracle BI Publisher

This chapter covers the following topics:

• Diagnosing and Resolving Issues in Oracle BI Publisher
• Configuring Log Files
• Viewing Log Messages
• About Performance Monitoring and User Auditing
• Enabling Monitoring
• Viewing the Audit Log
• Configuring an Audit Repository
• Using BI Publisher to Create Audit Reports from Your Audit Repository
• Viewing Performance Statistics in the MBean Browser

Diagnosing and Resolving Issues in Oracle BI Publisher

System Administrators are typically responsible for supporting end users when they experience issues with the use of Oracle BI Publisher and for interacting with Oracle Support to understand the cause of issues and apply fixes.

Issues may be reported in response to end users receiving error messages, experiencing poor performance, or lack of availability.

The principal activities administrators perform to support issue resolution include:

• Examination of error and diagnostic log information. For more information, see:

  • About Diagnostic Log Files

  • Configuring Log Files

  • Viewing Log Messages

• Examination of system and process metrics to understand availability and performance issues. For more information, see:

  • About Performance Monitoring and User Auditing

  • Enabling Monitoring

  • Viewing the Audit Log

  • Configuring an Audit Repository

  • Using BI Publisher to Create Audit Reports from Your Audit Repository

  • Viewing Performance Statistics in the MBean Browser

About Diagnostic Log Files

BI Publisher writes diagnostic log files in the Oracle Diagnostic Logging (ODL) format. Log file naming and the format of the contents of log files conforms to an Oracle standard. You can view log files by using the WLST displayLogs command, or you can download log files to your local client and view them using another tool (for example a text editor, or another file viewing utility).

Log files are created and edited using Oracle Fusion Middleware Control. By default, after install, the bipublisher-handler log is created. You can configure this log file or create a new logger.

About Log File Message Categories and Levels

Each log file message category is set to a specific default value between 1-32, and only messages with a level less or equal to the log level will be logged.

Five log file message categories exist as follows:

About Log File Formats

A log file must contain a consistent format. However, since there can be multiple formats, you can change the format used in a log file. When you change the format used in a log file, and the new format differs from the current log file's format, a new log file is created. For example, a log file containing ODL-XML, always contains XML, and will never be mixed with text.

Configure the log file format in the Edit Log File dialog (see Configuring Log Files). The format can by Text or XML.

About Log File Rotation

Log file rotation can be file size based or time based. Whenever a log file exceeds the rotation criterion, the existing log file is renamed, and a new log file is created.

The file naming looks like this:

• log.xml

• log.xml.1 (oldest log file)

• log.xml.n

Configuring Log Files

Configure log files in Oracle Fusion Middleware Control.

1. In Oracle Fusion Middleware Control, locate the BI Publisher server. For example:

   Under Application Deployments, expand bipublisher (11.1.1) (bi_cluster), and then right-click bipublisher (11.1.1)(bi_server1)

2. From the menu, click Logs and then Log Configuration, as shown in the following figure:

   

3. By default, the bipublisher-handler log is created. Select bipublisher-handler in the table and click Edit Configuration.

   

4. In the Edit Configuration dialog, set the Log Level and configure other options.

   

Viewing Log Messages

You can view log messages using Oracle Fusion Middleware Control or you can view the log files directly.

To view log messages in Oracle Fusion Middleware Control:

1. In Oracle Fusion Middleware Control, locate the BI Publisher server. For example:

   Under Application Deployments, expand bipublisher (11.1.1) (bi_cluster), and then right-click bipublisher (11.1.1)(bi_server1)

2. From the menu, click Logs and then View Log Messages, as shown in the following figure:

   

3. To view a specific log file, click Target Log Files.

   

4. From the Log Files page, select a specific log to view messages or download the log file.

   

5. Click View Log File to view the messages.

   

Viewing Messages by Reading the Log File

The log file is located in the directory specified in the Log Path in the Edit Log File dialog. Navigate to the directory on your server to view the log file:

The following example shows an ODL format error message:

<msg time="2009-07-30T16:00:03.150-07:00" comp_id="xdo" type="ERROR" level="1" host_id="MyBIPHost" host_addr="120.19.168.17" module="oracle.xdo" tid="11" user="Administrator">
<txt>Variable 'G_dept' is missing...</txt>
</msg>

About Performance Monitoring and User Auditing

Performance monitoring enables you to monitor the performance of queries, reports and document generation and to analyze the provided details. User auditing provides information about what users logged in, when, how many times, what reports they accessed, and other actions they took within the application.

BI Publisher collects performance statistics through JMX Management Beans or Mbeans. Each MBean reveals attributes, operations, and relevant statistics gathered by the Oracle Dynamic Monitoring Service (DMS). The following table summarizes the beans that are provided:

Enabling Monitoring

To enable monitoring:

1. Update properties in the BI Publisher server configuration file.

2. Copy the component_events.xml file to your Middleware Home.

3. Configure the Audit Policy Settings with Fusion Middleware Control (Enterprise Manager)

4. Restart WebLogic Server.

Update Properties in the BI Publisher Server Configuration File

Locate the xmlp-server-config.xml file in the BI Publisher repository under config/bipublisher/repository/Admin/Configuration/xmlp-server-config.xml located under the Oracle BI Domain Home (for example:MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Configuration.

A sample configuration file is shown in the following figure:

Perform the following:

1. Make a backup of the file.

2. Add the following property to the file and set it to "true":

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

   This property enables the integration of performance monitoring and auditing with Oracle Fusion Middleware Control.

3. Update the properties in the following table to enable performance monitoring and auditing:

   Property	Description
   MONITORING_ENABLED	Set to "true" to enable monitoring. The default is "false".
   AUDIT_ENABLED	Set to "true" to enable auditing. The default is "false".

Following is a sample configuration file with the properties updated:

<xmlpConfig xmlns="http://xmlns.oracle.com/oxp/xmlp">
   <property name="SAW_SERVER" value=""/>
   <property name="SAW_SESSION_TIMEOUT" value="90"/>
   <property name="DEBUG_LEVEL" value="exception"/>
   <property name="SAW_PORT" value=""/>
   <property name="SAW_PASSWORD" value=""/>
   <property name="SAW_PROTOCOL" value="http"/>
   <property name="SAW_VERSION" value="v4"/>
   <property name="SAW_USERNAME" value=""/>
   <property name="MONITORING_ENABLED" value="true"/>
   <property name="AUDIT_ENABLED" value="true"/>
   <property name=”AUDIT_JPS_INTEGRATION” value=”true"/
</xmlpConfig>

Copy the component_events.xml File to Your Middleware Home

1. Navigate to the MIDDLEWARE_HOME/oracle_common/modules/oracle.iau_11.1.1/components directory.

2. In the components directory create a directory named "xmlpserver".

3. Locate the component_events.xml file in the BI Publisher repository under config/bipublisher/repository/Admin/Audit/component_events.xml located under the Oracle BI Domain Home (for example: MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Audit.

4. Copy the component_events.xml file to the newly created xmlpserver directory.

   

Configure the Audit Policy Settings with Fusion Middleware Control

To configure the audit policy settings:

1. In Oracle Fusion Middleware Control, under WebLogic Domain, right-click bifoundation_domain. From the menu click Security and then click Audit Policy as shown in the following figure:

   

2. The Audit Policy table displays all the audited applications under the bifoundation_domain. Set the Audit Level to enable auditing for BI Publisher.

   

You will most likely set the Audit Level to Medium. If you wish to customize the audit level for each event, select Custom from the Audit Level list. This will enable you to set the audit level for each event and apply filters.

The events that are audited for the BI Publisher server are:

• User Logins

• User Logouts

• Report Request

• Scheduled Request

• Report Republish

• Report Data Download

• Report Download

• Report Data Process

• Report Rendering

• Report Delivery

Restart WebLogic Server

Restart the WebLogic Serve instance. You can do this using Oracle Fusion Middleware Control, or if you are running Windows, you can select "Stop BI Servers" and then "Start BI Servers" from the Start menu.

Viewing the Audit Log

If you set the property AUDIT_JPS_INTEGRATION to true, the audit log can be viewed under the xmlpserver folder under the WebLogic Server AdminServer directory: /AdminServer/logs/auditlogs/xmlpserver/audit.log

Alternatively, if you can configure an audit repository in your database to store audit data in database tables instead of the log file (the file is not generated in this case). The collected data can be analyzed using reports provided by Audit Framework, or you can create your own reports using BI Publisher.

For more information on the reports provided by Audit Framework, see "Using Audit Analysis and Reporting" in the Oracle Fusion Middleware Application Security Guide 11g.

The following section describes how to set up the audit repository in your database to store the auditing data.

Configuring an Audit Repository

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

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, and enter a prefix; for example: BIP

5. Select Audit Services from the list of schemas (shown in the following figure).

   

6. Click Next and accept the tablespace creation.

7. Click Finish to start the process.

When the Repository Creation Utility process finishes, the following three audit-related schemas will be 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)

Create a 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://report.oracle.com:7001/console)

2. Under Services, click the Data Sources link, as shown in the following figure:

   

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 following figure 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 you will 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.

   An example Connections Properties page is shown in the following figure:

   

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.

Register the Audit-Storing Database to Your Domain

To register the JNDI/JDBC data source as your auditing data storage with Fusion Middleware Control (Enterprise Manager):

1. Log in to Fusion Middleware Control.

2. Navigate to the WebLogic Domain, right click bifoundation_domain, then select Security, then Audit Store. The navigation path is shown in the following figure:

   

3. Click Search Data Sources. From the Select Data Source dialog, select the data source you created and click OK.

4. Click Apply to continue

5. Restart WebLogic Server.

When the WebLogic Server is restarted, BI Publisher will store all auditing data into the database table called "IAU_BASE". To verify this procedure, try logging in 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, which is located at: $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

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

Using BI Publisher to Create Audit Reports from Your Audit Repository

Once you have the auditing repository set up, you can use BI Publisher to create your own reports to visualize your auditing data. To create a report on your auditing data in BI Publisher:

1. Register the data source in BI Publisher.

2. Create a data model.

3. Create the report.

Registering the Data Source in BI Publisher

Register the audit data source (JNDI/JDBC connection) that you created in the previous procedure as a JNDI data source in BI Publisher. Because you created a JDBC connection registered as JNDI, you do not need to create a new JDBC connection by typing the connection URL, username/password, and so on. You can just register it using the JNDI name (for example: jdbc/AuditDB).

1. Log in to BI Publisher with administrator privileges and click the Administration link.

2. Under Data Sources, click JNDI Connection, then click Add Data Source.

3. Enter the Data Source Name and JNDI Name. The JNDI Name is the name you provided in the WebLogic Console as the auditing data source (for example :jdbc/AuditDB).

4. Click Test Connection to ensure that the data source connection works.

5. Add the appropriate roles to the data source so that the report developers and consumers can view the reports built on this data source.

6. Click Apply to save.

Creating a Data Model

To create a data model from your auditing data source:

Note: For the complete guidelines for developing data models in BI Publisher, see the Oracle Fusion Middleware Data Modeling Guide for Oracle Business Intelligence Publisher.

1. On the global header, click New and then click Data Model.

2. Set the Default Data Source to the audit JNDI data source.

3. Select SQL Query for your data set

4. Use the Query Builder to build a query or just type a SQL query against the IAU_BASE table. The IAU_BASE table contains all the auditing data for other products running on the WebLogic Server such as JPS, OID, and so on. To create a data model that contains only the BI Publisher data, then you can filter the data based on the value of the IAU_COMPONENTTYPE column that contains the product name. For BI Publisher, the value is "xmlpserver".

   The following SQL query sample selects only BI Publisher data:

   select     "IAU_BASE"."IAU_COMPONENTTYPE" as "IAU_COMPONENTTYPE", 
        "IAU_BASE"."IAU_EVENTTYPE" as "IAU_EVENTTYPE", 
        "IAU_BASE"."IAU_EVENTCATEGORY" as "IAU_EVENTCATEGORY", 
        "IAU_BASE"."IAU_TSTZORIGINATING" as "IAU_TSTZORIGINATING", 
      to_char("IAU_TSTZORIGINATING", 'YYYY-MM-DD') IAU_DATE, 
      to_char("IAU_TSTZORIGINATING", 'DAY') as IAU_DAY, 
      to_char("IAU_TSTZORIGINATING", 'HH24') as IAU_HH24, 
      to_char("IAU_TSTZORIGINATING", 'WW') as IAU_WEEK_OF_YEAR, 
        "IAU_BASE"."IAU_INITIATOR" as "IAU_INITIATOR", 
        "IAU_BASE"."IAU_RESOURCE" as "IAU_RESOURCE", 
        "IAU_BASE"."IAU_TARGET" as "IAU_TARGET", 
        "IAU_BASE"."IAU_MESSAGETEXT" as "IAU_MESSAGETEXT", 
        "IAU_BASE"."IAU_FAILURECODE" as "IAU_FAILURECODE", 
        "IAU_BASE"."IAU_REMOTEIP" as "IAU_REMOTEIP" 
   from    "BIP_IAU"."IAU_BASE" "IAU_BASE" 
   where "IAU_BASE"."IAU_COMPONENTTYPE" = 'xmlpserver'
   

5. To test your data model, click Get XML Output. Select a sample size, and run your data model. Save the sample XML to your data model.

6. Save your data model.

Creating the Report

Now you can use one of the BI Publisher’s layout options to design the report layout and visualize the auditing data. To create a report using the BI Publisher layout editor: .

1. On the global header, click New and then click Report.

2. Select the data model you created in the previous procedure.

3. To use the layout editor, click Add New Layout, and then click one of the Basic Templates to get started.

   For complete instructions on using the layout editor, see the topic: "Creating a BI Publisher Layout Template" in the Help or in the Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher.

The following figure shows using the layout editor to design a report based on the auditing data:

The following figure shows a sample completed auditing report displayed in the report viewer:

Viewing Performance Statistics in the MBean Browser

To view the performance statistics collected by the Report Event Monitor, Service Event Monitor, and User Event Monitor, navigate to the System MBean browser as follows:

1. In Oracle Fusion Middleware Control, locate the BI Publisher server. For example:

   Under Application Deployments, expand bipublisher (11.1.1) (bi_cluster), and then right-click bipublisher (11.1.1)(bi_server1)

2. From the menu, click System MBean Browser, as shown in the following figure:

   

3. In the System MBean Browser, under the Application Defined MBeans, expand the oracle.xdo folder to view the BI Publisher MBeans. Expand the list and select the bean to view the details.

   

Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved.