upgrading oracle business intelligence from 10g to 11g

7/28/2019 Upgrading Oracle Business Intelligence From 10g to 11g

1/82

Upgr adingOracleBusinessIntelligencefrom 10gt o11g

1/82m/webfolder/technetwork/t utorials/obe/fm w/bi/bi11115/upgrade/upgrade_to_11g.htm?

Upgrading Oracle Business Intelligence from 10gto 11g

This tutorial contains the following sections:

Purpose

Time to Complete

OverviewPrerequisites

Installing the Sample Sales Data Set

Upgrading the Oracle BI Repository and Catalog

Verifying the Upgrade

Incorporating Changes to 11gRepos itory Metadata

Exploring Default Securi ty Settings for Oracle BI 11g

Applying New 11gRepos itory Metadata Features

Using Fusion Middleware Control in 11g

Applying New 11gPresentation Features

Upgrading Oracle BI Publisher Reposi tory

Post Upgrade Considerations for BI Publisher 11g

Summary

Resources

Credits

Purpose

This tutorial covers using Oracle Fusion Middleware Upgrade Ass istant to upgrade an existing Oracle Business Intelligence 10g

environment to an 11genvironment.

Time to Complete

Approximately 1 hour.

Overview

This tutorial provides step-by-step procedures for using Oracle Fusion Middleware Upgrade Assistant to upgrade an existing Oracle

Business Intelligence (BI) Enterprise Edition 10gRelease 3 (10.1.3.2 or later) environment to Oracle Business Intelligence Enterprise

Edition 11gin a Windows environment on a single machine. You learn how to upgrade the OBI repository and presentation catalog, as

well as the Oracle BI Publisher (BI Publisher) repository. This tutorial uses the 10gversion of the Sample Sales application to

demonstrate the upgrade process, and also covers a subset of 11gfeatures and functions that you should consider applying as part of a

post-upgrade configuration.

Prerequisites

Before starting this tutorial, you should:

Have access to or have installed Oracle Busines s Intelligence Enterprise Edition 11g

Have access to the Sample Sales repos itory and Web catalog metadata, designed for Oracle Business Intelligence EnterpriseEdition 10g. You can download this sample data set from here or from the Oracle Technology Network (OTN). This tutorial shows you

how to upgrade this s ample data set from 10gto 11g.

Have downloaded the BIP10gRepository.zip file to your local hard drive, unzipped, and copied the files to your local hard drive. In

this example, the files are extracted to D:\Repository.

Installing the Sample Sales Data Set

In this set of steps, you download and unzip the Sample Sales data set on the server on which Oracle Busines s Intelligence Enterprise

Edition 11gis installed. To install the Sample Sales data set, perform the following steps:

1. As des cribed in the Prerequisites section, download the 10gSample Sales data set files

(oracle_bi_sample_analysis_setup_files.zip) from here or from the Oracle Technology Network (OTN) to

a directory on a server on which Oracle BI 11gis installed. In this example, the zip file is downloaded to
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s7http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t9http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t5http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t1http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s3http://www.oracle.com/technetwork/index.htmlhttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/files/oracle_bi_sample_analysis_setup_files.ziphttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/files/BIP10gRepository.ziphttp://www.oracle.com/technetwork/index.htmlhttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/files/oracle_bi_sample_analysis_setup_files.ziphttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s9http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s8http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s7http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s11http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t9http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t8http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t7http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t6http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t5http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t1http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s6http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#s1


2/82



D:\SampleSales.

2. Unzip the Sample Sales data set. You should see four new files:

Sample_Sales_V1.3_Dataset.zip

Sample_Sales_V1.3_Readme.txt

Sample_Sales_V1.3_Webcat.zip

samplesales.rpd

3. ExtractSample_Sales_V1.3 Webcat.zip to a subfolder in D:\SampleSales. In this example, the zip file is

extracted to D:\SampleSales\Sample_Sales_V1.3_Webcat\samplesales. This folder now contains the

Sample Sales 10gpresentation catalog.

4. Create a new directory named deliveries in D:\SampleSales\Sample_Sales_V1.3_Webcat. In 10g, the

deliveries directory is a special directory used for data such as Dashboard snapshots us ed by Briefing Books.

The directory is called deliveries by default and is located in the OracleBIData\web\catalogdirectory. In manycases, the 10gdirectory is empty. If the 10gdeliveries directory is not available, any empty directory named

deliveries can be given for upgrade. If Upgrade Assistant finds a directory called deliveries in the same folder as

the catalog, it is s elected by default.


3/82



5. Sample_Sales_V1.3_Dataset.zipcontains a sample set of data in XML format for display in Oracle BI

dashboards. To make this data available for queries, extract Sample_Sales_V1.3_Dataset.zip to the following

location:

%MIDDLEWARE_HOME%\instances\instance1\bifoundation\OracleBIServerComponent\

coreapplication_obis1\server\Sample

The extraction will create a new directory named samplesales with a set of XML files. Please notice that you must

create the two directories s erver\Sample to maintain the relative paths for all of the XML files in the repos itory. In

this example, the data set is extracted to:

D:\bi\instances\instance\bifoundation\OracleBIServerComponent\

coreapplication_obis\server\Sample\samplesales


4/82



6. samplesales.rpd is the Sample Sales 10gBI repository. You can leave this file in D:\SampleSales.

You are now ready to begin the upgrade process for the Sample Sales data set.

Upgrading the Oracle BI Repository and Catalog

To upgrade the Sample Sales repos itory and presentation catalog, perform the following steps by using the Upgrade Assistant. Please

note that the WebLogic Adminis tration Server and the Managed Server in the 11genvironment must remain running during the upgrade

process.

