Upgrading Oracle Business Intelligence from 10g to 11g

Purpose
This tutorial covers using Oracle Fusion Middleware Upgrade Assistant 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 10g Release 3 (10.1.3.2 or later) environment to Oracle Business Intelligence Enterprise Edition 11g in 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 10g version of the Sample Sales application to demonstrate the upgrade process, and also covers a subset of 11g features 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 Business Intelligence Enterprise Edition 11g Have access to the Sample Sales repository and Web catalog metadata, designed for Oracle Business Intelligence Enterprise Edition 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 sample data set from 10g to 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 Business Intelligence Enterprise Edition 11g is installed. To install the Sample Sales data set, perform the following steps:

1. As described in the Prerequisites section, download the 10g Sample 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 11g is installed. In this example, the zip file is downloaded toD:\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. Extract Sample_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 10g presentation 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 used by Briefing Books. The directory is called deliveries by default and is located in the OracleBIData\web\catalog directory. In many cases, the 10g directory is empty. If the 10g deliveries 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 selected by default.

5. Sample_Sales_V1.3_Dataset.zip contains 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 server\Sample to maintain the relative paths for all of the XML files in the repository. In this example, the data set is extracted to: D:\bi\instances\instance\bifoundation\OracleBIServerComponent\ coreapplication_obis\server\Sample\samplesales

6. samplesales.rpd is the Sample Sales 10g BI 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 repository and presentation catalog, perform the following steps by using the Upgrade Assistant. Please note that the WebLogic Administration Server and the Managed Server in the 11g environment must remain running during the upgrade process.

1. Navigate to the ORACLE_HOME\bin directory of the Oracle Fusion Middleware installation. In this example, the directory path is D:\bi\Oracle_BI1\bin.

2. Double-click ua.bat to open Upgrade Assistant in the graphical user interface mode. This tutorial describes how to use Upgrade Assistant in the 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 Oracle Fusion Middleware Upgrade Planning Guide.

3. On the Welcome screen, click Next.

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).

6. Click Browse next to the RPD File field.

7. Browse to the location of the 10g version of the Sample Sales repository and click Open. In this example, the path isD:\SampleSales\samplesales.rpd.

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

9. Enter the Administrator User Name and Administrator Password for the 10g samplesales repository. In this example, the username and password are both Administrator.

10. Enter and confirm a password that will be used to secure the upgraded 11g repository. This password is required for 11g repositories. It does not have to match the 10g repository password or any other password. In this example, the password is welcome1.

11. Select Upgrade Catalog.

12. Click Browse next to the Catalog Directory field.

13. Browse to the location of the 10g version of the Sample Sales presentation catalog and click Open. In this example the path is D:\SampleSales\Sample_Sales_V1.3_Webcat\samplesales.

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

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.

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

18. Click Next to continue.

19. On the Examining Components screen, wait until you see a succeeded message. During the examination process, Upgrade Assistant checks whether the source directory exists, the source directory is readable, and contains a file for upgrade.

20. Click Next to continue.

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

22. Click Upgrade to start the upgrade process.

23. On the Upgrading Components screen, you can view the upgrade progress. BI components are stopped 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 <BI_ORACLE_HOME>\upgrade\logs\ua<timestamp>.log where<timestamp> is the current date and time. You can also check the component log files in directories organized by component under <ORACLE_INSTANTANCE>\diagnostics\logs.

25. Click Next to continue.

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

Verifying the Upgrade

The Upgrade Assistant automatically loads the new repository to the 11g BI Server and restarts all BI components. You can verify that Oracle BI EE has been upgraded successfully by logging into the 11g system to confirm that Oracle BI EE components are running, checking repository metadata, and verifying that you are able to view dashboards 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

1. In a browser, enter http://localhost:7001/em to log into Fusion Middleware Control on the 11g system.

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.

4. Select the Deployment page.

5. Select the Repository subtab. This page shows the current installed repository. Notice that the Upgrade Assistance automatically uploaded the upgraded repository to the BI Server domain. In this example, the repository is named assamplesales_BI0002.

Verifying Repository Metadata

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

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 identif during the upgrade process: welcome1. The username and password are the Oracle WebLogic Server adminis username and password created during your 11g installation. In this example, the user is weblogic.

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

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

