Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle Business Intelligence
11g Release 1 (11.1.1)

Part Number E16452-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

7 Upgrading Oracle Real-Time Decisions

This chapter describes how to upgrade an existing Oracle Real-Time Decisions 3.0.0.1 environment to Oracle Real-Time Decisions 11g.

This chapter contains the following sections:

7.1 Task 1: Understand the Starting Points for Oracle Real-Time Decisions Upgrade

For information about starting points for an Oracle Business Intelligence upgrade, see Chapter 3, "Supported Starting Points for Oracle Business Intelligence Upgrade."

If you are already running Oracle Fusion Middleware 11g, then see Oracle Fusion Middleware Patching Guide, which provides information about applying the latest Oracle Fusion Middleware patches.

This guide provides instructions for upgrading from Oracle Real-Time Decisions Version 3.0.0.1 to the latest Oracle Real-Time Decisions 11g.

7.2 Task 2: Examine Oracle RTD and Other System Configuration Settings

If you have customized the 3.0.0.1 Oracle Real-Time Decisions system with specific server-side configuration parameter values, then examine and note down the customizations. If they have a direct equivalent, then you can replicate them later in the 11g upgraded system.

The customized Oracle RTD server-side configuration settings are included in the Oracle RTD SDConfig table, as shown in the following image.

Surrounding text describes sdconfig.gif.

Note:

The Config values for the Name="config" row show the Oracle RTD configuration parameters set at the cluster level, the values for the Name="config <server_name>" rows show the parameters for the server level.

You might also have created special configuration settings at the application server level, such as JDBC data source settings, JVM parameters, and memory configuration parameters. Note down any configuration settings that you want to be used, exactly or in an equivalent way, in the upgraded system.

7.3 Task 3: Run RCU to Create the Destination BIPLATFORM Schema

The Repository Creation Utility (RCU) is a graphical tool for creating and managing Oracle Fusion Middleware database schemas in the database. To create the Oracle BI EE 11g destination BIPLATFORM schema, see "Additional Oracle BI Installer Requirements" in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

Note:

If you have already run RCU to create the destination BIPLATFORM schema for Oracle BI EE or BI Publisher, then you are not required to perform Task 3. Oracle BI EE, BI Publisher, and Oracle Real-Time Decisions share the BIPLATFORM schema.

7.4 Task 4: Install and Configure Oracle Real-Time Decisions 11g

For installation and configuration instructions, see "Running the Installer" in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

7.5 Task 5: Copy and Reconfigure Data from 3.0.0.1 System to 11g System

There are three broad categories of data that affect Oracle RTD users, and the upgrade considerations for each category are slightly different. The three categories are:

This procedure includes the following assumptions:

Note:

For convenience, all three categories of data upgrade are described in this section, although you do not need to upgrade all the types of data at the same time.

Typically, you upgrade the SDDS database first, then the external enterprise data and model snapshot tables when you need to use them.

SDDS Database

For the SDDS database, copy the existing Oracle RTD 3.0.0.1 database using scripts that are located in RTD_HOME\scripts\sql\db_type, where db_type is either Oracle, SQL Server, or DB2, as follows:

To upgrade the Oracle RTD schema:

  1. In the RTD_HOME\scripts\sql\db_type folder, read the "readme" for the database.

  2. Set up any objects (such as database links) that the readme indicates.

  3. Run the CopyRTDSDDBData.sq script to copy the 3.0.0.1 SDDB data to the 11g database.

External Database Tables and Model Snapshot Tables

For the external data sources that are referenced in the Inline Services, check the 3.0.0.1 data sources that are defined in WebLogic Server Administration Console. The JDBC data sources to be recreated in 11g are the ones for model snapshots (assuming the 3.0.0.1 production model snapshots were created in a non-SDDS database), and the JDBC data sources referenced in the Inline Services.

To create new JDBC data sources and register them with Oracle RTD, follow the steps described in "Configuring Data Access for Oracle Real-Time Decisions" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.

For model snapshots, Oracle recommends setting up the model snapshot tables in a different schema from the SDDB tables. For more information, see "Setting Up and Using Model Snapshots" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.

There are two options for generating contents into the 11g model snapshot tables:

7.6 Task 6: Reapply Oracle RTD and Other System Configuration Settings

If you had previously customized the Version 3.0.0.1 Oracle Real-Time Decisions system with specific server-side configuration parameter values, then you can reapply the settings that have a direct equivalent in 11g. Generally, these are parameters that were set up in JConsole, whose equivalents can be accessed through Oracle RTD MBeans in Fusion Middleware Control. System parameters set up for specific customizations can also be reapplied if still required.

7.7 Task 7: Upgrade the Oracle Real-Time Decisions Artifacts

To upgrade the existing Oracle RTD 3.0 artifacts:

  1. Back up the existing 3.0.0.1 Inline Services.

  2. Open the Inline Services in the Oracle RTD 11g Decision Studio. Ensure that you have created and configured JDBC data sources and JDBC data source references correctly. If there are any errors, correct them.

  3. Recompile the 11g Inline Services in Decision Studio. For each Inline Service, from the Decision Studio menu, select Project, then Clean.

Note:

In version 3.0.0.1, Inline Services were protected by a combination of cluster permissions and explicit Inline Service permissions. In 11g, no permissions are defined in the Inline Service; all permissions are created and configured through permission grants in application policies in a policy store.

You might need to examine any 3.0.0.1 custom roles that you set up in 3.0.0.1 to control Inline Service access and create equivalent application roles and permissions in 11g. For more details, see the Security chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.

7.8 Task 8: Perform Any Required Post-Upgrade Configuration Tasks

If you have Oracle RTD 3.0 clients, such as Java Smart Client, then turn off Web service security, and run the clients in the new 11g environment. (This assumes that you do not need Web service security for the clients.)

If you do need Web service security activated, then update the clients as described in Appendix B, "Oracle RTD Web Services and Clients" of Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions, and the chapter appropriate to your client type in "Part II - Integration with Oracle RTD" in Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions.

As with Inline Service security, in general, you might need to examine any 3.0.0.1 custom roles that you set up in 3.0.0.1, and create equivalent application roles and permissions in 11g. For more details, see the Security chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions

7.9 Task 9: Verify the Oracle Real-Time Decisions Upgrade

To verify that the Oracle Real-Time Decisions upgrade was successful, run test integration points in the Inline Services, then log into Decision Center, and verify that your reports are visible.