Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for HP-UX Itanium

Part Number E14773-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

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

3 Upgrade

This chapter describes issues associated with upgrading your environment and your applications to Oracle Fusion Middleware 11g. It includes the following topics:

3.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

3.1.1 Patches Required to Address Specific Upgrade and Compatibility Requirements

In general, Oracle assumes that you are running the latest Oracle Application Server 10g patch sets before you begin the upgrade to Oracle Fusion Middleware 11g.

In addition, in some specific cases, you must apply an additional software patches to your Oracle Application Server 10g components before you start the upgrade process. These patches are designed to address specific interoperability issues that you might encounter while upgrading your Oracle Application Server 10g environment to Oracle Fusion Middleware 11g.

Table 3-1 lists the specific patch sets required to address specific upgrade and compatibility requirements for Oracle Fusion Middleware 11g.

For more information, refer to the following sections:

Table 3-1 Patches Required to Address Specific Upgrade and Compatibility Requirements

Patch Set Number Description and Purpose Additional Information

8404955

Before you can perform the Oracle B2B schema upgrade, you must apply this required patch to the Oracle Application Server Integration B2B 10g Release 2 (10.1.2) middle tier.

This patch set is required in order to enable the Java command that you use to export the trading partner agreements, as described in the following step.

"Task 6b: If Necessary, Upgrade the B2B Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

5746866

If the database that hosts your Oracle Application Server 10g schemas is an Oracle Database 10g (10.1.0.x) database, then make sure that this database patch (or database patch 5126270) has been applied to the 10g (10.1.0.x) database before you upgrade the database to the required Oracle Database 10g (10.2.0.4).

Note that database patch 5746866 includes patch 5126270.

"Upgrading to Oracle Database 10g Release 2 (10.2.0.4)" in the Oracle Fusion Middleware Upgrade Planning Guide

7685124

Apply this patch against Oracle Secure Enterprise Search (10.1.8.3.0) before you attempt to use Oracle Secure Enterprise Search with Oracle Portal 11g.

"Oracle Secure Enterprise Search" in the Oracle Fusion Middleware Administrator's Guide for Oracle Portal

Section 34.4, "Interoperability Issues and Workarounds"

8372141

Apply this patch on your Oracle Application Server 10g Release 3 (10.1.3.4) environment to enable interoperability between Oracle SOA Suite 10g Release 3 (10.1.3.4) and Oracle BPEL Process Manager 11g.

This patch is also referred to as the Oracle SOA Suite 10g Release 3 (10.1.3.4) Cumulative MLR #7.

"Applying Patch Sets to Address Specific Upgrade Interoperability Issues" in the Oracle Fusion Middleware Upgrade Planning Guide

"Upgrading Oracle SOA Suite Client Applications" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

6522654

Apply this patch to your Oracle Database before you attempt to upgrade your Oracle BAM schema.

If you do not apply this patch to your Oracle Database 10g (10.2.0.3), 10g (10.2.0.4), or Oracle Database 11g (11.1.0.7) before performing the schema upgrade, you will likely see the following error:

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

The description for this patch on My Oracle Support is "USING DATA PUMP THROUGH DBLINK CAUSED DATA CORRUPTION FOR CLOB VALUES".

"Task 6c: If Necessary, Upgrade the BAM Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

7675269

Apply this patch to prevent the occurrence of an ORA-01591 error in an Oracle Real Application Clusters (RAC) 11g (11.1.0.7) database.

This error can occur for rows locked by transactions which were in the middle of two-phase commit.

The description of this patch on My Oracle Support is "ODAC 2008:RAC NODE AFFINITY: DISTRIBUTED TXN ABORTS WITH ORA-01591."

"Upgrading and Preparing Your Databases" in the Oracle Fusion Middleware Upgrade Planning Guide


3.1.1.1 Obtaining Patches and Support Documents From My Oracle Support (Formerly OracleMetaLink)

To obtain a patch, log in to My Oracle Support (formerly OracleMetaLink), click Patches and Updates, and search for the patch number:

http://metalink.oracle.com/

To obtain a support note or document, log in to My Oracle Support and enter the support note number in the Quick Find search field at the top of the My Oracle Support window and search the Knowledge Base for the note number.

3.1.2 Additional Database Requirement for Oracle Portal Upgrade

Section 3.6.4.3 of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer provides a list of database parameters you should verify before upgrading to Oracle Portal 11g.

In addition to the parameters listed in that section, you should also verify that the Processes initialization parameter is set to at least 500.

3.1.3 Clarification of Oracle Portal Compatibility Issues During Upgrade

