This task involves completing the following component-specific upgrade steps:
Refer to the following sections for information about post-upgrade tasks for Oracle Portal:
After you upgrade to Oracle Portal 11g, if you then download a new Oracle Portal Developer Kit-Java (PDK-Java) and you install the PDK-Java software in your newly upgraded Oracle Portal environment, you must perform the following additional configuration task.
For more information about the PDK-Java, see "Creating Java Portlets" in the Oracle Fusion Middleware Developer's Guide for Oracle Portal.
By default, PDK-Java requires the
jdbc/portletPrefs data source, which is created, but not configured during the Oracle Portal 11g installation. To configure the data source for PDK-Java, do one of the following:
jdbc/portletPrefs data source so it points to a valid Oracle Portal preferences store:
If necessary, implement an Oracle Portal preference store, which involves creating a schema for the preference store in an Oracle database.
For more information, see "Implementing a Preference Store" in the Oracle Fusion Middleware Developer's Guide for Oracle Portal.
Open the Administration Console for the Oracle WebLogic Server domain and locate the
jdbc/portletPrefs data source.
jdbc/portletPrefs data source so it connects to the Oracle Portal preference store schema.
For more information, see "Using the PDK-Java Preference Store Migration and Upgrade Utility" in the Oracle Portal Administrator's Guide.
Starting with OracleAS Portal 10g (10.1.4) and later, the Community News portlet is no longer supported.
This portlet is still available on Oracle Portal pages, but when you attempt to edit this portlet, a blank page is displayed. You can manually delete the Community News portlet from portal pages, as follows:
Log in to Oracle Portal.
Navigate to the page from which you want to delete the portlet.
Click Edit at the top of the page to switch to Edit mode.
Click Actions next to the Community News portlet.
On the confirmation page, click Yes to delete the portlet and return to the page.
After you upgrade to Oracle Portal 11g, you can configure end-to-end secure socket layer (SSL) security connections for all your Portal connections.
To configure SSL for Oracle Portal 11g:
Locate the following Oracle Portal configuration file:
# WLS routing configuration<Location /portal> SetHandler weblogic-handler WebLogicHost stbcw19-4.us.oracle.com WebLogicPort 9001 WLProxySSL ON </Location>
Note that the
keytool command shown in the above example is based on the assumption that the managed server keystore is Java Standard Trust.
Log in to the Administration Console.
In the left pane of the Console, expand Environment and select Servers.
Select the WLS_PORTAL managed server.
Select Keystores > Trust > Java Standard Trust Keystore.
Restart OPMN and the WebLogic servers.
For more information, see "Starting and Stopping Oracle Fusion Middleware" in the Oracle Fusion Middleware Administrator's Guide.
If you select the Use source Oracle home ports in destination option when you upgrade to Oracle Portal 11g, then you will notice that, after the upgrade, some extra partner applications will appear on the SSO Administration page in the Oracle Portal 11g instance.
You can safely remove these extra partner applications after upgrade, since they are replaced by the upgraded partner applications.
For more information about the Use source Oracle home ports in destination option, see Section 3.6.3, "Task 6c: Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tiers".
For more information about viewing the partner applications in Oracle Portal 11g, see "Using the Oracle Portal Administer Tab" in the Oracle Portal Administrator's Guide. You use the Portal Administer tab to access the Oracle Single Sign-On administration features in Oracle Portal.
The following sections describe the post-upgrade tasks you should consider performing after you upgrade to Oracle BI Discoverer 11g:
Oracle BI Discoverer provides command-line utilities to help you authorize new users and to update the privileges of existing users. For more information, see "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog" in the Oracle Business Intelligence Discoverer Configuration Guide.
Refer to the following sections for specific post-upgrade tasks to complete using the command-line utilities:
Use the following commands to authorize one or more users so they can access the Discoverer Catalog:
java -classpath path_to_d4o_jar_file load . java -classpath path_to_d4o_jar_file authorize -h hostname -po portname -sid database_SID -p d4osyspasswd -u user
java -classpath C:\temp\d4o.jar load . java -classpath C:\temp\d4o.jar authorize -h sys42.example.com -po 1521 -sid disco_db1 -p nPword432 -u jones
In this example, you must run the load command only once before authorizing any number of users. For example, if you want to authorize ten users, run the load command once, and then run the authorize command once for each user.
To update the user's privileges to access all private and shared folders, use the following command:
java -classpath path_to_d4o_jar_file updatePrivileges -h hostname -po portname -sid database_SID -p d4osyspasswd -u user
java -classpath C:\temp\d4o.jar updatePrivileges -h sys42.example.com -po 1521 -sid disco_db1 -p nPword432 -u jones
In this example, if you provide the -u option, then the privileges will be upgraded only for that user. If you do not provide the -u option, then the privileges will be upgraded for all users.
Oracle BI Discoverer 11g uses the same End User Layer version (5.1) as Oracle BI Discoverer 10g Release 2 (10.1.2).
For more information, see "Creating and maintaining End User Layers" in the Oracle Business Intelligence Discoverer Administrator User's Guide.
Review the following list of manual tasks that you might have to perform after using the Upgrade Assistant to upgrade Oracle Forms Services 10g Release 2 (10.1.2) to Oracle Fusion Middleware 11g.
Note:For information on upgrading from Oracle Forms Release 6i , refer to "Upgrading to Oracle Forms Services" in the Oracle Fusion Middleware Forms Services Deployment Guide.
Refer to the Oracle Fusion Middleware Forms Services Deployment Guide for detailed information about performing these tasks in Oracle Forms Services 11g:
If you deployed the Oracle Forms Services J2EE applications EAR file (
formsapp.ear) on multiple OC4J instances for load balancing and high availability purposes, then you deploy them in a similar manner on Oracle WebLogic Server.
Specifically, you can create additional managed servers and deploy the Oracle Forms Services J2EE application ear file on each server. The ear file is stored in the following location in Oracle Fusion Middleware 11g:
If you deployed the Oracle Forms Services J2EE custom application ear file (
formsapp.ear) file to override the context root or Forms servlet alias, then you should perform similar steps in the 11g Oracle WebLogic Server domain.
The Upgrade Assistant copies the FMA utility configuration files (
search_replace.properties) to the Oracle Fusion Middleware 11g destination Oracle instance and renames them so they have a
You can then manually copy the required entries from the
.10.1.2 configuration files into the Oracle Fusion Middleware 11g version of these files as needed.
After you upgrade to OracleAS Reports Services 11g, review the following sections, which provide information about typical post-upgrade tasks for OracleAS Reports Services users:
When you upgrade to Oracle Reports 11g, the security configuration is not upgraded. As a result, the security configuration of Oracle Reports 11g remains the same as it was before the upgrade.
For information about the security features available in Oracle Reports 11g and how to configure them, see "Securing Oracle Reports Services" in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.
The following sections describe some other common post-upgrade tasks to complete after upgrading to OracleAS Reports Services 11g:
Any shell scripts that are stored in the bin directory of the Oracle Reports 10g Oracle home, such as
rwserver.sh are not upgraded automatically during the upgrade process. Instead, you must change these scripts manually, as needed. After the upgrade, you can find these scripts in the following Oracle Fusion Middleware 11g directory:
OracleAS Reports Services DAT files are upgraded during the upgrade process. However, if job command entries in the DAT files contain references to old Oracle Home path names or invalid path names, then those jobs will fail. Therefore, you must reschedule any such report jobs.
In OracleAS Reports Services 10g, the in-process server target appears in the Oracle Enterprise Manager Application Server Control as
However, after you upgrade to OracleAS Reports Services 11g, the in-process server does not appear as
Reports server in Oracle Enterprise Manager Fusion Middleware Control. Instead, it appears as a Reports application, called
reports, and you can manage the in-process server target and the Reports servlet on the Reports application page.
Refer to the following sections for information about post-upgrade tasks you must perform after upgrading to Oracle Web Cache 11g:
For Oracle Fusion Middleware 11g, the Oracle Web Cache administration and invalidation passwords are saved in the Oracle Fusion Middleware credential store. In past releases, they were stored in the
webcache.xml configuration file.
However, the Oracle Web Cache upgrade process is unable to update the passwords in the credential store. These passwords are used not only for Oracle Web Cache monitoring and invalidation, but they are also used by Oracle Portal for internal communications between the two components.
As a result, you should update the Oracle Web Cache passwords in two places as soon as possible after upgrade of your Oracle Portal and Oracle Web Cache components:
For more information, see "Configuring Password Security" in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.
Set the Oracle Web Cache invalidation credentials for Oracle Portal so that Oracle Portal uses the same invalidation password as the one you modified in Oracle Web Cache.
For more information, see "Managing Oracle Web Cache" in the Oracle Portal Administrator's Guide.