6. Double-click Connection Pool A.

7. Click Yes to check out the object.

8. The Connection Pool A dialog box opens. Notice the data source name field. This points to the location wher XML files are stored. The data source name includes a variable (BI_EE_HOME) and the path to the directory are stored. Recall that earlier in this tutorial you unzipped the Sample Sales XML data files to the...\server\Sample\samplesales directory on the 11g server. In the steps that follow, you modi theBI_EE_HOME variable to point to the correct directory.

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

10. Select Manage > Variables to open Variable Manager.

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

12. Click Yes to check out the object.

13. In the Static Repository Variable dialog box, change the Default Initializer to the XML data source path (with additional directories). In the example shown below, you set the variable initializer to

D:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreapplic .

14. Click OK to close the Static Repository 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 consistency at this point.)

18. Close the repository.

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

20. Close the Administration Tool.

Verifying Reports and Dashboards

1. Sign in to Oracle BI 11g as an administrative 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.

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

7. Open and view dashboards.

8. Sign out of Oracle BI. Congratulations! You have upgraded the Sample Sales data set from 10g to 11g and 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 10g and 11g environments 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 checking Incorporating 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 11g and Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence 11g.

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 consistency 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 see error and warning messages 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 Consistency Check Manager addresses these issues by enforcing additional validation rules to help ensure that the repository is consistent. In addition, some rules that existed in previous releases might now be displayed during consistency checks.

The steps that follow provide only a few examples of 11g consistency 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 11g and Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g.

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 11g security.

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.

12. Click Yes 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 error 38123 no longer appears in Consistency Check Manager.

17. Minimize Consistency Check Manager.

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 11g release, including an improved 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 used 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 11g changes to the modeling diagrams.

For more information related to using the Physical and Business Model layer diagrams, please refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g and 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

2. Right-click any one of the four highlighted tables and select Business Model Diagram > Selected Tables Only to open the Business 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.

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 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.

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

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 andD3 Order.

10. Close the Business Model Diagram.

11. Restore Consistency Check Manager.

12. Click Check All Objects.

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

14. Minimize Consistency Check Manager.

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

Incorporating Changes to the Repository Security Model

There are changes in the Oracle BI 11g repository related to security:

As discussed earlier in this tutorial, repositories now have repository-specific passwords 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 11g. 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 Manager and 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 repository 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 Assistant migrates users and groups from a Release 10g repository into the embedded LDAP server in a Release 11g installation.

4. Notice the Administrator user. In an Oracle Business Intelligence Release 10g installation, a special user named Administrator has full administrative permissions and is also used to establish trust between processes within that installation. In Oracle Business Intelligence Release 11g, there is no special significance to the name Administrator 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 installation is configurable and independent.

5. Notice the demo2 and demo users. These are additional users from the 10g Sample Sales repository.

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 theweblogic administrative user. Your results will vary depending on which users you have defined in your 11genvironment. For example, the users Administrator_f and Administrator_d are 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.

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 assigned to users and groups in a directory. This indirection allows an Oracle Business Intelligence 11g system 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 with XMLP. These are security groups that were defined in the 10g Sample Sales repository. They are automatically converted to application roles in the 11g environment.

11. Notice also the following application roles: BIConsumer BIAuthor BIAdministrator Oracle BI 11g provides this set of application roles as part of the default security realm.

12. BIAdministrators, however, is not a default application role, which is why you received the consistency check warning39051. To remove the warning, right-click BIAdministrators and select Delete.

13. Click Check Out.

14. Click Yes to confirm the delete.

15. Select Action > Close to close Identity Manager.

16. Restore Consistency Check Manager.

17. Click Check All Objects.

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

19. Close Consistency Check Manager.

20. Check in the changes.

21. Click Yes to check global consistency.

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

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.

26. Close the repository.

27. Click OK.

28. Leave the Administration Tool open .

Exploring Default Security Settings for Oracle BI 11g

There are changes to how security is managed in Oracle BI 11g. Security is now managed by using WebLogic Administration 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 security controls include:

An embedded directory server functioning as an identity store designed to hold all user and group definitions, required to control authentication A file-based policy store designed to hold the application role and permission grant mappings to users and groups, required to control 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 11g and Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

1. To open the WebLogic Administration 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 username and password to use as an Oracle BI Administrator. In this training environment, the Administrator user created during installation is weblogic. This is an arbitrary choice and there is nothing special about the name. This user has administrative privileges across the Oracle Business Intelligence 11g stack. This includes the OBI repository, 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 single WebLogic domain namedbifoundation_domain into which all the OBI applications are deployed.

3. Click Security Realms.

4. Notice in the right pane that there is a single 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 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 processes, 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.

8. Click the Users and Groups tab.

9. Click the Users subtab.

The default identity store is pre-seeded with usernames specific to Oracle Business Intelligence. These default usernames are provided as a convenience so that you can begin using 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 10g repository and were created by the Upgrade Assistant (for example, demo and demo2), and some are from the 11g environment used to build this tutorial (for example, Administrator_f and Administrator_d).

10. Notice the weblogic user. This is the administrative 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 installation, can be any desired name, and therefore does not need to be Administrator. The password is likewise provided during installation. In the default security configuration, an administrative user is a member of the BIAdministrators 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 administrative 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.

11. Notice the BISystemUser user. Oracle Business Intelligence system components establish a connection to each other as BISystemUser instead of as the Administrator user, the latter being the practice in earlier releases. Using a trusted system account, such as BISystemUser, to secure communication 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 user 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 should be protected from non-administrative 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 security 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 see later in this practice, groups are then mapped to application roles in order to grant rights.

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 using 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 permissions equivalent to those of the Administrator user of earlier releases. Members of the BIAuthors group have the permissions necessary to create content for others to consume. Members of the BIConsumers group have the permissions 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 weblogic user is a member of the two administrator groups: Administrators and BIAdministrators.Administrators is the WebLogic administrators group, which gives rights to administer WebLogic and FMW enterprise manager. Membership in

both administration groups gives this user a single unified administration account for the entire product stack.

16. Return to the browser tab where Fusion Middleware Control is open. If it is not open, enter http://localhost:7001/emand log in as an administrative 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 10g Sample Sales repository (XMLP_*) are also displayed as

application roles.

20. The default application roles are:

BIAdministrator: Grants administrative permissions 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 the BIAuthor group is explicitly granted this role. 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.

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 permissions. These permissions 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 those used 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.

23. Leave Fusion Middleware Control open.

Applying New 11g Repository Metadata Features

There are new repository metadata features for 11g that 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 11g metadata features, please refer toOracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g and Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition.

1. In the BI Administration Tool, select File > Open > Offline to open samplesales.rpd in offline mode. Recall that this is the copy of the upgraded repository 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 Business Model and Mapping layer, expand the Sample Sales business model and notice that logical dimensions already exist: H0 Time, H1 Customer, H2 Market, and so on.

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

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 presentation table.

7. Notice that two presentation hierarchies are created: H0 Time - Year and H0 Time - Fiscal Year. For logical dimensions 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 dimension in the Business Model and Mapping layer.

Presentation hierarchies and presentation levels provide an explicit way to expose the multidimensional 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.

10. Minimize Consistency Check Manager.

11. Expand the H0 Time - Fiscal Year presentation hierarchy.

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

13. Click the Display Columns tab.

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.

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

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

19. Repeat the steps to add display 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

20. Restore Consistency Check Manager.

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.

24. Close the repository.

25. Close the Administration 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 repository in this tutorial, you must upload the modified repository 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 f URL:http://localhost:7001/em and sign in as an administrative 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.

6. Click Close when you receive the Lock and Edit Configuration Completed Successfully confirmation me

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

8. By default, the dialog box should open to the default repository directory. If not, browse toD:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreappli

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

10. Enter welcome1 in the Repository Password and Confirm Password fields.

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

12. Click Activate Changes.

13. Allow Activate Changes processing to complete. Click Close when you receive the Activate Changes Com message.

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

15. On the Overview page, click Restart.

16. Click Yes when you receive the Are 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 the Restart All Completed Successfully confirmation message.

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

Applying New 11g Presentation Features