1. Navigate to the ORACLE_HOME\bindirectory of the Oracle Fusion Middleware installation. In this example, the

directory path is D:\bi\Oracle_BI1\bin.


5/82

UpgradingOracleBusinessIntelligencefrom 10gt o11g


2. Double-click ua.bat to open Upgrade Ass istant in the graphical user interface mode. This tutorial describes how

to use Upgrade Assis tant in the graphical user interface mode. You can also use the Upgrade Assis tant

command line to perform these tasks. For more information, see "Using the Upgrade Ass istant Command-Line

Interface" in Oracle Fusion Middleware Upgrade Planning Guide.

3. On the Welcome screen, click Next.


6/82



4. On the Specify Operation screen, select Upgrade Oracle BI RPD and Presentation Catalog and click Next.

5. On the Specify Source Details screen, select Upgrade Repository (RPD).


7/82



6. Click Browse next to the RPD File field.

7. Browse to the location of the 10gversion of the Sample Sales repos itory and click Open. In this example, the path

is D:\SampleSales\samplesales.rpd.


8/82



8. The path to samplesales.rpd is added to the RPD File field.


9/82



9. Enter the Administrator User Name and Administrator Password for the 10gsamplesales repository. In this

example, the username and password are both Administrator.


10/82



10. Enter and confirm a password that will be used to secure the upgraded 11grepository. This pass word is required

for 11grepositories. It does not have to match the 10grepository password or any other pass word. In this

example, the password is welcome1.

11. Select Upgrade Catalog.


11/82



12. Click Browse next to the Catalog Directory field.

13. Browse to the location of the 10gversion of the Sample Sales presentation catalog and click Open. In this

example the path is D:\SampleSales\Sample_Sales_V1.3_Webcat\samplesales.


12/82



14. The path to the Sample Sales presentation catalog is added to the Catalog Directory field. The path to the

deliveries directory is automatically added to the Catalog Deliveries Directory field.


13/82



15. Click Next to continue.

16. On the Specify WebLogic Server screen, enter the WebLogic Admin Server port number. Typically the port

number is 7001.


14/82



17. Enter the username and password for the WebLogic Admin Server. In this example, it is weblogic/welcome1 .


15/82




19. On the Examining Components s creen, wait until you see a succeededmessage. During the examination

process, Upgrade Assistant checks whether the source directory exists, the source directory is readable, and

contains a file for upgrade.


21. On the Upgrade Summary screen, review the summary of the upgrade to be performed.


16/82



22. Click Upgrade to start the upgrade process .

23. On the Upgrading Components s creen, you can view the upgrade progress. BI components are s topped and

restarted. The Sample Sales presentation catalog and repository are loaded.

24. When the upgrade completes the status changes to succeeded. If there are errors during the upgrade, inspect the

log files for details. The log files are located in \upgrade\logs\ua.log whereis the current date and time. You can also check the component log files in directories organized by

component under\diagnostics\logs.


17/82




26. On the Upgrade Success screen, review information related to the upgrade task and click Close.


18/82



Verifying the Upgrade

The Upgrade Assistant automatically loads the new repository to the 11 gBI Server and res tarts all BI components . You can verify that

Oracle BI EE has been upgraded successfully by logging into the 11gsystem to confirm that Oracle BI EE components are running,

checking repos itory metadata, and verifying that you are able to view das hboards and reports. To verify the upgrade, perform the following

steps:

Verifying Oracle BI system components

Verifying repository metadata

Verifying reports and dashboards

Verifying Oracle BI System Components

Verifying Repos itory Metadata

Verifying Reports and Dashboards

Verifying Oracle BI System Components

1. In a browser, enterhttp://localhost:7001/em to log into Fusion Middleware Control on the 11gsystem.

2. In the left pane, expand Business Intelligence > coreapplication.

3. In the right pane, select the Overview page and confirm that all system components are available.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s1http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3s1


19/82



4. Select the Deployment page.

5. Select the Repository subtab. This page shows the current installed repository. Notice that the Upgrade

Ass istance automatically uploaded the upgraded repos itory to the BI Server domain. In this example, therepository is nam ed as samplesales_BI0002.

Verifying Repository Metadata

1. Select Start > Programs > Oracle Business Intelligence > BI Administration to open the Administration Tool.

2. Select File > Open > Online to open the repository in online mode.

3. Enter the repository password and user password. The repository password is the password that you identified

earlier during the upgrade process : welcome1. The username and password are the Oracle WebLogic Server

adminis tration username and password created during your 11ginstallation. In this example, the user is

weblogic.


20/82



4. Click Open to open the upgraded repository in online mode.

5. In the Physical layer, expand A - Sample Sales (XML).


21/82



6. Double-click Connection Pool A.

7. ClickYes to check out the object.


22/82



8. The Connection Pool A dialog box opens. Notice the data source name field. This points to the location where

Sample Sales XML files are stored. The data source name includes a variable (BI_EE_HOME) and the path to the

directory where the files are stored. Recall that earlier in this tutorial you unzipped the Sample Sales XML data files

to the ...\server\Sample\samplesalesdirectory on the 11gserver. In the steps that follow, you modify the

BI_EE_HOMEvariable to point to the correct directory.

9. Click OK to close the Connection Pool dialog box.

10. Select Manage > Variables to open Variable Manager.


23/82



11. In the right pane, double-click the BI_EE_HOME variable.

12. ClickYes to check out the object.

13. In the Static Repository Variable dialog box, change the Default Initializer to the XML data source path (without the

additional directories). In the example shown below, you set the variable initializer to

D:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1

.


24/82



14. Click OK to close the Static Repos itory Variable dialog box.

15. Select Action > Close to close Variable Manager.

