3 Upgrading Your Oracle Portal, Forms, Reports, and Discoverer Environment

3.5.3.1 About the Oracle Portal, Forms, Reports, and Discoverer Installation and Configuration Tool

The Oracle Portal, Forms, Reports, and Discoverer installer functions as an installation and configuration tool. It allows you optionally to separate the installation and configuration tasks. In other words, you can choose to install the software on disk into an Oracle home and configure the components later.

However, for the purposes of this upgrade procedure, and in order to ensure you are installing and configuring the latest Oracle Fusion Middleware 11g software, you must perform a software-only install, then apply the latest Oracle Fusion Middleware patch set, and then start the tool a second time to configure the Oracle Portal, Forms, Reports, and Discoverer software.

For more information about specific version information, refer to "Obtaining the Latest Oracle WebLogic Server and Oracle Fusion Middleware 11g Software" in the Oracle Fusion Middleware Upgrade Planning Guide.

3.5.3.2 Related Documentation for Installing and Configuring Oracle Portal, Forms, Reports, and Discoverer 11g

Refer to the following documentation resources for complete instructions on installing and configuring the Oracle Portal, Forms, Reports, and Discoverer middle tiers:

• The Oracle Fusion Middleware Installation Planning Guide

• The Oracle Fusion Middleware Quick Installation Guide for Oracle Forms and Reports

• The Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer

3.5.3.3 Summary of the Oracle Identity Management 11g Installation Steps

Table 3-1 provides a high-level summary of the main steps you must perform when installing and configuring the Oracle Portal, Forms, Reports, and Discoverer middle tiers.

Note that the procedures described in this section assume you have downloaded the latest version of Oracle WebLogic Server and Oracle Fusion Middleware 11g. For more information, refer to "Obtaining the Latest Oracle WebLogic Server and Oracle Fusion Middleware 11g Software" in the Oracle Fusion Middleware Upgrade Planning Guide.

3.5.4.1 Running the Oracle Portal, Forms, Reports, and Discoverer Configuration Tool

After you install the Oracle WebLogic Server software, create the Middleware home, and install the latest Oracle Fusion Middleware software, you can then configure the Oracle Portal, Forms, Reports, and Discoverer components.

To configure Oracle Portal, Forms, Reports, and Discoverer:

1. Start the Oracle Portal, Forms, Reports, and Discoverer 11g configuration:

   On UNIX systems:

   > IDM_ORACLE_HOME/common/bin/config.sh
   

   On Windows systems:

   IDM_ORACLE_HOME\common\bin\config.bat
   

2. Follow the instructions on the screen to configure one or more of the Oracle Portal, Forms, Reports, and Discoverer components.

   As you proceed through the installation screens, note the following:

   • If you are upgrading to Oracle Portal 11g, then see Section 3.5.4.2, "Specifying the PORTAL Schema Name and Password".

   • If you are upgrading Oracle Business Intelligence Discoverer, then see Section 3.5.4.3, "Specifying the DISCOVERER Schema Name and Password".

   For other information about installing and configuring Oracle Portal, Forms, Reports, and Discoverer, refer to the following:

   • For help on the options available on each screen, click Help.

   • For more detailed information about the configuration options, "Configuring Your Components" in the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer..

3.5.4.2 Specifying the PORTAL Schema Name and Password

If you are configuring Oracle Portal in preparation for an upgrade from Oracle Portal 10g, then the installer prompts you for the name and password of the Oracle Portal schema (Figure 3-3).

It is important that you enter the name and password of the Oracle Application Server 10g PORTAL schema, as follows:

• In the Schema Name column, enter PORTAL.

• In the Schema Password column, enter the password for the 10g PORTAL schema. For more information, see Section 3.5.4.4, "Locating the Oracle Portal 10g Schema Password in the Oracle Internet Directory"

Figure 3-3 Specify Schema Screen From an Oracle Portal, Forms, Reports, and Discoverer Installation

Description of "Figure 3-3 Specify Schema Screen From an Oracle Portal, Forms, Reports, and Discoverer Installation"

3.5.4.3 Specifying the DISCOVERER Schema Name and Password

If you are configuring Oracle BI Discoverer in preparation for an upgrade from Oracle BI Discoverer 10g, then the installer prompts you for the name and password of the Oracle Fusion Middleware 11g DISCOVERER schema (Figure 3-3).

It is important that you enter the name and password of the Oracle Fusion Middleware 11g DISCOVERER schema that you created using the Repository Creation Utility in Section 3.4, "Task 4: Use the Repository Creation Utility to Install the Oracle BI Discoverer Schema in the Database".

Enter the following information about the DISCOVERER schema on the Specify Schema screen:

• In the Schema Name column, enter the schema name and prefix that you used when you created the schema with Repository Creation Utility. For example, DEV_DISCOVERER.

• In the Schema Password column, enter the password that you provided for the DISCOVERER schema in Repository Creation Utility.

3.5.4.4 Locating the Oracle Portal 10g Schema Password in the Oracle Internet Directory

You can locate and view the password for an Oracle Application Server 10g component schema by using the following ldapsearch command on the Oracle Internet Directory.

