Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle Forms and Reports
11g Release 2 (11.1.2)

Part Number E23975-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

6 Post-Upgrade Tasks After Upgrading to Oracle Forms and Reports 11g Release 2 (11.1.2)

This task involves completing the following component-specific upgrade steps:

6.1 Post-Upgrade Tasks for Oracle Forms Services

Review the following list of manual tasks that you might have to perform after upgrading to Oracle Forms and Reports 11g Release 2 (11.1.2):

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.

6.1.1 Post-Upgrade Steps After Upgrading from Oracle Forms Services 10g

Review the following list of post-upgrade tasks you might have to perform after using the Upgrade Assistant to upgrade Oracle Forms Services 10g Release 2 (10.1.2) to Oracle Forms and Reports 11g Release 2 (11.1.2):

  • Regenerate the Forms application files: fmx's, mmx's, and plx's to run on 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:

    ORACLE_HOME/forms/j2ee/formsapp.ear
    

    For more information, see "Expanding Forms Managed Server Clusters" in the Oracle Fusion Middleware Forms Services Deployment Guide.

  • 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.

    For more information, see "Custom Deployment of Forms Java EE Application" in the Oracle Fusion Middleware Forms Services Deployment Guide.

  • Manually copy any customizations to the shell scripts in the source Oracle home to the equivalent shell scripts that reside Oracle Fusion Middleware 11g Oracle instance directory.

  • The Upgrade Assistant copies the FMA utility configuration files (converter.properties and search_replace.properties) to the Oracle Fusion Middleware 11g destination Oracle instance and renames them so they have a .10.1.2 suffix.

    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.

6.1.2 Post-Upgrade Steps After Upgrading from 11g Release 1 (11.1.1)

Review the following list of manual tasks that you might have to perform after using the Upgrade Scripts to upgrade Oracle Forms Services in Oracle Fusion Middleware 11g Release 1 (11.1.1) to Oracle Fusion Middleware 11g Release 2 (11.1.2):

  • 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 can deploy it 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:

    ORACLE_INSTANCE/config/Formscomponent/forms/provision/formsapp.ear
    

    For more information, see "Expanding Forms Managed Server Clusters" in the Oracle Fusion Middleware Forms Services Deployment Guide.

  • 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.

    For more information, see "Custom Deployment of Forms Java EE Application" in the Oracle Fusion Middleware Forms Services Deployment Guide.

  • If you made any customizations to the Forms Oracle HTTP Server configuration file, forms.conf, in the source instance, then you must manually add those customizations to the equivalent file in the destination instance.

    In Oracle Forms and Reports 11g Release 2 (11.1.2), the configuration file is installed in the following location:

    ORACLE_INSTANCE/config/OHS/ohs1/modulesconf/forms.conf
    

    Note that you must restart the Oracle HTTP Server instance after you modify the forms.conf file.

    The previous bullet was added via an email from Naseer Syed on 10/05/11.

6.2 Post-Upgrade Tasks for Oracle Reports

After you upgrade from Oracle Reports 10g to Oracle Reports 11g, review the following sections, which provide information about typical post-upgrade tasks for OracleAS Reports Services users:

6.2.1 Configuring Security After Upgrade to Oracle Reports 11g

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.

6.2.2 Additional Oracle Reports Post-Upgrade Tasks

The following sections describe some other common post-upgrade tasks to complete after upgrading to OracleAS Reports Services 11g:

6.2.2.1 Modifying Oracle Reports Shell Scripts After Upgrade

Any shell scripts that are stored in the bin directory of the Oracle Reports 10g Oracle home, such as reports.sh, rwrun.sh, and 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:

ORACLE_INSTANCE/config/reports/bin

6.2.2.2 Modifying Oracle Reports DAT Files After Upgrade

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.

6.2.2.3 About the In-process Server Target After Upgrade

In OracleAS Reports Services 10g, the in-process server target appears in the Oracle Enterprise Manager Application Server Control as Reports Server.

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.

6.2.2.4 Viewing Cached Reports Output Files After Upgrade

Cached Reports output files are not upgraded to Oracle Reports 11g.

6.3 Post-Upgrade Tasks Required When Using Single Sign-On Software