16. Check in the changes.

17. Save the repository. (There is no need to check cons istency at this point.)

18. Close the repository.

19. Click OK when you receive the message about manually restarting each non-master Oracle BI Server instance in

the cluster.

20. Close the Adminis tration Tool.


25/82



Verifying Reports and Dashboards

1. Sign in to Oracle BI 11gas an adminis trative user. In this example the user is weblogic. Your username and

password will vary depending on how you have installed and configured your environment.

2. Click the Administration link.

3. On the Administration page, in the Maintenance and Troubleshooting section, click Reload Files and Metadata.

4. Click the Home link.

5. From the Home page, select Analysis > Samples Sales to open the Analysis Editor.


26/82



6. Create and run an analysis to test your metadata and data.

7. Open and view dashboards.


27/82



8. Sign out of Oracle BI.

Congratulations! You have upgraded the Sample Sales data set from 10gto 11gand verified that the upgraded

Oracle BI system components, repository, and presentation catalog are working as expected.

Incorporating Changes to 11g Repository Metadata

After upgrade, there are a number of differences between the 10gand 11genvironments related to Oracle BI repository metadata. This

tutorial covers only a small subset of the differences you should address post-upgrade. Specifically, this topic discusses:

Incorporating enhanced repository consistency checkingIncorporating repository modeling changes

Incorporating changes to the repository security model

For additional information about repository metadata upgrade considerations, refer to Oracle Fusion Middleware Upgrade Guide for

Oracle Business Intelligence 11gand Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence

11g.

Incorporating Enhanced Repository Consistency Checking

Incorporating Repository Modeling Changes

Incorporating Changes to the Repository Security Model

Incorporating Enhanced Repository Consistency Checking

In 11g, the Consistency Check Manager now enforces additional validation rules to help ensure that your repository is consistent. In

addition, some rules that existed in previous releases might now be displayed during consis tency checks. After upgrading from a

previous software version and checking the consistency of your repository, you might notice messages that you had not received in

previous consistency checks. This typically indicates inconsistencies that had been undetected before the upgrade, not new errors. As a

result, it is likely that you will s ee error and warning mes sages that you did not see in 10g.

For example, in 10g, there were several modeling constructs allowed by the consistency checker that resulted in unexpected query

behavior at runtime, or inconsistencies at multi-user development (MUD) checkout time. In 11g, the Consis tency Check Manager

addresses these issues by enforcing additional validation rules to help ensure that the repository is consis tent. In addition, some rules

that existed in previous releases might now be displayed during consis tency checks.

The steps that follow provide only a few examples of 11gconsis tency check errors and warnings that should be addressed. For more

information, please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise

Edition 11gand Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s1http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s3http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t4s1


28/82



1. Select Start > Programs > Oracle Business Intelligence > BI Administration to open the Administration Tool.

2. Select File > Open > Online to open the repository in online mode.

3. Enter the repository password (welcome1) and user password.

4. Click Open to open the upgraded repository in online mode.

5. Select File > Check Global Consistency.

6. Consistency Check Manager opens. Notice that there are consistency check errors and warnings.

Error 38123 indicates that the initialization block test1 is not associated with the system variable USER.

Warning 39054 indicates that the aggregation content filter "Group by Level" in the logical table source of a fact

table references logical dimension tables that are not joined to that fact table. If that fact table is extracted in the

extract/MUD process, the dimensions that are not joined will not be extracted. In this case, the aggregation content

of the extracted logical table source would not be the same as in the original logical table source.

Warning 39051 indicates that there is a BI Administrators application role that is defined in the repository, but not

defined in Fusion Middleware Control Enterprise Manager. You learn more about addressing this warning in the

subtopic on 11gsecurity.


29/82



7. Minimize Consistency Check Manager.

8. To address error 38123, select Manage > Variables to open Variable Manager.

9. In the left pane, select Session > Initialization Blocks.

10. In the right pane right-click the test1 initialization block and select Delete.

11. Click Check Out.


30/82



12. ClickYes to confirm the delete.

13. Select Action > Close to close Variable Manager.

14. Restore Consistency Check Manager.

15. Click Check All Objects.

16. Confirm that error38123 no longer appears in Cons istency Check Manager.


31/82




18. Leave the repository open in online mode for the next subtopic.

Incorporating Repository Modeling Changes

The Physical and Business Model Diagrams have enhanced capabilities in the 11grelease, including an im proved look-and-feel, the

ability to display columns in table objects in the diagram, and new diagram options like auto-layout, marquee zoom, and zoom to fit.

There are a few additional changes you should be aware of:

Joins in the Physical and Business Model Diagrams are represented by a line with an arrow at the "one" end of the join, rather than

the line with crows feet at the "many" end of the join that was us ed in previous releases.

When creating joins in the Physical and Business Model Diagrams, you now select the "many" end of the join first, and then select

the "one" end of the join. In previous releases, joins in the diagrams were created by selecting the "one" end of the join first.

In the steps for this topic, you address the consistency check warning 39054 related to logical joins. In the process, you explore some of

the 11gchanges to the modeling diagrams .

For more information related to using the Physical and Busines s Model layer diagrams, please refer to Oracle Fusion Middleware

Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11gand Oracle Fusion Middleware Upgrade

Guide for Oracle Business Intelligence 11g.

1. To address warning 39054, use Ctrl + click to select the following tables in the Business Model and Mapping

layer:

D1 Customer

D3 Order

D5 Employee

F1 Inv Base Measures


32/82



2. Right-click any one of the four highlighted tables and select Business Model Diagram > Selected Tables Only to

open the Busines s Model Diagram.

3. In the diagram toolbar, click the Fit icon or use the Zoom icons to adjust the diagram so that all four objects are

