2 Upgrading Oracle Application Server

The upgrade of Oracle Application Server 10g (9.0.4) to 10g release 2 (10.1.2) involves upgrade of all the components from version 9.0.4 to 10.1.2.0.2. It is then followed by application of the 10.1.2.2 patch set.

In Oracle Application Server 10g release 2 (10.1.2) on hp Tru64 UNIX, it is mandatory to apply 10g release 2 (10.1.2) patch set 2 (10.1.2.2.0) after upgrading the software from Oracle Application Server release 10g (9.0.4) to Oracle Application Server 10g release 2 (10.1.2).

For more information about upgrade tools and processes, refer to Oracle Application Server Upgrade and Compatibility Guide for UNIX.

The Oracle Application Server 10g release 2 (10.1.2) patch set 2 (10.1.2.2.0) ships with the media pack. You can also download the patch set from OracleMetaLink by using patch number 4960210 at

https://metalink.oracle.com

To apply the patch, you must follow the instructions provided in the readme.html file that is shipped with the patch.

Note:

Oracle Business Intelligence Discoverer is not supported on Oracle Application Server 10g release 2 (10.1.2) on hp Tru64 UNIX. Therefore, ignore any upgrade steps listed for Oracle Business Intelligence Discoverer product and schema in Oracle Application Server Upgrade and Compatibility Guide.
Oracle Application Server Portal 10.1.2.0.2 or 10.1.2.2 is no longer supported with Oracle Application Server 10g release 2 (10.1.2). Therefore, you must upgrade it to 10.1.4.1.0.

Only Oracle Application Server Portal 10g (10.1.4.1.0) is supported with the release of Oracle Application Server 10g release 2 (10.1.2) for hp Tru64 UNIX. You must follow the steps mentioned in the subsequent sections to upgrade to Oracle Application Server Portal 10g (10.1.4.1.0) from 9.0.4.

This section contains the following subsections:

Section 2.1, "Upgrade and Validation Tasks"
Section 2.2, "Post-Upgrade Tasks"

2.1 Upgrade and Validation Tasks

The following sections describe the upgrade and validation tasks.

Step 1: Upgrading the Middle-Tier

The following steps describe the upgrade tasks:

Install the 10.1.2.0.2 Middle-Tier pointing to the 9.0.4 Infrastructure.
Run the Oracle Application Server Upgrade Assistant on Middle-Tier by using the iasua.sh command from the destination Oracle home location. For example:
```
DESTINATION_ORACLE_HOME/upgrade/iasua.sh
```
For more information about OracleAS Upgrade Assistant and Middle -Tier, refer to Section 4.4, "Task 3: Run the OracleAS Upgrade Assistant" and Chapter 4, "Upgrading the Middle-tier" respectively, of Oracle Application Server Upgrade and Compatibility Guide.

Step 2: Validating the Middle-Tier

The following steps describe the validation tasks:

Verify that the Middle-Tier components have been updated successfully by checking the URLs of specific applications and components on the upgrade instance.
Verify that the Oracle HTTP Server is accessible on the same host and port as in the previous release by entering the URL. For example,

http://midtierhost.mycompany.com:7777
Verify that the URLs for the applications you worked with the previous release are accessible and functional.

Step 3: Upgrading Oracle Identity Management

Install 10.1.2.0.2 Infrastructure in the upgrade mode.

For more information, refer to Chapter 5, "Upgrading Identity Management Services" of Oracle Application Server Upgrade and Compatibility Guide.

Step 4: Validating Oracle Identity Management

To validate the installation, log in to Oracle Single Sign-On, Oracle Application Server Certificate Authority, and Oracle Delegated Administrative Services by using the ORCLADMIN user name. If you are able to log in successfully, then the OracleAS Single Sign-On connectivity, Oracle Application Server Certificate Authority, Oracle Internet Directory, and Oracle Delegated Administrative Services are properly functioning.

Step 5: Upgrading OracleAS Metadata Repository

