| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Release 7.9.6.4 Part Number E35270-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Release 7.9.6.4 Part Number E35270-01 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of the Oracle Business Intelligence Applications upgrade process.
This chapter contains the following topics:
Section 2.2, "Why Upgrade to Oracle BI Applications Release 7.9.6.4?"
Section 2.3, "Considerations About Upgrading to Oracle BI Enterprise Edition 11g"
Section 2.4, "Considerations About Upgrading Oracle BI Applications"
Section 2.6, "Major Stages of Oracle BI Applications Upgrade"
Note:
Upgrading Oracle BI Applications requires careful planning and testing. You must allocate sufficient time for implementing the upgrade. It is highly recommended that customers consider obtaining support from Oracle Consulting Services to assist with an applications upgrade.
Also note that the process of upgrading to Oracle BI Applications release 7.9.6.4 includes an upgrade of the Oracle Business Intelligence platform to Oracle Business Intelligence Enterprise Edition 11g (11.1.1.6.4)
The Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users provides instructions for upgrading to the current release of Oracle BI Applications from the previous releases listed below:
Siebel Analytics 7.5.3
For instructions, see Chapter 3, "Upgrading Siebel Analytics 7.5.x."
Siebel Business Analytics 7.7, 7.7.x and 7.8.x
For instructions, see Chapter 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x."
Siebel Business Analytics for Life Sciences 7.8.0, 7.8.1 and 7.8.2
For instructions, see Chapter 4, "Upgrading Siebel Business Analytics 7.7, 7.7.x and 7.8.x."
Oracle Business Intelligence Applications 7.9.0 through 7.9.6.3
For instructions, see one of the following chapters, depending on your source system:
Chapter 5, "Upgrading Oracle BI Applications 7.9.x for Siebel Source Systems"
Chapter 6, "Upgrading Oracle BI Applications for Oracle Source Systems"
Chapter 7, "Upgrading Oracle BI Applications for PeopleSoft Source Systems"
Chapter 8, "Upgrading Oracle BI Applications for JD Edwards Source Systems"
There can be many reasons your organization would consider upgrading to Oracle BI Applications release 7.9.6.4, including, but not limited to, the following:
An upgrade of the transactional applications can trigger a need to upgrade Oracle BI Applications to the latest release. However, it is not always necessary to upgrade Oracle BI Applications if you upgrade the transactional applications. For example, if both the version of transactional applications from which you are upgrading and to which you are upgrading are supported by the release of Oracle BI Applications you are using, you do not need to upgrade Oracle BI Applications to the latest release.
A strong need to leverage new features and enhancements offered by Oracle BI Enterprise Edition 11g (11.1.1.6.4), including support for newer versions of databases.
New features and enhancements offered by Oracle BI Applications, including new application content, support for newer versions of source systems, support for new versions of databases, and language support.
Potential cost savings on additional maintenance costs in the event that support is no longer available for the transactional applications, the database version, or the Informatica version.
Business requirements.
The most common triggers for upgrading Oracle BI Applications are an upgrade of the underlying transactional source system or systems, the need to take advantage of new content in the latest version of Oracle BI Applications, and support for new database platforms or operating systems.
While upgrading only the Oracle Business Intelligence Foundation to leverage several enhancements offered in Oracle BI Enterprise Edition 11g (11.1.1.6.4) is a supported option, note that only Oracle BI Applications release 7.9.6.4 is certified on Oracle BI Enterprise Edition 11g (11.1.1.6.4). Previous releases of Oracle BI Applications are not certified on Oracle BI Enterprise Edition 11g. Unless you have a compelling need to leverage the enhancements offered in Oracle BI Enterprise Edition 11g (11.1.1.6.4), suitable options worth considering are 1) staying on Oracle BI Enterprise Edition 10g, or 2) upgrading Oracle BI Enterprise Edition as part of an integral upgrade along with Oracle BI Applications.
As with any upgrade, Oracle recommends that Oracle BI Applications customers who currently use Oracle BI Enterprise Edition 10g do a thorough cost-benefit analysis before considering an upgrade to Oracle BI Enterprise Edition 11g (11.1.1.6.4).
Upgrading to Oracle BI Applications release 7.9.6.4 requires an upgrade of the Oracle Business Intelligence Foundation to Oracle BI Enterprise Edition 11g (11.1.1.6.4).
Upgrading Oracle Business Intelligence from 10g to 11g is a substantial project, requiring the need to budget sufficient time and resources for analysis, implementation, and verification of the upgrade. Oracle provides tools and technology to automate much of the upgrade process. However, the precise strategy that you will want to adopt will depend both on the configuration of the existing 10g system, and on the required configuration of the upgraded 11g system. Before performing the platform upgrade, you should thoroughly review Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1), and carefully read the chapter titled, "Planning to Upgrade from Oracle BI 10g to BI 11g."
Oracle BI Applications customers upgrading to the Oracle Business Intelligence Foundation to Oracle BI Enterprise Edition 11g (11.1.1.6.4) should note that the BI Server in Oracle BI Enterprise Edition 11g (11.1.1.6.4) is more stringent in its metadata validation checks and produces a number of warnings on the repositories that are upgraded from earlier Oracle BI Applications releases. These warnings can be fixed manually. For more information about these warning and for the workarounds to fix the issues, see Oracle Business Intelligence Applications Release Notes.
In addition, Oracle BI Enterprise Edition 11g (11.1.1.6.4) includes changes and enhancements that affect the look, feel, and behavior of dashboards and reports. For a description of these changes, see the section titled "Appendix B: Possible Changes in Oracle BI Enterprise Edition Appearance and Behavior After Upgrade," in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).
You should also be aware of the following security-related changes in Oracle BI Enterprise Edition 11g (11.1.1.6.4):
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 authentication provider 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.
See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for more information about these and other security-related changes.
You should consider the following points before you begin your upgrade:
Review the System Requirements and Supported Platforms for Oracle Business Intelligence Applications to make sure your database platform versions are supported.
The upgrade process is not only a technical process. It requires significant planning and involvement from many teams, including development, database administrators, business analysts, QA, and so on.
You should determine what customizations were made to your existing application before you begin the upgrade process. It is recommended that you budget sufficient time (in the upgrade project) for detailed review of current customizations and relevance of the customizations for the new version of the application to which you plan to upgrade.
You will also need to analyze the impact of the schema changes on your current custom implementation. The extent of your customizations will have an impact on the length of time required for the upgrade.
At different stages of the upgrade you will also need to analyze your organization's business requirements. For example, at the stage in which you are upgrading the Oracle Business Intelligence repository, you will need to know which repository objects are not in use so that they can be trimmed from the repository. To determine this information, you will need to know what reports are in use.
Depending on the release from which you are upgrading, moving the customizations in your existing repositories, reports, and dashboards to the new version may require a multi-step process and may involve manual processes at some stages.
It is highly recommended that you use side-by-side environments when performing each stage of the upgrade process. Enabling side-by-side-instances of the entire Oracle BI Applications environment is a critical success factor for upgrade.
For some stages of the upgrade, you can upgrade your environments in place. However, for comparison and benchmarking purposes, it is recommended that you upgrade using side-by-side environments.
For each stage of the upgrade process, you need to allocate a reasonable amount of time to validate the results of that stage and address any problems. In addition, final user acceptance testing must confirm that the entire upgrade process was successful.
When you move from a development environment to test or production environments, you must perform the following stages of the upgrade process for each environment:
Upgrade the Oracle Business Intelligence platform
Upgrade Oracle BI Applications
Migrate the data
You can migrate the DAC, Informatica, and Oracle BI repositories, and the presentation catalogs into the production environment after you merge and test them.
This section provides best practice steps you need to perform before you begin the upgrade process.
Review this guide, Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users, in its entirety.
Rename and copy into a different location your current repositories, presentation catalog (formerly known as the Web Catalog), and DAC installation folder from your existing environment. The file names and locations listed below represent the standard names and locations of files that shipped with previous versions of Siebel Business Analytics Applications and Oracle BI Applications.
When you back up the DAC Repository, you export the DAC metadata, in XML format (using the DAC's Export tool), into a different database, which can be used later as a reference. For instructions, see the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
| Type | File or Folder | Default BI 10g Location |
|---|---|---|
|
DAC metadata repository |
*.xml |
OracleBI\dac\export Note: This is the directory into which you copied the DAC metadata files after you installed DAC. |
|
Oracle BI Repository (formerly called Siebel Analytics Repository) |
Oracle BI Repository (or Siebel Analytics Repository) you are currently using |
OracleBI\server\Repository |
|
Informatica Repository |
Informatica Repository file (for example, Oracle_BI_DW_Base.rep) |
OracleBI\dwrep\Informatica\Repository |
|
Presentation Catalog (formerly called Web Catalog) |
Presentation Catalog (or Web Catalog) you are currently using |
OracleBIData\web\catalog |
|
DAC installation folder |
dac |
OracleBI\dac |
Gather information that describes the current implementation, including the following:
Version of the transactional database to which you upgraded.
Version of the Oracle BI Enterprise Edition (platform) or Siebel Business Analytics platform from which you are upgrading.
To determine the platform version from which you are upgrading, launch the Administration Tool, and click Help, and then click Administration Tool in the toolbar. A message box provides the platform version.
Version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading.
To determine the version of Siebel Business Analytics Applications or Oracle BI Applications from which you are upgrading, launch the Data Warehouse Administration Console (DAC), and click Help, and then click About DAC.
Note:
If DAC is not a component of your Analytics installation, you are running Siebel Analytics 7.5.x.
This section describes the major stages of the Oracle BI Applications upgrade process and includes the following topics:
Note:
iBots (agents) are not included in the standard (out-of-the-box) Oracle BI Applications product. However, you can upgrade a 10g Scheduler schema to 11g. For more information, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).
Figure 2-1 shows the upgrade flow for the major stages of the Siebel Business Analytics and Oracle BI Applications upgrade process. Depending on the prior release from which you are upgrading, you may find minor changes in the process shown in Figure 2-1.
In general, you must complete stages one through five sequentially, in the following order:
Stage 1: Upgrade the Siebel Business Analytics platform or Oracle BI platform to Oracle Business Intelligence Enterprise Edition 11g (11.1.1.6.4). See Section 2.3, "Considerations About Upgrading to Oracle BI Enterprise Edition 11g" for important information about this upgrade process.
Stage 2: Upgrade the following:
Siebel Business Analytics Applications or Oracle BI Applications to the current release of Oracle BI Applications
Informatica PowerCenter to version 9.01 Hotfix 2
DAC platform to release 11g (11.1.1.6.4)
Stage 3: Upgrade the metadata in the DAC and Informatica repositories.
Stage 4: Upgrade the data warehouse schema.
Stage 5: (For Siebel source systems) upgrade the Siebel transactional database schema.
After completing stage 4 or stage 5 for Siebel source systems, you can then perform the next three stages simultaneously:
Stage 6: Migrate data into the upgraded data warehouse. Note that for testing purposes, you can migrate a subset of data and study the results before migrating all of the data.
Stage 7: Import the Oracle BI Applications release 7.9.6.4 LDIF file into the embedded LDAP Server.
Stage 8: Use the Oracle BI Enterprise Edition 11g Upgrade Assistant to upgrade the following repositories and presentation catalog (or Siebel Analytics Web catalog) from the 10g format to the 11g format:
The Oracle BI repository you are currently using (the repository that includes your customizations).
The standard (out-of-the-box) Oracle BI repository version 7.9.x (the version from which you are upgrading).
The presentation catalog you are currently using.
Note: Your current policy store will be merged with the Oracle BI Applications release 7.9.6.4 policy store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final policy store will be the super set of Oracle BI Applications release 7.9.6.4 policy store and the custom and current policy information from the 10g repository.
Also, your current users and groups from the repository will be merged with the Oracle BI Applications release 7.9.6.4 identity store while upgrading the Oracle BI repository from the 10g format to the 11g format. The final identity store will be the super set of the Oracle BI Applications release 7.9.6.4 identity store and the identity store information (users and groups) from the 10g repository.
After you complete stage 8, you can perform stages 9 and 10 simultaneously:
Stage 9: Merge your customizations of a prior release of the Oracle BI repository with the new release of the Oracle BI repository.
See the section titled "Understanding the Upgrade of Repository Metadata," in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1) for information about Oracle BI Enterprise Edition platform behavior related to the upgrade of the Oracle BI repository.
Stage 10: Merge your customizations of a prior release of the presentation catalog with the new release of the presentation catalog.
See the section titled "Understanding Oracle BI Presentation Catalog Upgrade," in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1) for information about Oracle BI Enterprise Edition platform behavior related to the upgrade of the Siebel Analytics Web Catalog and the Oracle BI Presentation Catalog.
Note:
Depending on the prior release from which you are upgrading, you may find minor changes in the process described in this section.
Note:
The schema and data are upgraded in place and affect only the preconfigured (out-of-the-box) content. Customizations to the schema are not affected by the upgrade process.
Table 2-1 provides the documentation you should refer to for each stage of the upgrade.
Table 2-1 Major Stages of the Oracle BI Applications Upgrade and Related Documentation
| Stage | Documentation Related to Stage |
|---|---|
|
Stage 1: Upgrade the Siebel Business Analytics platform or Oracle BI Enterprise Edition platform to Oracle BI Enterprise Edition 11g (11.1.1.6.4). |
Note: You should carefully review the chapter titled, "Planning to Upgrade from Oracle BI 10g to BI 11g" before beginning the upgrade process. |
|
Stage 2: Upgrade the following:
|
|
|
Stage 3: Upgrade the metadata in the DAC and Informatica repositories. |
|
|
Stage 4: Upgrade the data warehouse schema. |
|
|
Stage 5: (For Siebel source systems only) Upgrade the Siebel transactional database schema. |
|
|
Stage 6: Migrate data into the upgraded data warehouse. |
|
|
Stage 7: Import the Oracle BI Applications release 7.9.6.4 LDIF file into the embedded LDAP Server. |
|
|
Stage 8: Upgrade the Oracle BI repositories and presentation catalog from the 10g format to the 11g format. |
|
|
Stage 9: Merge the Siebel Analytics repository or Oracle BI repository with the new version installed with the current release. |
|
|
Stage 10: Merge the Siebel Business Analytics Web Catalog or Oracle BI presentation catalog with the new version installed with the current release. |
|
|
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