As described in Section 4.3.2 of the Oracle Fusion Middleware Upgrade Planning Guide and in Section 3.5.1 of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer, there are some interoperability issues to consider when upgrading Oracle Portal to 11g.

To clarify the issues, consider the steps required to upgrade Oracle Portal:

  1. Install Oracle Portal against the 10g PORTAL schema.

  2. Run the Upgrade Assistant to upgrade your Oracle Portal 10g middle tier to 11g.

  3. Run the Upgrade Assistant to upgrade the PORTAL schema to 11g.

After you install Oracle Portal against the 10g PORTAL schema, you must then run the Upgrade Assistant to upgrade the Oracle Portal middle tier. After performing the middle-tier upgrade, Oracle Portal is operational, although only 10g features will be available.

Later, you can use the Upgrade Assistant to upgrade the PORTAL schema to 11g. After the PORTAL schema is upgraded, then your upgraded Oracle Portal 11g instance will be fully operational with 11g features.

3.1.4 Unable to Read Composite Model Error During SOA Application Upgrade

The Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF describes how Oracle JDeveloper 11g will automatically upgrade specific features of your Oracle SOA Suite 10g applications to 11g.

However, if you see the following error while upgrading your application in JDeveloper 11g, then you can safely ignore the error. Your application will be upgraded, but you will need to create a new SOA-SAR deployment profile after the application upgrade. And use this newly created profile for deploying SOA composite:

SEVERE: Unable to read composite model for project project_name

For more information, see 43.2, "Deploying a Single SOA Composite in Oracle JDeveloper," in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

3.1.5 Oracle BAM Upgrade Issues

The following sections provide information about specific issues related to upgrading Oracle BAM 10g to Oracle BAM 11g:

3.1.5.1 Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)

Before you upgrade the Oracle BAM 11g schema to 11g, you must first apply patch 6522654 to your Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7).

If you do not apply this patch, then you will likely experience the following error during Oracle BAM schema upgrade:

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

For more information, see Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements".

3.1.5.2 Dependent Alerts Do Not Upgrade Correctly

When an alert in Oracle BAM 10g is dependent upon another alert, the dependent alert keeps a reference to the parent alert with a GUID reference. When such an alert is exported from 10g it will contain a GUID reference to the parent alert, and import to an Oracle BAM 11g system is not successful.

The following modification to the exported alert definition file can be used as a workaround for import to an Oracle BAM 11g system.

Edit the exported file contents of the dependent alert from the Oracle BAM 10g system, and modify the following element containing reference to parent alert.

Change this:

<param name="RuleID" order="0">
  //private:weblogic/Rule/624567ffe84de34c-6e6bdbaa120eb7f6ea6-8000
</param>

To this:

<param name="RuleID" order="0">
  ParentAlertName
</param>

In other words, the GUID reference for parent alert must be replaced by the parent alert's name.

3.1.5.3 Upgrading Images in Oracle BAM Reports

Any images you used in Oracle BAM 10g are not upgraded automatically to Oracle BAM 11g. As a result, you must manually move any of your Oracle BAM images to the Oracle BAM 11g before the images can be used in your Oracle BAM 11g reports.

  • If you uploaded background images or inserted images into columnar views, you have two options to upgrade the images to Oracle BAM 11g:

    • Option 1: Copy all image files from the Oracle BAM 10g location to the Oracle BAM 11g location.

      Oracle BAM 10g location:

      ORACLE_HOME\BAM\images
      

      Oracle BAM 11g location:

      BAM_DOMAIN_HOME/servers/BAM_Managed_Server/
         /tmp/_WL_user/oracle-bam-11.1.1/
         /tmpdir/war/buildnumber/Images
      

      Note that the Images directory in Oracle BAM 11g is case-sensitive and must begin with an uppercase "I".

    • Option 2: Edit the Oracle BAM 11g reports and re-upload the image files.

      For more information, see "Setting Backgrounds for Reports" in the Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring.

  • If you manually placed image files in the "images" directory in Oracle BAM 10g and you referenced them in your Oracle BAM 10g HTML calculations, then do the following:

    1. Copy the Oracle BAM 10g directory to the Oracle BAM 11g directory location as described in Option 1 provided earlier in this section.

    2. Edit your Oracle BAM 11g HTML calculation expressions and change any folder reference images to Images.

  • If you manually placed image files in a custom folder in Oracle BAM 10g and you referenced them in HTML calculations, then you must do the following:

    1. Create custom folder in 11g relative to:

      BAM_DOMAIN_HOME/servers/BAM_Managed_Server/
         /tmp/_WL_user/oracle-bam-11.1.1/
         /tmpdir/war/buildnumber/Images
      
    2. Copy the 10g images to this new location.

    3. Edit your Oracle BAM 11g HTML calculation expressions and change any folder reference images to Images.