visible.


33/82



4. To create logical joins, select the New Join button on the toolbar.

5. Click the F1 Inv Base Measures table first and then click the D5 Employee table to open the Logical Join dialog

box. Again, when creating joins in the Physical and Business Model Diagrams, you now select the "many" end ofthe join first, and then select the "one" end of the join. In previous releases, joins in the diagrams were created by

selecting the "one" end of the join first.

6. Click OK to close the Logical Join dialog box.


34/82



7. Click Check Out.

8. The logical join is created between F1 Inv Base Measures and D5 Employee.

9. Repeat the steps to create joins between F1 Inv Base Measures and D1 Customer, and F1 Inv Base Measures

and D3 Order.


35/82



10. Close the Business Model Diagram.



13. Verify that the 39054 warnings are no longer visible.


15. Leave the repository open in online mode for the next subtopic.


36/82



Incorporating Changes to the Repository Security Model

There are changes in the Oracle BI 11grepos itory related to security:

As dis cuss ed earlier in this tutorial, repositories now have repository-specific pass words that are used to encrypt the repository contents.

The repository password is stored in an external credential store when you publish a repository in Fusion Middleware Control,so that the

Oracle BI Server can retrieve the password to load the repository.

Groups no longer exist in the repository as objects. Instead, you implement data access security based on the application roles to which

a user belongs. Application roles are managed in an external policy store. Application role objects exist in the repository, but these

objects are pointers (references) to the externally managed roles.

Users are managed in an external identity store and are no longer managed in the repository. User objects exist in the repository, but

these objects are pointers (references) to the externally managed users.

In the steps for this topic you address the consistency check warning 39051 related to application roles. In the process, you explore

some of the 11gchanges to the Oracle BI repository security model.

This tutorial covers only a small subset of the changes related to security in Oracle BI 11 g. For more information related to security,

please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g

and Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

1. To address warning 39051, select Manage > Identity to open Identity Manager.

2. In the left pane, expand Identify Managerand select BI Repository.

3. In the right pane, select the Users tab.

In Oracle Business Intelligence Release 10g, users and groups could be defined within a repos itory file by using

the Oracle BI Administration Tool. In Oracle Business Intelligence Release 11g, users and groups can no longer

be defined within a repository. The Oracle Business Intelligence Enterprise Edition Upgrade Assis tant migrates

users and groups from a Release 10grepository into the embedded LDAP server in a Release 11ginstallation.

4. Notice theAdministratoruser.

In an Oracle Business Intelligence Release 10ginstallation, a special user namedAdministratorhas full

adminis trative permissions and is als o used to establish trust between processes within that installation. In

Oracle Business Intelligence Release 11g, there is no special significance to the name Adminis trator and there

can be one or more users who are authorized to undertake different sets of administrative functions. In Oracle

Business Intelligence Release 11g, the identity used to establish trust between processes in an ins tallation is

configurable and independent.

5. Notice the demo2and demo users. These are additional users from the 10gSample Sales repository.


37/82



6. Select Action > Set Online User Filter.

7. Enter an asterisk (*) in the field and click OK.

8. Notice that the Users tab is now populated with all of the users defined in the WebLogic security realm, including

the weblogicadministrative user. Your results will vary depending on which users you have defined in your 11 g

environment. For example, the usersAdministrator_fandAdministrator_dare unique to the environment used to

build this tutorial. You explore this security realm in more detail later in this tutorial.

9. Click the Application Roles tab.


38/82



In Oracle Business Intelligence 10g, security policies in the Oracle BI Presentation Catalog and repository could

be defined to reference groups within a directory. In Oracle Business Intelligence 11g, a level of indirection is

introduced whereby security policies are defined in terms of application roles, which are in turn are as signed to

users and groups in a directory. This indirection allows an Oracle Business Intelligence 11gsystem to be

deployed without changes to the corporate directory and eases movement of artifacts between development, test,

and production environments.

10. Notice the application roles beginning withXMLP. These are security groups that were defined in the 10gSample

Sales repos itory. They are automatically converted to application roles in the 11genvironment.

11. Notice also the following application roles:

BIConsumer

BIAuthor

BIAdministrator

Oracle BI 11gprovides this s et of application roles as part of the default security realm.

12. BIAdminis trators, however, is not a default application role, which is why you received the consistency check

warning 39051. To remove the warning, right-click BIAdministrators and select Delete.


39/82



13. Click Check Out.

14. ClickYes to confirm the delete.

15. Select Action > Close to close Identity Manager.



18. Verify that the 39051 warning is no longer visible.

19. Close Consistency Check Manager.

20. Check in the changes.

21. ClickYes to check global consistency.

22. You should receive a message that consistency check did not find any errors, warnings, or best practice

violations.


40/82



23. Click OK.

24. Save the repository.

25. Select File > Copy As and save a copy of the repository with the file name samplesales.rpd. You will use this

copy later in this tutorial.


27. Click OK.

28. Leave the Administration Tool open .


41/82



Exploring Default Security Settings for Oracle BI 11g

There are changes to how security is managed in Oracle BI 11 g. Security is now managed by using WebLogic Adminis tration Console

and Fusion Middleware Control.

During installation, three Oracle Business Intelligence security controls are preconfigured with initial values to form the default security

model. The s ecurity controls include:

An embedded directory server functioning as an identity store des igned to hold all user and group definitions , required to control

authentication

A file-based policy store designed to hold the application role and permiss ion grant mappings to users and groups , required tocontrol authorization

A file-based credential store designed to hold all user and system credentials , required to control authentication or authorization

In the steps for this topic, you explore some of these default security settings.

This tutorial explores only a small subset of the security model changes for Oracle BI 11g. For more information related to upgrade

