Friday Jun 17, 2011

Upgrade Your Existing BI Publisher 11g ( to

It’s already more than a month now since BI Publisher was released at beginning of May. Have you already tried out many of the great new features? If you are already running on the first version of BI Publisher 11g ( you might wonder how to upgrade the existing BI Publisher to the version.

There are two ways to do this, one is ‘Out-Place’ and another is ‘In-Place’. The ‘Out-Place’ would be quite simple. Basically you will need to install the whole BI or just BI Publisher standalone R11.1.1.5 at a different location then you can switch the catalog to the existing one so that all the reports will be there in the new environment.

But sometimes things are not that simple, you might have some custom applications or configuration on the original environment and you want to keep all of them with the upgraded environment. For such scenarios, there is the ‘In-Place’ upgrade, which overrides on top of the original environment only the parts relevant for BI and BI Publisher, and that’s what I’m going to talk about today.

Here is the basic steps of the ‘In-Place’ upgrade.

  1. Upgrade WebLogic Server to 10.3.5
  2. Upgrade BI System to
  3. Upgrade Database Schema
  4. Re-register BI Components
  5. Upgrade FMW (Fusion Middleware) Configuration
  6. Upgrade BI Catalog

There is a section that talks about this upgrade from to as part of the overall upgrade document. But I hope my blog post summarized it and made it simple for you to cover only what’s necessary.

Upgrade Document:

Before You Start

Stop BI System and Backup

I can’t emphasize enough, but before you start PLEASE make sure you take a backup of the existing environments first. You want to stop all WebLogic Servers, Node Manager, OPMN, and OPMN-managed system components that are part of your Oracle BI domains. If you’re on Windows you can do this by simply selecting ‘Stop BI Services’ menu. Then backup the whole system.

Upgrade WebLogic Server to 10.3.5

Download WebLogic Server 10.3.5 Upgrade Installer

With BI installation your WebLogic Server (WLS) is 10.3.3 and you need to upgrade this to 10.3.5 before upgrading the BI part. In order to upgrade you will need this 10.3.5 upgrade version of WLS, which you can download from our support web site (

You can find the detail information about the installation and the patch numbers for the WLS upgrade installer on this document.

Just for your short cut, if you are running on Windows or Linux (x86) here is the patch number for your platform.

  • Windows 32 bit: 12395517:
  • Linux: 12395517

Upgrade WebLogic Server

1. After unzip the downloaded file, launch wls1035_upgrade_win32.exe if you’re on Windows.


2. Accept all the default values and keep ‘Next’ till end, and start the upgrade.

Once the upgrade process completes you’ll see the following window.


Now let’s move to the BI upgrade.

Upgrade BI Platform to with Software Only Install

Download BI

You can download the version from our OTN page for your evaluation or development. For the production use it’s recommended to download from eDelivery.

1. Launch the installer by double click ‘setup.exe’ (for Windows)

2. Select ‘Software Only Install’ option


3. Select your original Oracle Home where you installed BI


4. Click ‘Install’ button to start the installation.


And now the software part of the BI has been upgraded to Now let’s move to the database schema upgrade.

Upgrade Database Schema with Patch Assistant

You need to upgrade the BIPLATFORM and MDS Schemas. You can use the Patch Assistant utility to do this, and here is an example assuming you’ve created the schema with ‘DEV’ prefix, otherwise change it with yours accordingly.

Upgrade BIPLATFORM schema (if you created this schema with DEV_ prev)

psa.bat -dbConnectString localhost:1521:orcl -dbaUserName sys -schemaUserName DEV_BIPLATFORM

Upgrade MDS schema (if you created this schema with DEV_ prev)

psa.bat -dbConnectString localhost:1521:orcl -dbaUserName sys -schemaUserName DEV_MDS

Re-register BI System components

Now you need to re-register your BI system components such as BI Server, BI Presentation Server, etc to the Fusion Middleware system. You can do this by running ‘upgradenonj2eeapp.bat (or .sh)’ command, which can be found at %ORACLE_HOME%/opmn/bin.

Before you run, you need to start the WLS Server and make sure your WLS environment is not locked. If it’s locked then you need to release the system from the Fusion Middleware console before you run the following command.


Here is the syntax for the ‘upgradenonj2eeapp.bat (or .sh) command. 

   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user

And here is an example:

cd %BI_HOME%\opmn\bin

upgradenonj2eeapp.bat -oracleInstance C:\biee11\instances\instance1 -adminHost localhost -adminPort 7001 -adminUsername weblogic

Upgrade Fusion Middleware Configuration

There are a couple things on the Fusion Middleware need to be upgraded for the BI system to work. Here is a list of the components to upgrade.

  • Upgrade Shared Library (JRF)
  • Upgrade Fusion Middleware Security (OPSS)
  • Upgrade Code Grants
  • Upgrade OWSM Policy Repository

Before moving forward, you need to stop the WebLogic Server. Here is an example.

cd %MW_HOME%user_projects\domains\bifoundation_domain\bin


And, let’s start with ‘Upgrade Shared Library (JRF)’.

Upgrade Shared Library (JRF)

You can use updateJRF() WLST command to upgrade the shared libraries in your domain. Before you do this, you need to stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain.

Here is an example of the ‘upgradeJRF()’ command:

cd %MW_HOME%\oracle_common\common\bin



Upgrade Fusion Middleware Security (OPSS)

This step is to upgrade the Fusion Middleware security piece. You can use ‘upgradeOpss()’ WLST command. Here is a syntax for the command.

upgradeOpss(jpsConfig="existing_jps_config_file", jaznData="system_jazn_data_file")

The ‘existing jps-config.xml file can be found under %DOMAIN_HOME%/config/fmwconfig/jps-config.xml and the ‘system_jazn_data_file’ can be found under %MW_HOME%/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml.

And here is an example:

cd %MW_HOME%\oracle_common\common\bin


upgradeOpss(jpsConfig="c:/biee11/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml", jaznData="c:/biee11/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml")


Upgrade Code Grants for Oracle BI Domain

And this is the last step for the Fusion Middleware platform upgrade task. You need to run this python script ‘‘ script to configure the code grants necessary to ensure that SSL works correctly for Oracle BI. However, even if you don’t use SSL, you still need to run this script. And if you have multiple BI domains (Enterprise deployment) then you need to run this on each domain.

Here is an example:

cd %MW_HOME%\oracle_common\common\bin

wlst c:\biee11\Oracle_BI1\bin\ --bioraclehome c:\biee11\Oracle_BI1 --domainhome c:\biee11\user_projects\domains\bifoundation_domain

Upgrade OWSM Policy Repository

This is to upgrade OWSM (Oracle Web Service Manager) policy repository, you can use WLST command ‘upgradeWSMPolicyRepository()’. In order to run this command you need to have your WebLogic Server up-and-running. Here is an example.

cd %MW_HOME%user_projects\domains\bifoundation_domain\bin


cd %MW_HOME%\oracle_common\common\bin


connect ('weblogic','welcome1','t3://localhost:7001')


Upgrade BI Catalogs

This step is required only when you have your BI Publisher integrated with BIEE. If your BI Publisher is deployed as a standalone then you don’t need to follow this step.

Now finally, you can upgrade the BI catalog. This won’t upgrade your BI Publisher reports themselves, but it just upgrades some attributes information inside the catalog. Before you do this upgrade, make sure the BI system components are not running. You can check the status by the command below.

opmnctl status

You can do the upgrade by updating a configuration file ‘instanceconfig.xml’, which can be found at %BI_HOME%\instances\instance1\config\coreapplication_obips1, and change the value of ‘UpgradeAndExit’ to be ‘true’. Here is an example:

<ps:Catalog xmlns:ps="">

After you made the change and save the file, you need to start the BI Presentation Server. This time you want to start only the BI Presentation Server instead of starting all the servers. You can use ‘opmnctl’ to do so, and here is an example.

opmnctl startproc ias-component=coreapplication_obips1

This would upgrade your BI Catalog to be

After the catalog is updated, you can stop the BI Presentation Server so that you can modify the instanceconfig.xml file again to revert the upgradeAndExit value back to ‘false’.

Start Explore BI Publisher

After all the above steps, you can start all the BI Services, access to the same URL, now you have your BI Publisher and/or BI in your hands. Have fun exploring all the new features of R11.1.1.5!


Thursday May 19, 2011 New Feature – More Data to Audit and Monitor


We believe Auditing and Monitoring capability for Reporting is crucial for the IT management and governance regardless if it’s enterprise level or department level deployment. So we are always committed to improve our BI Publisher Auditing and Monitoring capability since we introduced it for the first time

With the first release of 11g ( we added this Auditing and Monitoring capability, which enables you to monitor who access to which report at what time.

With this new release of, we added more data to audit and monitor especially more BI Publisher reports specific information such as:

  • Report output format type
  • Layout Template name
  • Reporting locale
  • If the reports is run online (on-demand) or through the scheduler
  • Processing time
  • Reporting data size
  • Report error message
  • Scheduled job information

And these information can be all available through the database tables so you can use BI Publisher to generate your Auditing reports or visualize the data to gain more insights about how your users are doing on your reporting platform.

If you are interested in the power of the new BI Publisher Auditing and Monitoring, here is a video.

And, if you want to know how to enable the Auditing with the new data sets I’ll cover that below.

Enable Auditing Data

There are three things you need to do to enable the Auditing data.

Setup basic Auditing configuration

I have already talked about these steps before, take a look at these two posts for the detail.

Run ‘xmlpserver_audit.sql’

There is a SQL script that you can run to create an additional table, which will store more BI Publisher reports specific data to audit and monitor.

Let’s take a look how to run the script step by step.

1. Change the current directory to ‘%BI_HOME%user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Audit’.

This directory should contain a file called ‘xmlpserver_audit.sql’ file.

2. Run this script as SYS or SYSTEM user and alter the session user to the schema who owns the AUDIT tables.


Let’s say you have created the Audit schema with the RCU with ‘KAN_IAU’, then you can follow something like below.

$ sqlplus / as sysdba

SQL*Plus: Release Production on Mon May 2 13:53:49 2011

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> alter session set CURRENT_SCHEMA = KAN_IAU;

Session altered.

Now you can run the ‘xmlpserver_audti.sql’ script. Note that, when you run you'll be prompted to enter the following three schema names.

  • Basic Auditing Schema name
  • Edit Auditing Schema name
  • View Auditing Schema name

With the above example of using ‘KAN_IAU’ as your basic schema, it would be something like below.


Here is the example:

SQL> @xmlpserver_audit

Table created.

Index created.

Enter value for 1: KAN_IAU

old 1: GRANT ALL on xmlpserver to &&1

new 1: GRANT ALL on xmlpserver to KAN_IAU

Grant succeeded.

Enter value for 2: KAN_IAU_APPEND

old 1: GRANT INSERT on xmlpserver to &&2

new 1: GRANT INSERT on xmlpserver to KAN_IAU_APPEND

Grant succeeded.

Enter value for 3: KAN_IAU_VIEWER

old 1: GRANT SELECT on xmlpserver to &&3

new 1: GRANT SELECT on xmlpserver to KAN_IAU_VIEWER

Grant succeeded.

old 1: CREATE OR REPLACE SYNONYM &&3..xmlpserver FOR &&1..xmlpserver


Synonym created.

old 1: CREATE OR REPLACE SYNONYM &&2..xmlpserver FOR &&1..xmlpserver


Synonym created.

After that you need to restart the WebLogic Server to take that in effect. Once that’s done, BI Publisher will start feeding all the auditing and monitoring related information into the auditing tables, and you should be able to start access to the data to create reports and visualize it with BI Publisher.

Create Reports to Visualize

If you have already finished the steps mentioned on the previous blog posts then you should already have a JNDI/JDBC connection created. If you haven’t yet, then take a look at the following post. 

  • Make sure you assign appropriate application roles to this data source connection so that you or any users who need to create reports for the BI Publisher Auditing and Monitoring data will have an access to the data source.


    With this new set of data available, you can now start creating reports to gain more insights about how your users use the reporting platform and prepare for a better reporting experience by responding and adjusting promptly.

    Start with Sample Reports

    We’re planning to release a set of sample Auditing and Monitoring reports as part of our sample reports inside the catalog some time soon but till then you can start creating your own reports against the Auditing tables by using BI Publisher. For those looking for something quick, I’m attaching a sample report here

    You can download the above files and upload them to your BI Publisher 11g ( environment from the BI Publisher Catalog UI, but make sure the following three points before you run.

    1. Change the Data Model reference inside the Auditing report to point to the Auditing Data Model that you uploaded


    2. Change the Data Source inside the Auditing Data Model to your JNDI connection


    3. Update the SQL query to point to appropriate schema name.


    Path to Improve Reporting Experience

    Again, the Auditing is not just about collecting the auditing data and record it. It’s about how you as IT manager or administrator understand your users and reports on the reports environment in order to improve the reporting experience. The more you understand them the better service you can provide. We believe that the new release of BI Publisher would provide you a wide range of data to help you understand your reporting environment better and quickly. Hope you’ll enjoy the power of new BI Publisher Auditing and Monitoring capability.

    Also, as always, we’re very interested in your feedback. Please let us know what do you think about the data currently available, the sample reports, any additional requirements or improvement suggestion.

  • Tuesday Mar 22, 2011

    10G Users! Let’s Upgrade to BI Publisher 11G!

    [Read More]

    Friday Oct 23, 2009

    Installing BI Publisher into Weblogic Server 11g

    [Read More]

    Follow bipublisher on Twitter Find Us on Facebook BI Publisher Youtube ChannelDiscussion Forum

    Join our BI Publisher community to get the most and keep updated with the latest news, How-to, Solutions! Share your feedback and let us hear your voice @bipublisher on Twitter, on our official Facebook page, and Youtube!


    « June 2016