Run the mrua.sh from OracleAS 10.1.2.0.2 OracleAS Metadata Repository Upgrade assistant CD from the MRUA_CD_ROOT_DIRECTORY/mrua location to upgrade the component schema version of OracleAS Metadata Repository to 10.1.2.0.2.

For more information, refer to Chapter 7, "Upgrading the OracleAS Metadata Repository" of Oracle Application Server Upgrade and Compatibility Guide.

Note:

You must review the OracleAS Metadata Repository Upgrade Assistant logs and check for errors after running mrua.sh. Refer to Section 7.4.7,"Reviewing the MRUA Log Files" of Oracle Application Server Upgrade and Compatibility Guide for more information about reviewing the OracleAS Metadata Repository Upgrade Assistant (MRUA) logs.

Step 6: Validating OracleAS Metadata Repository

To verify the success of the OracleAS Metadata Repository upgrade, use the following SQL query:

SELECT comp_id,version,status FROM APP_REGISTRY

Note:

You must ensure that the component OracleAS Single Sign-On version is 10.1.2.2.0, and that the Oracle Internet Directory, wireless schemas, and portal schemas are at version 10.1.2.0.2. After completing the upgrade and running the utlrp.sql command, there should not be any invalid database objects.

Step 7: Upgrading OracleAS Portal

If you are using OracleAS Portal 9.0.4.1, then you must upgrade to OracleAS Portal 10.1.4.1.

Run the mrua.sh command from the OracleAS Portal release 10.1.4 OracleAS Metadata Repository Upgrade assistant CD to upgrade the portal schema to 10.1.4 from the /MRUA_CD_ROOT_Directory/mrua location.

Important:

Oracle AS portal 10.1.2.0.2 or 10.1.2.2 is no longer supported in this release.
You must check the upgrade/temp/portal/upgrade.log file for errors after upgrade. You cannot run OracleAS Portal until you have completed a successful upgrade. A successful upgrade has zero errors in the upgrade log file, upgrade.log. Any portals running after an upgrade that was not clean are not supported by Oracle.

For more information, refer to Oracle Application Server Portal Installation and Upgrade Guide 10g Release 2 (10.1.4).

Step 8: Validating OracleAS Portal

The following steps describe the validation tasks:

To access the upgraded OracleAS Portal instance, specify the URL in a browser. The format of the URL has been changed in OracleAS Portal 10.1.4, which is as follows:

http://host:port/portal/pls/portal_DAD
Verify that the portal schema version is 10.1.4.0, by using the following command:
```
SELECT comp_id,version,status FROM APP_REGISTRY
```

Step 9: Applying 10.1.2.2 Patch Set on Middle-Tier and OracleAS Infrastructure

It is mandatory to apply Oracle Application Server 10.1.2.2 patch set (4960210) on OracleAS Infrastructure and Middle-Tier after the upgrade.

You must apply software update to each Middle-Tier installation before applying the OracleAS Metadata Repository update to OracleAS Metadata Repository used by each Middle-Tier. For more information about applying patch set, you may refer to readme.html in the patch.

Note:

You must review OracleAS Metadata Repository Assistant logs after applying the 10.1.2.2 OracleAS Metadata Repository patch.

Step 10: Validating Middle-Tier and OracleAS Infrastructure

The following steps describe the validation tasks that should be carried out after applying the 10.1.2.2 patch set:

For Middle-Tier: Verify the Middle-Tier components and also, check the significant URLs.
For Oracle Identity Management: Test the functionality of OracleAS Single Sign-On connectivity, Oracle Delegated Admininstration Services and Oracle Application Server Certificate Authority.

For OracleAS Metadata Repository: Verify the success of the OracleAS Metadata Repository upgrade, use the following SQL query:

SELECT comp_id,version,status FROM APP_REGISTRY

Note:

You must verify that the following version requirements are addressed by the upgrade process:

- OracleAS Single Sign-On and Oracle Internet Directory are at version 10.1.2.2.0

- Portal schema version is 10.1.4.1.0

- Wireless schema version is 10.1.2.1.0