If your password is in an Oracle Internet Directory instance, use this command syntax:

ORACLE_HOME/bin/ldapsearch -p oid_port -h oid_hostname -D "cn=orcladmin"
-w orcladmin_password -b "orclresourcename=schema_name,
orclreferencename=metadata_rep_global_db_name, cn=ias infrastructure databases,
cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*"
orclpasswordattribute

For example, on a Linux system, if your Oracle Internet Directory instance is on host1, the port is 13060, the database name is myDB, and the cn=orcladmin password is myPassword1, then you would use this command:

$ORACLE_HOME/bin/ldapsearch -p 13060 -h host1.example.com -D "cn=orcladmin"
-w myPassword1 -b "orclresourcename=PORTAL,
orclreferencename=myDB.example.com, cn=ias infrastructure databases,
cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*"
orclpasswordattribute

3.6.2.1 Using the Upgrade Assistant to Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tier

To upgrade an Oracle Application Server 10g Release 2 (10.1.2) middle tier to Oracle Fusion Middleware 11g:

1. Start the Upgrade Assistant as described in Task 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade.

2. Select Upgrade Middle Tier Instance on the Specify Operation screen (Figure 3-5).

3. Refer to Table 3-2 for a description of the Upgrade Assistant screens that require input from you during a middle-tier instance upgrade and the options on each screen.

   The Upgrade Assistant performs the following tasks and provides the progress on each task:

   • Examines the components to be upgraded.

   • Provides a summary of the components to be upgraded so you can verify that the Upgrade Assistant is upgrading the components you expect.

   • Provides a progress screen so you can see the status of the upgrade as it proceeds.

   • Alerts you of any errors or problems that occur during the upgrade.

     See Also:

     Section B.1, "Troubleshooting Upgrade Assistant Problems and Issues" in the Oracle Fusion Middleware Upgrade Planning Guide for specific instructions for troubleshooting problems that occur while running the Upgrade Assistant

   • Displays the End of Upgrade screen, which confirms that the upgrade was complete.

3.6.2.2 Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance

When you select the Use Source Oracle home ports in destination option in the Oracle Fusion Middleware Upgrade Assistant, note the following.

General Information and Restrictions

• If you select this option, then you will not be able to run both the 10g and 11g middle tiers at the same time; otherwise, port conflicts will occur.

• If you are upgrading to multiple instances of a particular Oracle Fusion Middleware 11g component, you can select this option only once for each component that you upgrade on a host.

  For example, suppose you upgrade Oracle HTTP Server in one Oracle instance on MYHOST1.

  If you use the option again while upgrading another Oracle HTTP Server instance in another Oracle instance on MYHOST1, then the same listening ports are assigned to the second Oracle HTTP Server instance. Two instances of Oracle HTTP Server on the same host cannot use the same listening ports.

Component-Specific Information and Restrictions

• When you use this option to upgrade an Oracle Portal middle tier, the option is enabled and you cannot disable it. As a result, you might end up with extra partner applications displayed on the Oracle Single Sign-On Administration page in Oracle Portal 11g.

  For more information, see Section 4.1.5, "Removing Obsolete Partner Applications After Upgrade".

• If you are upgrading Oracle Reports and you select this option, then Fusion Middleware Control may not be able to gather performance metrics about the Oracle Reports instance. This is because Oracle Enterprise Manager Fusion Middleware Control is using the new Oracle HTTP Server 11g port and not the Oracle HTTP Server 10g port to communicate with Oracle Reports.

  To address this issue, modify the Agent-Monitored Target properties for the Oracle Reports component in Fusion Middleware Control. Change the following properties to reflect the 10g Oracle HTTP Server port information:

  • The HTTP Port property

  • The port identified in the Servlet URL property

  • The Server property for the WLS_REPORTS Java EE application. You must change this property because, during upgrade, the Oracle Reports 11g in-process server is renamed to use the same name as the 10g in-process server.

  For information on changing the Agent-Monitored Target properties, see "Troubleshooting the Display of Performance Metrics and Charts in Fusion Middleware Control" in the Oracle Fusion Middleware Administrator's Guide.

• If you are using Oracle Single Sign-On, and you do not select this option (in other words, if you use a different set of port numbers than those used in Oracle Application Server 10g), then consider the following:

  • You will likely have to re-register your components (such as Oracle Business Intelligence Discoverer) with Oracle Single Sign-On.

    For more information, see "Configuring and Administering Partner Applications" in the Oracle Application Server Single Sign-On Administrator's Guide, which is available in the Oracle Application Server 10g (10.1.4) documentation library on the Oracle Technology Network (OTN):

    http://www.oracle.com/technology/documentation/
    

  • You will have to verify the ports used for Oracle HTTP Server and Oracle Web Cache and re-register Oracle HTTP Server and Oracle Web Cache with Oracle Single Sign-On.

    For more information, see Section 4.5.2, "Web Tier Component Post-Upgrade Tasks When Using Oracle Single Sign-On".

3.6.4.1 Understanding the Impact of the Oracle Portal Schema Upgrade

Before you upgrade the Oracle Portal to 11g, consider the impact of the upgrade on your existing Oracle Portal environment.

