NOTICE: Support of BI Applications 11g with OBIEE

12.2.1(12C)

Purpose
The information contained in this document applies to customers who are planning to
use/upgrade Oracle Business Intelligence Applications 11g with Oracle Business
Intelligence Enterprise Edition 12.2.1.0 it discusses about the Possible Out Place
Upgrade for running OBIA 11g with OBIEE 12c.

Applies to
Business Intelligence Applications Consumer - Version 11.1.1.9.2, 11.1.1.10.1 and
11.1.1.10.2 [Release 11g]
Information in this document applies to any platform.

Note: This Out Place Upgrade is not Applicable to Business Intelligence Applications 11g
customers with Fusion Apps as the Source Application (Direct ETL).

Support of BI Applications 11g with OBIEE 12c Page 1

What is Dual-Headed Deployment or Out Place Upgrade?

Scenario:

1 DEV Machine (A): BI Apps11g Installed with OBIEE 11.1.1.x and ODI 11.1.1.x.

2 DEV Machine (B): OBIEE 12.2.1 (12c) installed.

3 Customer moves the BI Apps artifacts (I.e. RPD, Webcat, and JZAN-security) from
Machine (A) using the BI Migration Tool (bi-migration-tool.jar) and then importing it in
to the 12c system Machine (B)

Pre-Requisites
Oracle BI Applications 11.1.1.9.2 or 11.1.1.10.1 with Oracle BI EE 11.1.1.7 or later on
Machine (A)
Ensure your Oracle BI EE 11.1.1.7 or later Catalog on Machine (A) Is Upgraded to the
Correct Version of Please refer (Doc ID 2068965.1) for details.
Customer should have installed Oracle Fusion Middleware Infrastructure (Weblogic)
on Machine (B)

Support of BI Applications 11g with OBIEE 12c Page 2

 Before you install Fusion Middleware (Weblogic), you also need to download and
install JDK 8 on Machine (B),

Note: Java Developers Kit 8 (JDK8) is supported for all platforms.

Steps to Install OBIEE 12c (OBIEE Software install):

To start the installer simply run the file expanded from the first zip file, in my case
bi_platform-12.2.1.0.0_linux64.bin on Machine (B) , this will be different for each OS.

The next screen asks about auto updating patches, to automatically search My Oracle
Support for available patches or automatically search a local directory for patches
that youve already downloaded for your organization.
Next we need to specify the home for this installation. This needs to be the same
home as the Fusion Middleware installed.

Support of BI Applications 11g with OBIEE 12c Page 3

 Use this screen to select the type of installation and consequently, the products and
feature sets you want to install.

For this topology, select BI Platform Distribution with Samples. Click Next

Support of BI Applications 11g with OBIEE 12c Page 4

 This screen verifies that your system meets the minimum necessary requirements.

If there are any warning or error messages, refer to the Oracle Fusion Middleware
System Requirements and Specifications document on the Oracle Technology
Network.

Use next screen to verify the installation options you selected. If you want to save
these options to a response file, click Save Response File and provide the location and
name of the response file. Response files can be used later in a silent installation
situation.
For more information about silent or command line installation, see "Using the Oracle
Universal Installer in Silent Mode" in Installing Software with the Oracle Universal
Installer.

Support of BI Applications 11g with OBIEE 12c Page 5

 This screen shows the installation progress.

Support of BI Applications 11g with OBIEE 12c Page 6

 This screen appears when the installation is complete. Review the information on this
screen, then click Finish to dismiss the installer.

Support of BI Applications 11g with OBIEE 12c Page 7

Installing OBIEE 12c Creating the Repositories:

To start the RCU run the rcu (or rcu.bat for windows) from the
<obiee_home>/oracle_common/bin directory:

Use this screen to select the action you want to perform Create Repository or Drop
Repository

Support of BI Applications 11g with OBIEE 12c Page 8

 Use this screen to specify the connection credentials to the database in which you
will be creating or dropping your schemas. Select one of the following depending on
your database:

Some prerequisite checks will then be performed, essentially just checking that the
database is connecting correctly.