There are many new 11g presentation 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 is displayed using a tree-like structure. 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: Consists 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 11g presentation features for users, please refer to Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition 11g.

1. Sign in to Oracle BI.

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

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

4. Click Results.

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

Upgrading Oracle BI Publisher Repository

The Upgrade Assistant 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 11g into two objectsa 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 permissions will become available to 11g as the Upgrade Assistant 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 Repository

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

1 . Start the Upgrade Assistant as you did above in the topic titled "Upgrading the Oracle BI Repository and Cata

2 . The Welcome page appears. Click Next.

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

4 . The Specify Source Details page appears. Two options are available for selection: the first is for the BI Publis 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 loc are upgrading the E-Business Suite Data Template Directory, you browse for the data template directoryNo Assistant does not support reading the data definition from the E-Business Suite environment. You need to sto in a file system, and then run the Upgrade Assistant to create an equivalent data model definition in the BI Pub

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

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

Click Next. 7 . The Specify Destination Details page appears. Click Browse to select the location for your upgraded repositor repository as the installed bishiphome 11g repository path (for example,%MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\b 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 rep 11g repository contains required files. If you are upgrading the E-Business Suite Data Template Directory, you browse for the data model directory.

8 . Click Next. 9 . The Specify WebLogic Server page appears. In this example, the Administration server is running locally; the corresponds accordingly.

Enter the Host (localhost - the default), Port (7001), User Name (weblogic), and Password (welcome1) as y topic titled "Upgrading the BI Repository and Catalog" and click Next.

10 The Examining Components page appears. The system is examined to ensure that everything is available and . proceed. For example, the installer interrogates the system to ensure that there is enough space. The status is s A log file for the session is available. You review the log file now or at a later time. Click the hot link for the bottom of the dialog box).

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 Upgr .

14 The Upgrading Components page appears. Examine the status once again. If the status is not successful, revie . determine and resolve the issues. Click Next.

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

Verifying the BI Publisher Repository Upgrade

To verify that the upgrade ported your reports over to 11g properly, 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, enter http://<hostname>:7001/xmlpserver (for example,http://localhost:7001/xmlpserver). The Oracle BI Publisher Enterprise Login window appears.

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

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

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

5 . Click the Server Configuration tab.

6 . Enter the path for your upgraded repository into the Configuration Folder area. This is the path that you specif page in the Upgrade Assistant (for example,%MIDDLEWARE_HOME%\user_projects\domains\bifoundation_domain\config\b

7 . Click Apply. A confirmation message appears.

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 - User in the Fol 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.

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 Publisher 11g, there are a number of considerations and tasks that should be addressed. Some of these considerations are addressed below:

Verify that the xmlp-server-config.xml 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 directory.

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\DataSourcedirectory.

Editing upgraded data models: When the 10g report 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 11g model. 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 link to other data sets).

Validation errors for upgraded data templates: The Data Model Editor in 11g introduces restrictions 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 10g data template allowed you to reference elements within the data template without regard to the case being used. In 11g the case must match the referenced item. - Orphan elements: In 10g it was possible for a data template to declare an element name, which referenced a column that did not exist in the SQL query. In 10g this situation returned a null value for the element. In 11g this 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 Assistant to upgrade an existing Oracle Business Intelligence 10g environment to an 11g environment.

In this tutorial, you should have learned how to:

Install the Sample Sales 10g data set Upgrade an Oracle BI 10g repository and presentation catalog to Oracle BI 11g Verify an Oracle BI 11g upgrade Incorporate enhanced consistency checking for Oracle BI 11g repositories Incorporate modeling diagram changes for Oracle BI 11g repositories Incorporate changes to the Oracle BI 11g security model Apply new Oracle BI 11g repository metadata features Use Fusion Middleware Control to configure Oracle BI 11g Apply new Oracle BI 11g presentation features Upgrade the Oracle BI Publisher 10g repository to Oracle BI Publisher 11g

Resources

Oracle Business Intelligence Enterprise Edition Documentation Oracle Business Intelligence Enterprise Edition Online Tutorials Oracle University Oracle Technology Network Oracle Business Intelligence Discussion Forums

Credits

Lead Curriculum Developer:Jim Sarokin Other Contributors: Lea Shaw

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