In particular, you should be aware that when you use the Upgrade Assistant to upgrade your Oracle Portal schema, the Upgrade Assistant performs the following tasks:

• Creates the upgrade framework objects and installs the Schema Validation Utility.

• Identifies all invalid objects before the upgrade proceeds. You can use this for troubleshooting purposes; all OracleAS Portal packages must be valid before an upgrade.

• Recompiles any invalid non-OracleAS Portal objects and displays warnings if any invalid non-OracleAS Portal objects remain in the database.

• Disables the directory provisioning profile, as a result event notifications in the Oracle Internet Directory instance to which the Oracle Portal instance has subscribed. The Upgrade Assistant later re-enables the directory providing profile.

• Disables triggers in the portal schema and reenables them at the end of the upgrade.

• Disables the Database Management System (DBMS) jobs in the Oracle Portal schema and reenables them at the end of the upgrade.

• Drops statistics gathered on all tables in the portal schema. Later in the process, the Upgrade Assistant gathers statistics supported by OracleAS Portal. Later in the process, the Upgrade Assistant creates the jobs for gathering statistics.

• Upgrades OWA packages if necessary.

• Drops and reloads all Java objects in the Oracle Portal schema. Note that any Java objects that do not belong to OracleAS Portal, but reside in the Oracle Portal must be reinstalled manually after the upgrade.

• Drops and reloads all product messages in all languages in the Oracle Portal schema. If any product messages were manually altered before the upgrade, then these changes will have to be manually reapplied.

• Upgrades the schema and compiles new OracleAS Portal packages.

• Updates the OracleAS Portal release if there are no fatal compilation errors.

• Searches for errors and warnings in the upgrade log file and displays a summary of the issues.

3.6.4.2 Checking for Invalid Objects in the Database Where the Oracle Portal 10g Schema Resides

Before you upgrade the schemas in your database, it is good practice to make sure that none of the database objects required by Oracle Fusion Middleware are invalid:

1. Connect to the Metadata Repository database.

   For example:

   ORACLE_HOME/bin/sqlplus "connect / as sysdba"
   

2. When prompted, enter the SYS password.

3. Issue the following SQL command:

   SELECT owner, object_type, object_name
            FROM all_objects
            WHERE status='INVALID';
   

   The query should not return any database objects that have an Oracle Application Server component schema (such as PORTAL, WIRELESS, and so on) in the 'owner' column.

If you find any invalid objects, run the utlrp.sql script from the SQL*Plus command line to recompile the invalid objects:

@?/rdbms/admin/utlrp.sql

For more information about invalid objects, see "About Dependencies Among Schema Objects" in the Oracle Database Administrator's Guide.

3.6.4.3 Backing Up the Database Where the Oracle Portal 10g Schema Resides

Before you upgrade the Oracle Portal 10g schema to 11g, back up your database, in case you need to restore the database to its pre-upgrade state.

For more information, see "Backup Strategies for Upgrade" in the Oracle Fusion Middleware Upgrade Planning Guide.

3.6.4.4 Verifying the Required Database Parameters for Oracle Portal 11g

Before you upgrade the Oracle Portal schemas in the metadata repository, be sure to verify that the following database parameters are set correctly.

These settings are required for Oracle Portal 11g. If you do not set these parameters correctly, errors will appear in the Upgrade Assistant during the examination phase:

• Set the aq_tm_processes database parameter to a value of one (1) or higher to allow correct management of database queues.

• If you are upgrading the schema in Oracle Database 11g, then set the compatible database parameter to 11.0.0.0.0 or higher.

• If you are upgrading the schema in Oracle Database 10g, then set the compatible parameter to 10.2.0.0 or higher.

• Set the shared_pool_size database parameter to 20MB or higher.

• Set the java_pool_size database parameter to 20MB or higher.

• Set the optimizer_mode database parameter to CHOOSE.

• Set the processes database parameter to at least 500.

3.6.4.5 Verifying That the Database and Oracle Internet Directory Are Running

Before you proceed with the Oracle Portal schema upgrade, you must first ensure that the following processes are up and running and available:

• The database that hosts the Oracle Portal schema

• The listener for the database that hosts the Oracle Portal schema

• The Oracle Internet Directory instance where the Oracle Portal schema is registered

3.6.4.6 Using the Upgrade Assistant to Upgrade the Oracle Portal Schema

To upgrade the Oracle Portal schema:

1. Stop all the middle tiers associated with the metadata repository where the Oracle Portal schema resides.

   This includes the WLS_Portal managed server in the Oracle WebLogic Server domain, as well as any Oracle HTTP Server and Oracle Web Cache instances associated with the middle tiers.

   For more information, see "Starting and Stopping Oracle Fusion Middleware" in the Oracle Fusion Middleware Administrator's Guide.

2. Start the Upgrade Assistant as described in Task 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade.

3. Select Upgrade Metadata Repository Schemas and then Portal Schema from the Specify Operation screen (Figure 3-5).

4. Follow the instructions on the screens to upgrade the Oracle Portal schema.

   Click Help for information about the options available on each screen.