Support of BI Applications 11g with OBIEE 12c Page 9

 Use this screen you need to specify a prefix for the schemas. The default is DEV, but
you may change this to something more meaningful.

Note: Incase if youre using the same database where the OBIEE 11g repository schema
resides, then use a different schema prefix for OBIEE 12c.

Support of BI Applications 11g with OBIEE 12c Page 10

 The RCU will them perform some more prerequisite checks to ensure it can
continue

Next you need to specify passwords for these schemas. You can either set the same
single password for all schemas or specify different passwords for each schema.

Support of BI Applications 11g with OBIEE 12c Page 11

 Use this screen to choose which tablespaces you want the schemas created in. By
default the RCU will create a new set of tablespaces with the same prefix as the
schemas. These tablespaces will be created in the next step unless changed here.

Support of BI Applications 11g with OBIEE 12c Page 12

 Review the information on the Summary screen, and click Create to begin schema
creation. The operations summarized on this page will be performed when you click
Create.

While the schemas are being created, you will see the following progress screen:

This screen contains information about the log files that were created from this RCU
operation. You can click on the name of a particular log file to view the contents of
that file.

If there were any problems encountered during schema creation, you can
troubleshoot the issue using the log files. For more information, refer to RCU Log
Files.

If errors are encountered during a Create operation, or if a Create operation fails for
any component, the Cleanup for failed components checkbox appears on this page
and is selected by default. If selected, RCU will perform cleanup operations for the
component that failed during the Create operation. If you choose not to select this
checkbox, you can cleanup the failed component at a later time by performing a Drop
operation for the failed component(s).

Review the information on this screen, then click Close to dismiss this screen.

Support of BI Applications 11g with OBIEE 12c Page 13

 Look in the database lets to see the schemas that have been created:

So far we just completed the OBIEE 12c software installed as per the instructions in
Installing Oracle Business Intelligence and created Oracle Fusion Middleware schemas as
per the instructions in Creating Schemas with the Repository Creation Utility.

Support of BI Applications 11g with OBIEE 12c Page 14

Migrating BI Apps Artifacts from Oracle BI 11g to BIEE 12c
Copy the BI Migration Tool (bi-migration tool jar) from (Machine B) to the host
(Machine A) OBIA 11g system from where you want to export data.

<12cInstall>/bi/migration-tool/jlib/bi-migration-tool.jar

Run the BI Migration Tool without passing parameters. Enter the following command:

java -jar bi-migration-tool.jar out <11g Oracle Home> <11g Domain Home>
<Output Bundle File>

Linux Command:

Example: JAVA_HOME/java -jar /scratch/snkoya/work/BI_12cMigration/bi-migration-tool.jar

out /scratch/snkoya/work/mw1507/Oracle_BI1
/scratch/snkoya/work/mw1507/user_projects/domains/bifoundation_domain
/scratch/snkoya/work/BI_12cMigration/export_copy/export.jar

Windows Command:

JAVA_HOME\java -jar C:\Users\snkoya\Downloads\bi-migration-tool.jar out C:\OBIEE\Oracle_BI1

C:\OBIEE\user_projects\domains\bifoundation_domain C:\Users\snkoya\Downloads\export_BI.jar

Note: Make sure to replace these file paths with the respective paths on your
system.

Support of BI Applications 11g with OBIEE 12c Page 15

 The screen message indicates a successful export: Export succeeded

Copy over the 11g BI Export Bundle.jar file from Machine (A) to 12c Machine (B).

Importing the Export Bundle Using the BI 12c Configuration Assistant cd

Oracle_home\bi\bin

Support of BI Applications 11g with OBIEE 12c Page 16

 The Configuration Assistant starts and the Welcome screen is displayed.

Support of BI Applications 11g with OBIEE 12c Page 17

 On the Prerequisite Checks screen, after the prerequisite checks conclude with no
errors, click Next.

On the Define New Domain screen, specify the following, and click Next

Support of BI Applications 11g with OBIEE 12c Page 18

 On the Database Schema screen, choose either to create a new schema or use an
existing schema by clicking the appropriate option.