considerations for security, please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business

Intelligence Enterprise Edition 11gand Oracle Fusion Middleware Security Guide for Oracle Business Intell igence Enterprise Edition.

1. To open the WebLogic Adminis tration Console, open a browser, enter the following URL:

http://localhost:7001/console and sign in as an administrative user.

This console is used to manage users and groups for the embedded LDAP server that serves as an out-of-the-

box identity store. During installation, you are prompted for a us ername and password to use as an Oracle BI

Adminis trator. In this training environment, the Adminis trator user created during installation is weblogic. This is

an arbitrary choice and there is nothing special about the name. This user has adminis trative privileges across

the Oracle Business Intelligence 11gstack. This includes the OBI repos itory, the OBI presentation catalog, OBI

Publisher, RTD, Essbase, the identity store in WebLogic, and the Policy Store in Fusion Middleware.

2. On the left side of the console, under Domain Structure, notice that there is a s ingle WebLogic domain namedbifoundation_domain into which all the OBI applications are deployed.


42/82



3. Click Security Realms.

4. Notice in the right pane that there is a s ingle default security realm named myrealm .

The OBI installer installs a single domain with a single security realm in it. A security realm is a container for the


43/82



mechanisms that are used to protect WebLogic resources. This includes users, groups, security roles, security

policies, and security providers. Although multiple security realms can be defined for the OBI domain, only one can

be active, meaning designated as the default realm, at any given time.

5. Click myrealm to view the default security settings .

6. Click the Providers tab.

7. Notice that there is a default WebLogic Authentication Provider.

An authentication provider establishes the identity of users and system proces ses , transmits identity information,

and serves as a repository for identity information from which components can retrieve it. Oracle Business

Intelligence is configured to use the directory server embedded in Oracle WebLogic Server as the default security

provider. Alternate security providers can be used if desired and managed in the Oracle WebLogic Administration

Console, but the WebLogic authentication provider is used by default.


44/82



8. Click the Users and Groups tab.

9. Click the Users subtab.

The default identity store is pre-seeded with usernames specific to Oracle Busines s Intelligence. These default

usernames are provided as a convenience so that you can begin us ing the Oracle Business Intelligence software

immediately after installation but you are not required to maintain the default names in your deployment. The three

default users are BISystemUser, OracleSystemUser, and an administrative user created during Oracle BI

installation ("weblogic" in this example). Notice that the other users here match the users you saw in the

repository after running Set Online User Filter. Some of these other users are from the 10 grepository and were

created by the Upgrade Assistant (for example, demo and demo2), and some are from the 11genvironment used

to build this tutorial (for example,Administrator_fandAdministrator_d).

10. Notice the weblogicuser. This is the adminis trative user created during the installation process. A single

administrative user is shared by Oracle Business Intelligence and Oracle WebLogic Server. As stated earlier, this

username is created during ins tallation, can be any desired name, and therefore does not need to be

Adminis trator. The password is likewise provided during installation.

In the default security configuration, an adminis trative user is a member of the BIAdminis trators group and has all

rights granted to the Oracle Business Intelligence Administrator user in earlier releases , with the exception of

impersonation. An administrative user cannot impersonate other users. An adminis trative user is also a member

of the Oracle WebLogic Server default Administrators group, which enables this user to perform all its

administration tasks, including the ability to manage Oracle WebLogic Servers embedded directory server and

policy store.


45/82



11. Notice the BISystemUseruser. Oracle Busines s Intelligence system components es tablish a connection to each

other as BISystemUs er instead of as the Adminis trator user, the latter being the practice in earlier releases. Using

a trusted system account, such as BISystemUs er, to secure comm unication between Oracle BI components

enables you to change the password of your deployments system administrator account without affecting

communication between these components. The name of this us er is the default, and it can be changed or a

different user can be created for the purpose of inter-process communication. This is a highly privileged user

whose credentials s hould be protected from non-adminis trative users .

12. Click the Groups subtab.

Groups are logical ordered sets of users. Creating groups of users who have similar system resource access

needs enables easier s ecurity management. Managing a group is more efficient than managing a large number

of users individually. Oracle recommends that you organize your users into groups for easier maintenance. As you

will s ee later in this practice, groups are then mapped to application roles in order to grant rights.


46/82



13. Notice the three default groups specific to Oracle BI: BIAdministrators, BIAuthors, and BIConsumers. These

default groups are provided as a convenience so you can begin us ing the Oracle Business Intelligence software

immediately after installation, but you are not required to maintain the default names in your deployment.

Members of the BIAdministrators group have permis sions equivalent to those of the Adminis trator user of earlier

releases.

Members of the BIAuthors group have the permis sions necessary to create content for others to consume.

Members of the BIConsumers group have the permis sions necessary to consume content created by others.

Groups are nested in a hierarchy.

Members of the BIAdministrators group are by default members of both other groups. Members of BIAuthors are

members of BIConsumers.

14. Select Users > weblogic > Groups.

15. Notice that the weblogicuser is a member of the two adminis trator groups: Administrators and BIAdministrators.

Adminis trators is the WebLogic adminis trators group, which gives rights to adminis ter WebLogic and FMW

enterprise manager. Membership in both adminis tration groups gives this user a single unified administration

account for the entire product stack.


47/82



16. Return to the browser tab where Fusion Middleware Control is open. If it is not open, enter

http://localhost:7001/em and log in as an adminis trative user.

17. In the left pane, expand Business Intelligence.

18. Right-click coreapplication and select Security > Application Roles to navigate to the Application Roles page.

19. By default, the obi application stripe is selected and the default application roles are displayed. The groups

inherited from the 10gSample Sales repository (XMLP_*) are also dis played as application roles.