If you are using single sign-on software for authentication, then in certain upgrade scenarios, you must re-register your Oracle Forms and Reports software with the single sign-on software.

Refer to the following sections for more information:

6.3.1 Scenarios That Require Regeneration of Single Sign-on Configuration Information

The following table describes the typical upgrade scenarios that require the re-generation of the single sign-on client access files after the upgrade to Oracle Forms and Reports 11g Release 2 (11.1.2).

Table 6-1 Upgrade Scenarios That Require Regeneration of Single Sign-On Configuration information

Upgrade Scenario Description

Upgrading from Oracle Single Sign-On 10g to Oracle Access Manager 11g

Oracle Forms and Reports 11g Release 2 (11.1.2) supports Oracle Access Manager 11g as a single sign-on alternative to your existing Oracle Single Sign-On 10g software.

For more information, see Section 1.6, "About Using Identity Management and Single Sign-On With Oracle Forms and Reports 11g Release 2 (11.1.2)".

If you install your target Oracle Forms and Reports 11g Release 2 (11.1.2) software against Oracle Access Manager 11g, then after you upgrade, you must generate new configuration information for the Oracle HTTP Server so the server can connect to Oracle Access Manager, instead of Oracle Single Sign-On 10g.

Similarly, if you later upgrade from Oracle Single Sign-On 10g to Oracle Access Manager 11g, then you must perform the same procedure.

Configuring Oracle HTTP Server to work with Oracle Web Cache

Oracle Forms and Reports 11g Release 2 (11.1.2) does not include Oracle Web Cache. As a result, configuration data for connecting Oracle HTTP Server with your existing Oracle Web Cache instances is not preserved during upgrade.

For more information, see Section 1.5, "About Using the Web Tier Components with Oracle Forms and Reports 11g Release 2 (11.1.2)".

If--after upgrade--you configure your Oracle HTTP Server instance to work with your existing Oracle Web Cache instances, you must generate new configuration information for the Oracle HTTP Server so the server can connect to your single sign-on software.


6.3.2 Product-Specific Instructions for Regenerating Single Sign-On Configuration Information

The procedure you use to regenerate your single sign-on configuration information varies depends on the single sign-on software you are using, as well as the way it was configured. See the following for more information:

6.4 Post-Upgrade Tasks and Information for the Web Tier Components

Refer to the following sections for information about post-upgrade tasks you must perform for your Web Tier components after upgrading to Oracle Forms and Reports 11g Release 2 (11.1.2):

6.4.1 Reconfiguring the Connections and Ports for Oracle Web Cache

If you were using Oracle Web Cache prior to the Oracle Forms and Reports 11g Release 2 (11.1.2) upgrade, you can continue to use your existing Oracle Web Cache instance. However, you must reconfigure both Oracle Web Cache and Oracle HTTP Server after the upgrade is complete.

For more information, see "Basic Tasks for Configuring and Managing Oracle Web Cache" in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

If you are also using Oracle Single Sign-On 10g or Oracle Access Manager 11g, then after you reconfigure the ports and connections, you will likely need to re-register your installation with your single sign-on software. For more information, see Section 6.3, "Post-Upgrade Tasks Required When Using Single Sign-On Software".

In addition:

  • If you are currently using Oracle Web Cache 10g, then you can consider upgrading your Oracle Web Cache 10g installation to Oracle Web Cache 11g.

    For information on upgrading from Oracle Web Cache 10g, see "Upgrading a Java EE and Web Server Environment" in the Oracle Fusion Middleware Upgrade Guide for Java EE.

  • If you are already running Oracle Web Cache 11g, consider applying the latest 11g patch set so you are running the very latest Oracle Web Cache software.

    For information on applying the latest Oracle Fusion Middleware patch set, see the Oracle Fusion Middleware Patching Guide.

6.4.2 Additional Web Tier Component Post-Upgrade Tasks

For more information about tasks and information for Oracle HTTP Server and Oracle Web Cache after you upgrade to Oracle Fusion Middleware 11g, see "Task 5: Perform Any Required Post-Upgrade Tasks for the Web Tier Components" in the Oracle Fusion Middleware Upgrade Guide for Java EE.