3.1.6 Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema

If you receive an error when using the Upgrade Assistant to upgrade the Oracle Internet Directory schema from 10g Release 2 (10.1.2.3) to 11g, then verify that the ODS 10g schema is valid.

To view the status of the Oracle Application Server 10g schemas in your database, use the following SQL command:

SELECT comp_id, version, status FROM app_registry;

If the output from this command shows that the ODS schema is INVALID, then use the instructions in the following My Oracle Support document to install and configure Referential Integrity:

730360.1, "Referential Integrity in Oracle Internet Directory Version 10.1.2.3"

After performing the instructions in the support document, then retry the Oracle Internet Directory schema upgrade.

3.1.7 Restore From Backup Required If Upgrade Fails During a Colocated Oracle Internet Directory and Oracle Directory Integration Platform Upgrade

If you are using the Upgrade Assistant to upgrade both Oracle Internet Directory and Oracle Directory Integration Platform, consider the following.

If the Oracle Internet Directory upgrade fails, then before you can run the Upgrade Assistant again, you must restore your Oracle Internet Directory 10g backup before you can run the Upgrade Assistant again. Otherwise, the Upgrade Assistant will not attempt to upgrade Oracle Directory Integration Platform.

3.1.8 Cannot Verify Oracle Forms Services Upgrade When Oracle HTTP Server is Running On a Separate Host

If you use the Upgrade Assistant to upgrade an Oracle Forms Services instance that does not include a local instance of Oracle HTTP Server, then the Verify feature of the Upgrade Assistant cannot verify that the upgrade was successful. Instead of reporting that the upgrade was successful, the Verify feature will report that the server is unavailable. This verification error may not be valid if the Oracle HTTP Server is installed and configured on a different host than the Oracle Forms Services instance.

3.1.9 WebCenter Security Upgrade Release Notes

The following bugs/release notes relate to security changes for Custom WebCenter applications upgrading from 10.1.3.x:

3.1.9.1 RowSetPermission check fails with compatibility flag set

In 10.1.3, the ADF framework performed rowset, attribut,e and method permission checks in addition to page permission checks. If a 10.1.3 application grants 'read' permission on the rowset and attribute and 'invoke' permission on the method for all users, then the application will behave as expected in 11R1 without any additional setup.

However, if the 10.1.3 application was designed to allow only certain users to view the rowset, attribute, or invoke method, then a special flag needs to be set to support this style of security. If this flag is not set, then anyone who has page access can view attributes and rowsets and invoke methods since in 11R1 the permission check is performed only on pages and taskflows. The flag must be set for each application in the adf-config.xml file.

<sec:adf-security-child
xmlns="http://xmlns.oracle.com/adf/security/config">
    <JaasSecurityContext
initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
                         authorizationEnforce="true"/>
                <contextEnv name="oracle.adf.security.metadata"
value="false"/>
    <CredentialStoreContext
credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
   </sec:adf-security-child> 

3.1.9.2 Grants not migrated properly if application contains grants without permissions

Grants are not migrated properly if a 10.1.3 application contains grants without any permissions. Developers should inspect the app-jazn-data.xml file in the 10.1.3 workspace and remove any grants that have empty permission set prior to performing the migration.

3.1.10 Upgrade Assistant Upgrades Only Enabled Oracle Identity Federation Resources

If you have configured more than one data store, Authentication Engine, or SP Engine in your Oracle Identity Federation environment, note that the Upgrade Assistant will upgrade only the enabled resources to 11g. Any additional data stores, authentication engines, or SP engines that are are configured, but not enabled, will not be upgraded to the new Oracle Identity Federation 11g environment.

After you upgrade, you can reconfigure the resources that were not upgraded. In addition, unlike Oracle Identity Federation 10g, you can enable more than one of these resources at a time in 11g.

3.1.11 Service Name Is Required When Using ebMS with Oracle B2B

Because the Service Name parameter is required when using the ebMS protocol in Oracle B2B 11g, you may need to provide a value for this field after importing 10g data.

With the agreement in the draft state, update the field on the Partners > Documents tab. When you select a document definition that uses the ebMS protocol, the Document Type > ebMS tab appears in the Document Details area. The Service Name field is on this tab.

3.1.12 Converting Wallets to Keystores for Oracle B2B 11g