Support of BI Applications 11g with OBIEE 12c Page 19

 On the Port Range screen, specify the port range and click Next.

On the Initial Application screen, choose the following option:

o Your own existing BI Application from export bundle (.jar).

When you select this option, you are prompted with a dialog box to select the export
bundle that you created previously from the 11g environment.

Support of BI Applications 11g with OBIEE 12c Page 20

 Browse and select the export bundle and enter the BI RPD password for .Jar file then
click Next

On the Summary screen, verify the values you specified on each screen. Click Save to
generate a response file used for silent installation (optional).

Click Configure.

After the configuration concludes without any errors, click Next to go to the
Configuration Complete screen.

On the Configuration Complete screen, review the configuration summary.

Support of BI Applications 11g with OBIEE 12c Page 21

 Click Save to save the information on this screen in a file.

Click Finish to exit the Configuration Assistant.

Support of BI Applications 11g with OBIEE 12c Page 22

 Once you get the 12.2.1 system configured please set the compatibility flag in BI
Server NQSConfig.ini file. In the end of the file please add for example:

[COMPATIBILITY]
COMPATIBLE_RELEASE=11.1.1.9;

And restart the OBIEE 12c BI Services.

NQS Config.INI File Locations:

Windows:
ORACLE_HOME\user_projects\domains\bi\config\fmwconfig\biconfig\OBIS
Unix:

Support of BI Applications 11g with OBIEE 12c Page 23

 /ORACLE_HOME/user_projects/domains/bi12/config/fmwconfig/biconfig/OBIS

The BI Application opens in the browser. Use the login credentials you specified while
configuring to log in to the BI application home.

A Known BI Applications 11g Issues with OBIEE 12c

BI Applications 11g SCM: DSO and AR Balance Trend Are Displayed Differently in 12c
BI Applications 11g View Display Error: Invalid Column Encountered in Orders
Outstanding Report
For all other known differences please refer section Known Differences: Oracle
Business Intelligence 12c

Summary:
OBIA 11.1.1.9.2 and 11.1.1.10.1 is certified for use with OBIEE 12c however ODI 11g
will need to be in its own ORACLE_HOME different Machine from OBIEE 12c ORACLE_HOME
until ODI 12c is certified with OBIA.

FAQs:

Support of BI Applications 11g with OBIEE 12c Page 24

This document talks of how to use OBIEE12c instead of OBIEE 11g. None of the
other components change. So BIACM will remain on the node with OBIEE11g itself.

1. How can we access the BIAPPS configuration manager i.e. BIACM?

BIACM will continue to be accessed from the original node on which BIAPPS in
installed which will be on 11g. BIACM will NOT be moved to the OBIEE 12c node as
that is meant only for OBIEE and no other component.

2. How can we configure BIAPPS offerings (financials) and load plans? There is no
mention of the BIACM URL in the document sent.
Same as earlier, Use BIACM URL from the original node. That does not change.

3. Do we have to use both the weblogic instances in order to maintain OBIEE12c

and BIAPPS 11.1.1.10.2?
Weblogic server will need to run on both instances. Weblogic on OBIEE12c is used
by BI Server on that node.

4. Can we have two weblogics in the same machine for OBIEE 12c and BIAPPS
11.1.1.10.2(weblogic 11 and weblogic 12)?
Please check the Weblogic documentation to see if that is supported. The document
talks of a dual head approach only.

5. Is it possible to run BIAPPS 11.1.1.10.2 rcu pointing to OBIEE12c weblogic server?

Only OBIEE is being moved to the second node and nothing else changes. So RCU
will have to be run pointing to the original instance unless stated otherwise in the
document for any particular step. It is as though you first complete your current
BIAPPS installation, then install the second OBIEE12c and move the RPD/Webcat etc
over to the new node.

6. We have not configured security provider yet for the BI Apps, do we still have to
migrate the security jazn file?
We have migrated 11g OBIEE to 12c and it migrates RPD, System Jazn and Webcat.
Yes, customer has to migrate System Jazn.

Support of BI Applications 11g with OBIEE 12c Page 25