This chapter describes how to upgrade your existing Oracle Business Intelligence Publisher 10g Release 3 (10.1.3.4 or later) environment to Oracle Business Intelligence Publisher 11g.
This chapter contains the following sections:
Task 1: Understand the Starting Points for Oracle Business Intelligence Publisher Upgrade
Task 2: Decide Upon an Oracle Business Intelligence Topology
Task 3: Run RCU to Create the Destination BIPLATFORM Schemas
Task 4: Install and Configure Oracle Business Intelligence Publisher 11g
Task 5: Upgrade the Oracle Business Intelligence Publisher Repository
Task 6: Upgrade the Oracle Business Intelligence Publisher Scheduler Schema
Task 7: Perform Any Required Post-Upgrade Configuration Tasks
Task 8: Verify the Oracle Business Intelligence Publisher Upgrade
For information about starting points for an Oracle Business Intelligence Publisher upgrade, see Chapter 2, "Supported Starting Points for Oracle Business Intelligence Upgrade." If you are running a version of Oracle Business Intelligence Publisher older than version specified in Chapter 2, you must upgrade to the supported starting point version before attempting to upgrade to 11g.
If you are already running Oracle Fusion Middleware 11g, refer to the Oracle Fusion Middleware Patching Guide, which provides information about applying the latest Oracle Fusion Middleware patches.
This guide provides instructions for upgrading from Oracle Business Intelligence Publisher 10g to the latest Oracle Business Intelligence Publisher 11g.
To help you decide on a target topology for your Oracle Business Intelligence 11g deployment, see Chapter 3, "Oracle Business Intelligence for 10g Users." Chapter 3 compares 10g and 11g features, directory structures, and architecture. It also describes Oracle Business Intelligence Publisher 11g integration with Oracle WebLogic Server and Oracle Fusion Middleware applications.
For more information, see "Understanding Oracle Fusion Middleware Concepts" in the Oracle Fusion Middleware Administrator's Guide.
The Repository Creation Utility (RCU) is a graphical tool for creating and managing Oracle Fusion Middleware database schema in your database. To create your Oracle Business Intelligence Publisher 11g destination schema, see Create Database Schema Using the Repository Creation Utility in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Important screens when running RCU:
Database Connection Details screen - Select the type of database on your system. This is the database in which you create the Oracle Business Intelligence schemas. Provide the necessary credentials for RCU to be able to connect to your database.
Select Components screen - Near the top of the screen, select Create a New Prefix. The default prefix is DEV. You can provide another prefix, if preferred.
Expand the Business Intelligence component group by clicking the plus sign (+) next to it. Then, click Business Intelligence Platform so that a check appears next to it. This action automatically selects the Metadata Services (MDS) schema (under the AS Common Schemas group), which is also required by Oracle Business Intelligence.
Note:
If you have already run RCU to create the destination BIPLATFORM schema for Oracle Business Intelligence Enterprise Edition, you are not required to perform Task 3. Oracle BI EE and Oracle BI Publisher share the BIPLATFORM schema.For installation instructions for Oracle Business Intelligence Publisher, see "Running the Installer" in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Important screens when running the Oracle Business Intelligence Installer:
Select Installation Type screen - Select Enterprise install for new installations. This option Installs a new Oracle Business Intelligence system for a hosted deployment on one or more computers.
Create or Scale Out BI System screen - Click Create New BI System.
Specify Installation Location screen - Specify the Oracle Middleware home location.
Database Details screen - Specify the database type, the database connection string, and the user name and password for the Business Intelligence Platform schema.
Note:
If you have already installed Oracle Business Intelligence Enterprise Edition, and selected the option to install Oracle BI Publisher, you are not required to perform Task 4.Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the Oracle Business Intelligence Publisher Repository.
Note:
You can upgrade Oracle Business Intelligence Publisher Repository and Scheduler schema in any order.Before Running Upgrade Assistant
Before you start Upgrade Assistant follow these steps:
Back up the 10g and 11g repositories before running Upgrade Assistant.
Choose your upgraded Oracle BI Publisher 11g repository path. This can be same as your installed 11g repository path, for example, \user_projects\domains\bifoundation_domain\config\bipublisher\repository. It can also be a new path on the server, for example, D:\MyUpgradedBIPRepository\repository. If you choose a new path for the upgraded repository, copy the content of 11g repository to this new path.
When you install Oracle BI Publisher 11g, the catalog type is Oracle BI EE Catalog. In 10g the repository has always been a file-based repository (not Oracle BI EE Catalog). Upgrade Assistant provides a file based repository after upgrade. Therefore, change your catalog type to Oracle BI Publisher - File System before running Upgrade Assistant as follows:
Before starting the upgrade, log in to the Oracle BI Publisher Administration page, navigate to the Server Configuration page, under the Server Maintenance section, change the Catalog Type to Oracle BI Publisher - File System.
Enter the repository path. If you are using a new repository path for the upgraded repository, update the path, for example: D:\MyUpgradedBIPRepository\repository, for both the configuration folder path and the Oracle BI Publisher repository path in the catalog section.
If you are using the default 11g repository path for upgrade, you can keep the default repository path for both the Configuration Folder and BI publisher Repository Path.
Click the Apply button.
Stop the Managed Server on which Oracle BI Publisher is running.
Admin Server and Managed Servers
Before running Upgrade Assistant, shut down the Managed Server. The Admin Server should remain running.
For information on what is upgraded by Upgrade Assistant, see Section 3.6, "What Gets Upgraded?."
For a descriptions of the security model upgrade path, see Section 3.6.3, "Security Model Mapping for Oracle BI Publisher Upgrade."
Upgrade Assistant is installed automatically into the bin directory of your Oracle Fusion Middleware Oracle home.
Note:
The following sections describe how to use the Upgrade Assistant in graphical user interface mode. You can also use the Upgrade Assistant command line to perform these tasks.For more information, see "Using the Upgrade Assistant Command-Line Interface" in the Oracle Fusion Middleware Upgrade Planning Guide.
Table 5-1 Running the Upgrade Assistant to Upgrade the Oracle BI Publisher Repository
| Step | Screen | Description and Action Required |
|---|---|---|
|
1 |
None. |
To start the Upgrade Assistant using the graphical user interface: Change directory to the For UNIX: ./ua On a Windows operating system: ua.bat |
|
2 |
Click Next to continue. |
|
|
3 |
Select Upgrade Oracle BI Publisher Repository. Click Next to continue. |
|
|
4 |
Select Upgrade 10g BI Publisher Repository Directory or Upgrade E-Business Suite Data Template Directory. For Upgrade 10g BI Publisher Repository Directory, enter, or browse to the Repository Directory. For Upgrade E-Business Suite Data Template Directory, enter, or browse to the Data Template Directory. Note: Upgrade Assistant does not support reading the data definition from the E-Business Suite environment. Store your data template XML files in a file system and run Upgrade Assistant to create an equivalent data model definition in the Oracle BI Publisher Enterprise Server. Click Next to continue. |
|
|
5 |
In the Repository Directory field, enter the destination 11g BI Publisher Repository directory if you selected the 10g BI Publisher Repository Directory as your source directory. The default location of the destination repository is MWHOME\user_projects\domains\bifoundation_domain\config\bipublisher\repository. However, this destination repository path can be any path on the server. Enter the 11g data model directory if you selected the E-Business Suite Data Template Directory as your source. Click Next to continue. |
|
|
6 |
Enter the following:
Click Next to continue. |
|
|
7 |
During the examination process, Upgrade Assistant checks for the following:
Under the Status column, the word succeeded should appear. If instead, the word failed appears, inspect the log file for details. Click Upgrade. |
|
|
8 |
Click Upgrade to continue. |
|
|
The upgrade process begins, and is completed when the status bar reaches 100 percent. For an illustration of what gets upgraded, see Section 3.6, "What Gets Upgraded?." If there are errors during the upgrade, inspect the log file for details. The log files are located in the following directory: BI_ORACLE_HOME/upgrade/logs/ua<timestamp>.log For Windows Operating Systems: BI_ORACLE_HOME\upgrade\logs\ua<timestamp>.log Where <timestamp> is the current date and time. Click Next to continue. |
||
|
9 |
Click Close. |
Note:
Review the log for any errors or warnings. Resolve any errors or warnings in 10g files and resolve them manually in the upgraded 11g RPDs and Web Catalogs.Use the Oracle Fusion Middleware Upgrade Assistant to upgrade the Oracle Business Intelligence Publisher Scheduler schema.
Upgrade Assistant is installed automatically into the bin directory of your Oracle Fusion Middleware Oracle home.
Note:
You can upgrade Oracle Business Intelligence Publisher Repository or Scheduler schema in any order.Upgrade Assistant performs the schema upgrade by upgrading source Oracle Business Intelligence Publisher Scheduler schema content into the destination Oracle Business Intelligence Publisher Scheduler schema content.
Table 5-2 Running the Upgrade Assistant to Upgrade the Oracle BI Publisher Scheduler Schema
Note:
Review the log for any errors or warnings. Resolve any errors or warnings in 10g files and resolve them manually in the upgraded 11g RPDs and Web Catalogs.Refer to Post-Upgrade Tasks and Considerations for Oracle Business Intelligence Publisher for a description of the post-upgrade tasks you might need to perform for each of the Oracle Business Intelligence Publisher components.
To verify that your Oracle Business Intelligence Publisher upgrade was successful see Section 4.8, "Task 8: Verify the Oracle Business Intelligence Enterprise Edition Upgrade."