After upgrading to Oracle B2B 11g, use the orapki pkcs12_to_jks option to replace the entire keystore. Convert the wallet to a keystore as follows:

  1. Back up the original keystore.

  2. Use the orapki wallet pkcs12_to_jks option to convert to the keystore.

  3. Use keytool -list to list the aliases and verify.

  4. Use keytool -importkeystore to import the converted keystore to the backup of the original keystore (as done in Step 1)

3.1.13 Migrating the Oracle HTTP Server Wallet After Upgrading a Secure Oracle HTTP Server

If you configured Secure Socket Layer (SSL) for the communications between Oracle HTTP Server and Oracle Web Cache, and you upgraded both Oracle HTTP Server and Oracle Web Cache to 11g, consider the following.

When you run the Oracle Fusion Middleware Upgrade Assistant, it configures Oracle Web Cache 11g to use the SSL wallet from your Oracle Web Cache 10g environment instead of the default wallet that gets installed with Oracle Web Cache 11g.

As a result, if you did not select the Use source Oracle home ports in destination option in the Upgrade Assistant, then you must perform one of the following actions:

  • If you want to keep using the same SSL wallet that you used in your Oracle Application Server 10g environment, then export all your certificates from the wallet used by Oracle HTTP Server 10g and import those certificates into the wallet used by Oracle HTTP Server 11g.

    You can use any available utility such as the WebLogic Scripting Tool (WLST) or Fusion Middleware Control for this task.

    For more information, see Section 7.4.7, "Common Certificate Operations," in the Oracle Fusion Middleware Administrator's Guide.

  • If you want to use a new SSL wallet for Oracle Fusion Middleware 11g, then change the SSL settings for Oracle Web Cache 11g connections to Oracle HTTP Server 11g to use the default 11g wallet.

    For more information, see Section 5.4.3, "Task 3: Configure SSL Settings for Oracle Web Cache Connections to Origin Servers," in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

3.1.14 Additional Oracle Identity Federation Post-Upgrade Tasks

The following additional post-upgrade tasks should be performed after upgrading to Oracle Identity Federation 11g, in addition to those described in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management:

  • If you are have configured Oracle Identity Federation 10g to use the SAML 1.x/WS-FED protocol, then after you upgrade to Oracle Identity Federation 11g, you must set a default single sign-on identity provider.

    For more information, see "Configuring Service Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

  • Export the Identity Provider self-signed certificate to the service provider

    The procedure you use to perform this task varies, depending on whether your service provider is a 10g or 11g service provider:

    • If you are using a 10g service provider, then refer to "Exporting the IdP's self-signed certificate to the SP" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN):

      http://www.oracle.com/technology/documentation/
      
    • If you are using an 11g service provider, then refer to "Set Up Single Sign-On for SAML 1.x and WS-Federation" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

  • If you are using an 11g Identity Provider and a 10g service provider, and you are using the SAML 1.x/WS-FED protocol, then you configure the 10g service provider.

    Specifically, for the 10g service provider, you must change the "Signing Certificate Subject DN" and "Signing Certificate Issuer DN" to 11g IdP format, which is of the form "CN=<host> Signing Certificate".

    For more information, see "Configure This Domain as a Source/Identity Provider" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN).

  • Enable "Send Signed Assertion" in Oracle Identity Federation 10g, or disable "Require Signed Assertions" in Oracle Identity Federation 11g.

    This task is necessary because in 10g, signed assertions are disabled by default, and in 11g, signed assertions are enabled by default.

    Depending whether you perform this task in 10g or 11g, refer to one the following:

    • "Configuring Service Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

    • Section 6.5.5, "Add Assertion Profile" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN).

3.1.15 Recommendation When Upgrading Oracle JDeveloper 10g Projects

As described in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF, when you open a Oracle JDeveloper 10g workspace (.jws) file in Oracle JDeveloper 11g, the Oracle JDeveloper migration utility upgrades the application—including all the projects within the application—to the new Oracle JDeveloper 11g format.

You can also upgrade individual Oracle JDeveloper 10g project (.jpr) files. However, Oracle recommends you take the following steps when upgrading .jpr files:

  1. Start Oracle JDeveloper 11g.

  2. Create a new application in Oracle JDeveloper 11g.

  3. Open the .jpr file from within the application so it becomes a project within the newly created application.

3.2 Additional Component-Specific Upgrade Release Notes

In addition to the upgrade-related release notes available in this chapter, refer to the component-specific chapters for upgrade-related information. For example, you can find additional upgrade-relatd release notes in the Oracle Identity Management chapter of these Release Notes.