48/82



20. The default application roles are:

BIAdministrator: Grants adminis trative permis sions necessary to configure and manage the Oracle Business

Intelligence installation. Any member of the BIAdministrator group is explicitly granted this role and implicitly

granted the BIAuthor and BIConsumer roles.

BIAuthor: Grants permissions necessary to create and edit content for others to consume. Any member of the

BIAuthor group is explicitly granted this role and implicitly granted the BIConsumer role.

BIConsumer: Grants permissions necessary to consume content created by others. Any member of theBIAuthor group is explicitly granted this ro le.

BISystem: Grants the permissions necessary to impersonate other users. This role is required by Oracle

Business Intelligence system components for inter-component communication.

The default application roles are mapped to default groups in the default WebLogic LDAP. The groups are listed in

the Members column. If you moved to a different LDAP server, rather than the default WebLogic LDAP server, you

could map these roles to groups in the new LDAP server. Application roles are in the policy store, whereas groups

are in the identity store.

21. In the left pane, right-click coreapplication and select Security > Application Policies.


49/82



22. By default, the obi application stripe is selected and the default application policies are displayed.

The default file-based policy store is pre-seeded with the Oracle BI-specific permissions . All Oracle Business

Intelligence permissions are provided and you cannot create additional permiss ions. These permis sions are

granted by the default application roles in the default security configuration. The default application role hierarchy

and permission grants can be changed as needed. Also notice that these permissions are not the same as thoseused to define access to BI objects (metadata, dashboards, reports, and so on). Policy store permissions are only

used to define what BI functionality the assigned roles can access. Notice, for example, that the BIAdministrator

role has been granted the permission to manage repositories.


50/82



23. Leave Fusion Middleware Control open.

Applying New 11g Repository Metadata Features

There are new repository metadata features for 11gthat you should consider applying after an upgrade from 10g. This topic covers only

one new feature: defining presentation hierarchies and presentation levels in the Presentation layer. For more information related to new

11gmetadata features, please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence

Enterprise Edition 11gand Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition.

1. In the BI Administration Tool, select File > Open > Offline to open samplesales.rpdin offline mode. Recall that this

is the copy of the upgraded repos itory you created earlier in this tutorial. Caution: In 11g, you can no longer open

the Administration Tool by double-clicking a repository file. The resulting Administration Tool window is not

initialized to your Oracle instance, and errors will result later in your session. Instead, always use the Start menu

to open the Administration Tool, or launch the Administration Tool from the command line by using bi-init.cmd.

For more information, please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle

Business Intelligence Enterprise Edition 11g.

2. Enter the repository password (welcome1 in this tutorial) and click OK.

3. In the Busines s Model and Mapping layer, expand the Sample Sales business model and notice that logical

dimens ions already exist: H0 Time, H1 Customer, H2 Market, and so on.


51/82



4. Expand H0 Time and observe the hierarchy levels. Notice that the H0 Time logical dimension contains two

hierarchies: Fiscal YearandYear.

5. In the Presentation layer, expand Sample Sales > D0 Time and observe that there are only presentation columns.

6. Drag the H0 Time logical dimension from the Business Model and Mapping layer to the D0 Time presentationtable.

7. Notice that two presentation hierarchies are created: H0 Time - Yearand H0 Time - Fiscal Year. For logical

dimens ions that contain multiple logical hierarchies, multiple separate presentation hierarchies are created.

8. Expand the presentation hierarchies and observe that they contain the same drill paths defined in the logical

dimens ion in the Business Model and Mapping layer.


52/82



Presentation hierarchies and presentation levels provide an explicit way to expose the multidimens ional model in

Oracle BI analyses and dashboards. When presentation hierarchies and levels are defined in the Presentation

layer, roll-up information is displayed in the Analysis Editor navigation pane, providing users with important

contextual information. Most importantly, users can create hierarchy-based queries using these objects.

9. Select File > Check Global Consistency. The errors indicate that the presentation levels for the H0 Time - Fiscal

Year presentation hierarchy do not have display columns defined.


53/82




11. Expand the H0 Time - Fiscal Yearpresentation hierarchy.


54/82



12. Double-click the Fiscal Yearpresentation level to open the Presentation Level dialog box.

13. Click the Display Columns tab.


55/82



14. Click the Add button (green plus sign) to open the Browse dialog box.

15. In the left pane, select Sample Sales.

16. In the right pane, scroll, and select T45 Fscl Year.


56/82



17. Click the Select button to add the column to the Presentation Level - Fiscal Year dialog box.


57/82



18. Click OK to close the Presentation Level dialog box.

19. Repeat the steps to add dis play columns to presentation levels. (Hint:Use the Query button in the Browse dialog

box to search for the presentation columns.)

Fiscal Half: T44 Fscl Half

Fiscal Qtr: T43 Fscl Qtr

Fiscal Month: T42 Fscl Month

Fiscal Week: T41 Fscl Week


21. Click Check All Objects and confirm that there are no errors, warnings, or best practice violations.

22. Close Consistency Check Manager.

23. Save the repository. There is no need to check global consistency again.


58/82




25. Close the Adminis tration Tool.

Using Fusion Middleware Control in 11g

Many configuration settings that affect repository development, including the default published repository, are now centrally managed in

Fusion Middleware Control. You can no longer manually change these configuration settings in NQSConfig.INI.

To incorporate the changes that you made to the reposi tory in this tutorial, you must upload the modified repos itory to Oracle BI Server by

using Fusion Middleware Control. For more information related to using Fusion Middleware Control to manage BI configuration settings,

please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g

and Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

1. Return to Fusion Middleware Control, which should still be open in your browser. If it is not open, enter the following URL:

http://localhost:7001/em and sign in as an adminis trative user.

2. In the left pane, expand Business Intelligence and select coreapplication.

3. In the right pane, click the Deployment tab.

4. Click the Repository subtab.

5. Click Lock and Edit Configuration.


59/82



6. Click Close when you receive theLock and Edit Configuration Completed Successfully confirmation message.

7. In the Upload BI Server Repositorysection, click Browse to open the dialog box.

8. By default, the dialog box should open to the default repos itory directory. If not, browse to

D:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository.

9. Select samplesales.rpd and click Open. You can als o double-click the repository to open it.

10. Enterwelcome1 in the Repository Password and Confirm Password fields.


60/82



11. Click Apply. Notice that Default RPD now displays samplesales with a new extension, for example, samplesales_BI0003.

12. Click Activate Changes.

13.Allow Activate Changes processing to complete. Click Close when you receive theActivate Changes Completed

Successfully confirmation message.

14. Click Restart to apply recent changes to navigate to the Overview page.

15. On the Overview page, cl ick Restart.


61/82



16. ClickYes when you receive theAre you sure you want to restart all BI components?message.

17.Allow the Restart All In Progress processing to complete.

18. Click Close when you receive theRestart All Completed Success fully confirmation message.


62/82



19. Confirm that System Components = 100%. The samples ales repository is now loaded into BI Server.

Applying New 11g Presentation Features

There are many new 11gpresentation features for Oracle BI users that you should considering applying after an upgrade from 10g. This

topic covers only one new feature: using hierarchical columns in an analysis .

A hierarchical column holds data values that are organized using both named levels and parent-child relationships. This column isdisplayed using a tree-like s tructure. Individual members are shown in an outline manner. Hierarchies allow you to drill deeper into the

data, to view more detailed information.

A hierarchical column can be one of the following kinds :

Level-based hierarchy: Consists of an ordered set of two or more levels. For example, a Time hierarchy might have three levels for

Year, Quarter, and Month. Level-based hierarchies can also contain parent-child relationships.

Parent-child hierarchy: Consis ts of values that define the hierarchy in a parent-child relationship and does not contain named levels.

For example, an Employee hierarchy might have no levels, but instead have names of employees who are managed by other

employees. Employees can have titles, such as Vice President. Vice Presidents might report to other Vice Presidents and different

Vice Presidents can be at different depths in the hierarchy.

The example in this topic uses a level-based hierarchy.

For more information related to new 11gpresentation features for users , please refer to Oracle Fusion Middleware User's Guide forOracle Business Intelligence Enterprise Edition 11g.

1. Sign in to Oracle BI.

2. In the Create section, select Analysis > Samples Sales.


63/82



3. Create the following analysis by using the H0 Time - Yearpresentation hierarchy.

4. Click Results.

5. Expand the hierarchy to view data at different levels.


64/82



Upgrading Oracle BI Publisher Repository

The Upgrade Ass istant performs the following upgrades to the BI Publisher Repository:

Upgrades reports: The reports created in 10g, stored originally within a single report file (.xdo), are now spilt in 11ginto two objects

a report definition file (.xdo) and a data model file (.xdm). Click this link to view a graphic representation of these structures.

Upgrades configuration files: The Administration files, containing users and roles, data source definitions, delivery server

configurations, and so on, are copied to the new location retaining all configuration settings. If you are using the BI Publisher security

model, then all roles and permiss ions wil l become available to 11gas the Upgrade Ass istant has that detailed information available.

If you are using another security model, such as LDAP, you need to address permissions separately. Note that the default security

model is Fusion Middleware.Running the Upgrade Assistant for the BI Publisher Reposi tory

Verifying the BI Publisher Repos itory Upgrade

Running the Upgrade Assistant for the BI Publisher Repository

To begin the upgrade for BI Publisher, perform the following steps:

1 . Start the Upgrade Ass is tant as you did above in the topic titled "Upgrading the Oracle BI Repository and Catalog."

2 . The Welcome page appears. Click Next.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#ua_lochttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t9s2http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t9s1http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/files/reports_upgrade.pdf


65/82



3 . The Specify Operation page appears. Select Upgrade Oracle BI Publisher Repository, and then click Next.


66/82



4 . The Specify Source Details page appears. Two options are available for selection: the first is for the BI Publisher

Repository, while the second is for the E-Business Suite Data Template Directory.

Select the first option, and then click Browse to locate the repository that you want to upgrade. This is the location of

the 10gcatalog. If you are upgrading the E-Business Suite Data Template Directory, you browse for the data

template directoryNote however, that the Upgrade Assistant does not support reading the data definition from the

E-Business Suite environment. You need to store the data template XML files in a file system, and then run the

Upgrade Assistant to create an equivalent data model definition in the BI Publisher Enterprise Server.


67/82



5 . Navigate to the 10gcatalog and select it.For this example, the repository is located in D:\Repository.


68/82



6 . The image below provides a view of the directories containing the reports that will be upgraded:

Click Next.


69/82



7 . The Specify Destination Details page appears. Click Browse to select the location for your upgraded repository.

This can be the same repository as the installed bishiphome 11grepos itory path (for example,

%MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\bipublisher\repository)

or it can be a new path on the server. If you choose a new path, then you must copy the contents of the 11g

repos itory to this new path. The 11grepository contains required files.

If you are upgrading the E-Business Suite Data Template Directory, you browse for the data model d irectory.


70/82



8 . Click Next.

9 . The Specify WebLogic Server page appears. In this example, the Adminis tration server is running locally; therefore,

the domain information corresponds accordingly.

Enter the Host (localhost - the default), Port (7001), User Name (weblogic), and Password (welcome1) as you