After completing the upgrade and running the utlrp.sql command, there should not be any invalid database objects.
Oracle Business Intelligence Discoverer is not supported on hp Tru64 UNIX. Therefore, any entry in the APP_REGISTRY schema can be ignored.

2.2 Post-Upgrade Tasks

Post-upgrade tasks are required to complete the upgrade process. The complete upgrade steps are documented in the Oracle Application Server Upgrade and Compatibility Guide. You must follow the steps based on the type of components, installation, and upgrade.

The following list describes some of the important post-upgrade steps:

Completing Middle-Tier Upgrade: Usually, the OracleAS Upgrade Assistant performs upgrade for Middle-Tier upgrade. However, some components might require manual adjustments. These components are Oracle HTTP Server, OracleAS Web Cache, Oracle Application Server Containers for J2EE, OracleAS Portal, OracleAS Wireless, and OracleAS Forms and Reports Services.

Refer to Task 5 in Section 4.5, "Complete the Middle-Tier Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for UNIX and follow the steps for the manual adjustments.
Completing Oracle Application Server HTTP Server Upgrade: If you make any changes related to usage of ports less than 1024, mod_sso, configuration files on non-default locations, usage of custom files and directories, and so on, on Oracle HTTP Server, then you must perform some post-upgrade steps manually.

Refer to Section, 4.6.3 "Completing the Oracle HTTP Server Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for more information.
Completing Oracle Application Server Containers for J2EE (OC4J) Upgrade: You might need to make manual adjustments after the upgrade.

Refer to Section, 4.6.4 "Completing the Oracle Application Server Containers for J2EE (OC4J) Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for more information.
Completing OracleAS Web Cache Upgrade: If the ports used by OracleAS Web Cache is less than 1024 or the upgraded Middle-Tier is a part of the OracleAS Web Cache cluster, then you must follow the steps documented for OracleAS Web Cache upgrade in Section 4.6.5, "Completing the Upgrade of OracleAS Web Cache" of Oracle Application Server Upgrade and Compatibility Guide.
Completing OracleAS Portal Middle-Tier Upgrade: If the OracleAS Portal uses a different Oracle Internet Directory (OID) than the one that Middle-Tier is registered to, then you need to reconfigure the OracleAS Portal. If there are any changes in the source deployment property file of Java Portal Development Kits (JPDK), then you need to manually apply the changes to the destination files.

Refer to Section, 4.6.6 "Completing the OracleAS Portal Middle Tier Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for more information.
Completing Oracle Application Server Reports Services Upgrade: All the customized Reports files should be updated manually to the upgraded environment. You need to also enable the Reports Services Management in Oracle Application Server Control Console and register standalone Reports Servers with Oracle Process Manager and Notification Server (OPMN) and Enterprise Manager (EM).

Refer to Section, 4.6.8 "Completing the Oracle Application Server Reports Services Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for more information.
Oracle Application Server Forms Services Upgrade: If the OracleAS Forms Services .EAR file is deployed in any other default OC4J instances, such as OC4J, OracleAS Portal, and so on, then you need to redeploy it. If the Forms*.Fmx files are present in source Oracle home directory, then you must manually copy the file to the destination Oracle home directory.

Refer to Section, 4.6.10 "Completing the Oracle Application Server Forms Services Upgrade" of Oracle Application Server Upgrade and Compatibility Guide for more information.
Oracle Identity Management Upgrade: You might need to manually update some of the Infrastructure components to complete the upgrade process. These components include Oracle Internet Directory, Oracle Single Sign-On, Oracle Certification Authority, OracleAS Wireless, and Oracle Enterprise Manager 10g Database Control.
Enabling Secure Socket Layer (SSL) for Oracle Identity Management Components: After the manual upgrade, you need to enable SSL for Oracle Single Sign-On and Oracle Delegated Administration Services.
Completing OracleAS Single Sign-On Upgrade: If the SSO server has custom configurations, third party authentication, customized login and password, and sign-off pages, then you must configure the SSO server manually.