3.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

3.3.1 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF:

3.3.1.1 Incorrect Version Reference in Section 9.6.5.2

The first sentence in Section 9.6.5.2, "Invoking Web Services from Oracle BAM Alerts" is incorrect. It should read as follows:

"In Oracle BAM 10g, you could configure alerts to invoke a Web service by invoking an external action. This method of using alerts to invoke a Web service is no longer supported in Oracle BAM 11g."

3.3.1.2 Additional Post-Upgrade Steps for Oracle BAM

See Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF for information about upgrading an existing Oracle BAM installation. The following statements are additions to the information contained in that guide.

Users and Groups

After the Oracle BAM schema is updated, any Oracle BAM 10g users will appear in the Oracle BAM Administrator as inactive if they do not exist in the 11g security provider. However, you can use Oracle BAM Administrator to remap 10g users to new Oracle BAM 11g users.

For more information, see Section 23.3.7, "Managing Oracle BAM Object Ownership," in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

You may need to address the following for users and groups:

-Reset any Shared Folder permissions

-Reset any Data Object and Data Object folder permissions

-Reset any Distribution Lists

-Reset Security Filters

-Reset Alerts actions to users and groups

Alerts

Some Oracle BAM alert actions were removed in Oracle BAM 11g, and after upgrading, any alerts using them may become invalid.

The Run a Plan action was removed because Oracle BAM replaced Enterprise Link with Oracle Data Integrator, Which uses the Run an ODI Scenario alert action.

Enterprise Message Sources

Enterprise Message Sources definitions have changed from Oracle BAM 10g to Oracle BAM 11g, and must be recreated.

3.3.1.3 Modified Procedure for Upgrading Domain Value Maps (DVMs) and Cross References with the Oracle SOA Suite Command-Line Upgrade Tool

Section 9.3.6.7, "Upgrading Domain Value Maps (DVMs) and Cross References with the Oracle SOA Suite Command-Line Upgrade Tool" explains how to upgrade DVMs and Cross-References with the Oracle SOA Suite command-line upgrade tool.

However, due to a change in the way Metadata archive (MAR) files are deployed, Task 3 , "Import the archive file into MDS repository" in that procedure should be replaced with the following steps:

  1. Start Oracle JDeveloper 11g and create a new application.

  2. Import the Oracle SOA Suite archive into a new SOA project:

    1. From the Oracle JDeveloper 11g File menu, select Import, then SOA Archive into SOA Project.

    2. In the Create SOA Project from SOA Archive Dialog Box, select JAR Options in the navigation tree on the left, and then click Browse to locate the sca_XrefDvmFiles10g_rev1.0.jar file that you created previously in this procedure.

    3. Select File Groups > Project Output from the navigational tree on the left, and enter XrefDvmFiles10g in the Target Directory in Archive field.

    4. Click OK to create the new SOA project, which is called XrefDvmFiles10g.

      The new project consists of an empty composite, along with the upgraded XRef and DVM files.

  3. Create a metadata archive (MAR) file for the application, which includes the XRef and DVM metadata, and then deploy the MAR to the Oracle WebLogic Server domain.

    For information about creating a MAR, see section 43.4, "Deploying and Using Shared Metadata Across SOA Composite Applications," in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

3.3.2 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management:

3.3.2.1 When Upgrading Oracle Identity Federation, Configuring Oracle Single Sign-On Is No Longer Required Before Running the Upgrade Assistant

Section 6.3, "Task 3: Install and Configure Oracle Identity Federation 11g" in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management describes how to install and configure Oracle Identity Federation in preparation for an upgrade to 11g.

In this procedure, Task 3d, "Configure Oracle Single Sign-On With Oracle HTTP Server 11g" is no longer necessary, since it is now performed automatically when you later run the Upgrade Assistant.

3.3.3 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer:

3.3.3.1 Additional Configuration Step for Oracle Reports When Using 10g Ports During Upgrade

Section 3.6.3.2, "Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance" in the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer describe some tasks you should consider if you are same ports in 11g that you were using in 10g.

In particular, it explains that if you have problems monitoring your upgraded Oracle Reports in Fusion Middleware Control, then you should modify the Agent-Monitored Target properties for the Oracle Reports component. It explains that you must change both the HTTP Port property and the port identified in the Servlet URL property to reflect the 10g Oracle HTTP Server port.

Note that in addition, you must also update the Server property for the WLS_REPORTS J2EE application. This is because, during the upgrade, the Oracle Reports 11g in-process server is renamed to use the same name as the 10g in-process server.