previously entered in the topic titled "Upgrading the BI Repository and Catalog" and click Next.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#port_un_pswd


71/82



10

.

The Examining Components page appears. The s ystem is examined to ensure that everything is available and

correct for the upgrade to proceed. For example, the installer interrogates the system to ensure that there is enough

space. The status is succeeded.

A log file for the ses sion is available. You review the log file now or at a later time. Click the hot link for the log file

(highlighted at the bottom of the dialog box).


72/82



11.

Scroll and examine the content. When you are finished reviewing the log file, click Close.

12

.

Click Next.

13 The Upgrade Summary page appears and provides you with the details for both source and target. Click Upgrade.


73/82



.

14

.

The Upgrading Components page appears. Examine the status once again. If the s tatus is not successful, review

the log file once again to determine and res olve the iss ues.

Click Next.


74/82



15

.

The final page of the Upgrade Assistant Wizard page appears. Click Close.


75/82



Verifying the BI Publisher Repository Upgrade

To verify that the upgrade ported your reports over to 11gproperly, perform the following steps:

1 . Log in to BI Publisher and change the server configuration to point to the upgraded repository.

Open a new browser window and in the address bar, enterhttp://:7001/xmlpserver(for example,

http://localhost:7001/xmlpserver). The Oracle BI Publisher Enterprise Login window appears.


76/82



2 . Enter the Username (weblogic) and Password (welcome1), and click Sign In.

3 . The Home Page appears. Click the Administration link.


77/82



4 . Within the System Maintenance section, click Server Configuration.

5 . Click the Server Configuration tab.


78/82



6 . Enter the path for your upgraded repository into the Configuration Folder area. This is the path that you specified on

the Destination Details page in the Upgrade Assistant (for example,

%MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\bipublisher\repository).

7 . Click Apply. A confirmation message appears.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#rep_path


79/82



8 . Log out, and then log back into BI Publisher to review your changes to the repository.

9 . Click the Catalog link on the global header. Expand Shared Folders > HR Manager > HR - Userin the Folders pane.

The ported reports appear in the right pane.

10

.

Select a specific report to view. Click Open for the Form P11D-UK2004 report.

The P11D-UK2004 report appears.


80/82



You have now verified that your reports have been successfully migrated. Close BI Publisher.

Post Upgrade Considerations for BI Publisher 11g

After upgrading to BI Publis her 11g, there are a number of considerations and tasks that should be addressed. Some of these

considerations are address ed below:

Verify that the xmlp-server-config.xmlcontains the correct repository name and path to the BI Publisher repository. This file is

located in the %MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\bipublisherdirectory.

Verify that the datasources.xml file contains the correct repository name and path to the BI Publisher repository. This file is located

in the

%MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\bipublisher\repository\Admin\DataSour

directory.


81/82



Editing upgraded data models: When the 10greport data model is using a SQL Query or BI Answers as the data source type, the

data sets do not display any column information in the Data Model Editor. This occurs because these data set types (in 10g) do not

capture the necessary information to populate the columns for the new 11gmodel. These data models will continue to work,

however should you need to make any modifications , you may not be able to edit the data model (for example, you might not be able

to add a calculated column or create a l ink to other data sets).

Validation errors for upgraded data templates: The Data Model Editor in 11gintroduces res trictions on data models that were not

present in 10g. Therefore, a data template-based data model that was valid in 10g, might invoke a warning message when you try to

save it. Case sensitivity and orphan elements present two restrictions of which you should be aware.

- Case sensitivity: The 10gdata template allowed you to reference elements within the data template without regard to the case

being used. In 11gthe case must match the referenced item.

- Orphan elements: In 10git was pos sible for a data template to declare an element name, which referenced a column that did notexist in the SQL query. In 10gthis situation returned a null value for the element. In 11gthis construction causes an invalid warning.

To correct the issue, delete the column by using the Data Model Editor in 11g.

For additional information about repository metadata upgrade considerations, refer to Oracle Fusion Middleware Upgrade Guide for

Oracle Business Intelligence 11g.

Summary

This tutorial showed you how to use Oracle Fusion Middleware Upgrade Assis tant to upgrade an existing Oracle Business Intelligence

10genvironment to an 11genvironment.

In this tutorial, you should have learned how to:

Install the Sample Sales 10gdata set


82/82


Upgrade an Oracle BI 10grepos itory and presentation catalog to Oracle BI 11g

Verify an Oracle BI 11gupgrade

Incorporate enhanced cons istency checking for Oracle BI 11grepositories

Incorporate modeling diagram changes for Oracle BI 11grepositories

Incorporate changes to the Oracle BI 11gsecurity model

Apply new Oracle BI 11grepository metadata features

Use Fusion Middleware Control to configure Oracle BI 11g

Apply new Oracle BI 11gpresentation features

Upgrade the Oracle BI Publisher 10grepository to Oracle BI Publisher 11g

Resources

Oracle Business Intelligence Enterprise Edition DocumentationOracle Business Intelligence Enterprise Edition Online Tutorials

Oracle University

Oracle Technology Network

Oracle Business Intelligence Discuss ion Forums

CreditsLead Curriculum Developer:Jim Sarokin

Other Contributors: Lea Shaw

Copyright 2011, Oracle and/or its affil iates. All rights reserved
http://www.oracle.com/corporate/index.htmlhttp://www.oracle.com/corporate/index.htmlhttp://forums.oracle.com/forums/category.jspa?categoryID=16http://www.oracle.com/technetwork/index.htmlhttp://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=3http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/tutorials/index.htmlhttp://www.oracle.com/technetwork/middleware/bi-enterprise-edition/documentation/bi-ee-087853.html

upgrading oracle business intelligence from 10g to 11g

Documents