|
Oracle® Application Server 10g Upgrading to 10g (9.0.4)
10g (9.0.4) for UNIX Part No. B10429-01 |
|
|
|
|
Oracle® Application Server 10g Upgrading to 10g (9.0.4)
10g (9.0.4) for UNIX Part No. B10429-01 |
|
|
|
|
This chapter describes the process of upgrading the middle tier and Infrastructure installation types from Oracle9i Application Server Release 2 (9.0.2) or Release 2 (9.0.3), also referred to as the source Oracle home or source instance, to Oracle Application Server 10g (9.0.4), also referred to as the destination Oracle home or destination instance. The middle tier comprises application server instances that process requests from the client tier, and may access or change data in the database to complete a request. The Infrastructure, usually installed on a different computer, provides centralized security and management services and a metadata repository to one or more application server instances on the middle tier.
This chapter contains these major sections:
Section 1.1, "The Oracle Application Server Upgrade Process"
Section 1.2, "The Middle Tier Upgrade Process"
Section 1.3, "The Infrastructure Upgrade Process"
Section 1.4, "OracleAS Upgrade Assistant Upgrade Paths"
This section describes the process of upgrading a distributed Oracle Application Server environment. A distributed environment is one in which multiple middle tiers access an Infrastructure, across multiple Oracle homes. A detailed discussion of the middle tier and Infrastructure portions of the upgrade process is provided in this chapter.
A distributed Oracle Application Server environment comprises one or more middle tiers and an Infrastructure, and is distributed across multiple Oracle homes. Upgrading such an environment involves upgrading each middle tier, and then upgrading the Infrastructure.
|
Note: The Infrastructure itself comprises two units: the Metadata Repository and Identity Management (See Section 2.1, "Oracle Application Server Compatibility" for valid upgrade sequences). Figure 1-1 illustrates the process of upgrading a distributed environment, depicting the Infrastructure as a single unit for simplicity’s sake. Although you can upgrade Identity Management and the Metadata Repository in any order, the middle tier upgrade must precede the Metadata Repository upgrade. |
Before the upgrade, middle tiers and Infrastructure are Release 2 (9.0.2) or Release 2 (9.0.3).
One middle tier is upgraded to 10g (9.0.4), and continues to use the Release 2 (9.0.2) infrastructure.
The remaining middle tiers are upgraded to 10g (9.0.4), and continue to use the Release 2 (9.0.2) Infrastructure.
The Release 2 (9.0.2) Infrastructure is upgraded to 10g (9.0.4).
Figure 1-1 Upgrading a Distributed Oracle Application Server Environment
The middle tier upgrade process is illustrated in Figure 1–2. The middle tier upgrade consists of the following steps:
The Release 2 (9.0.2) or Release 2 (9.0.3) middle tier installation resides on its computer, containing applications and configuration data.
A 10g (9.0.4) middle tier installation of the same installation type as the source installation is installed into a new Oracle home on the same computer.
The OracleAS Upgrade Assistant, a tool installed with Oracle Application Server that automates most middle tier component upgrade tasks, is executed. It copies the applications and configuration data from the source middle tier installation to the 10g (9.0.4) installation. Manual tasks may be necessary to complete the upgrade of some configurations.
(Optional) The source installation is decommissioned.
The Oracle Application Server Infrastructure provides centralized security and management services and a metadata repository to one or more application server instances. It is installed into a separate Oracle home from the application server instances, typically on a separate computer.
|
See Also: Oracle Application Server 10g Administrator's Guide |
The Infrastructure comprises these parts:
Identity Management — Oracle Application Server Single Sign-On, Oracle Internet Directory, Oracle Delegated Administration Services, Oracle Directory Integration and Provisioning, and Oracle Application Server Certificate Authority.
Metadata Repository — Product metadata schemas (used by middle tier components such as OracleAS Portal and Oracle Application Server Wireless) Identity Management schemas (used by Identity Management components) and management schemas (used by components such as DCM)
The Oracle Application Server Infrastructure comprises these pieces: Identity Management (the Oracle Internet Directory and Oracle Application Server Single Sign-On) and the Metadata Repository (comprising multiple schemas within the underlying database).
The Oracle Application Server Upgrade Assistant is not used to upgrade the Infrastructure.
|
Notes: The illustrations below show an abstraction of Identity Management and the Metadata Repository, depicting the phases of the overall Infrastructure upgrade.However, Identity Management consists of the Oracle Internet Directory and Oracle Application Server Single Sign-On binaries and their schemas in the Metadata Repository. In practice, Identity Management schemas in the Metadata Repository are upgraded in the Identity Management upgrade process, whereas all other schemas comprising the Metadata Repository are upgraded using individual scripts. See Section 5.1.2, "Understanding the Identity Management Upgrade Processes" for illustrations. Identity Management and the database containing the Metadata Repository can be on different computers. |
Phases of the Infrastructure upgrade are listed below. At each phase, the configuration is operable. The Infrastructure can operate in the hybrid states described in Steps 2 and 3, and Steps 3 and 4 may be reversed.
The Release 2 (9.0.2) Oracle Application Server Infrastructure contains a database of version 9.0.1.3 by default.
A patch is applied to upgrade the database to version 9.0.1.5.
The Metadata Repository (schemas other than those for Oracle Internet Directory and Oracle Application Server Single Sign-On) is upgraded to 10g (9.0.4).
Identity Management is upgraded to 10g (9.0.4).
Figure 1-4 Alternate Infrastructure Upgrade (Steps 3 and 4 Reversed)
This section describes the middle tier upgrade paths and requirements, and lists the components upgraded for each installation type. Alternative upgrade paths and exception cases are also discussed.
The OracleAS Upgrade Assistant can upgrade a middle tier from one Oracle home to another on the same computer, between these releases:
Release 2 (9.0.2) to 10g (9.0.4)
Release 2 (9.0.3) to 10g (9.0.4)
The OracleAS Upgrade Assistant will not display selections for Oracle homes of releases other than these.
The 10g (9.0.4) middle tier must be associated with the same Metadata Repository and Oracle Internet Directory as the Release 2 (9.0.2) middle tier.
The OracleAS Upgrade Assistant upgrades these components within each installation type:
Table 1-1 Components Upgraded by the OracleAS Upgrade Assistant (in processing order)
| Component Upgraded by OracleAS Upgrade Assistant | Included in J2EE & Web Cache Installation Type? | Included in Portal & Wireless Installation Type? | Included in Business Intelligence & Forms Installation Type? |
|---|---|---|---|
| Oracle Process Management and Notification
|
Yes | Yes | Yes |
| Instance Configuration (iasschema.xml) | Yes | Yes | Yes |
| Oracle Application Server Containers for J2EE
|
Yes | Yes | Yes |
| Oracle HTTP Server
|
Yes | Yes | Yes |
| Oracle Application Server Web Cache
|
Yes | Yes | Yes |
| mod_plsql | Yes | Yes | Yes |
| Oracle Enterprise Manager (targets.xml) | Yes | Yes | Yes |
| Oracle Application Server Web Services UDDI Registry | No | Yes | Yes |
| Oracle Ultra Search
|
No | Yes | Yes |
| Oracle Application Server Portal (Middle Tier) | No | Yes | Yes |
| Oracle Application Server Wireless
|
No | Yes | Yes |
| Oracle Application Server Forms Services
|
No | No | Yes |
| Oracle Application Server Discoverer
|
No | No | Yes |
| Oracle Application Server Reports Services
|
No | No | Yes |
The OracleAS Upgrade Assistant can perform upgrades between Oracle Application Server instances of the same installation type only. For example, if you have a Release 2 (9.0.2) J2EE and Web Cache installation, you must upgrade to J2EE and Web Cache in 10g (9.0.4).
Upgrading the Unified Messaging installation type from Release 2 (9.0.2) UNIX systems is a special case, because Unified Messaging is not part of Oracle Application Server 10g (9.0.4). If you upgrade a Unified Messaging installation type, the OracleAS Upgrade Assistant applies the configuration to the Business Intelligence and Forms installation type in 10g (9.0.4).
See the Oracle Collaboration Suite to determine the upgrade path for a Unified Messaging installation.
If you have applications or configuration elements whose upgrade requirements are not addressed by the OracleAS Upgrade Assistant, you may use one of the following alternative paths:
If there are applications deployed in Oracle Application Server Containers for J2EE (OC4J) instances of the"standalone" type—that is, the OC4J that is available for download from Oracle Technology Network in zip format—you must manually redeploy and reconfigure them.
|
Note: Standalone OC4J applications should not be configured in an Oracle Application Server Oracle home. Standalone applications should be redeployed in a managed OC4J instance in the 10g (9.0.4) Oracle home. See Section 3.3, "Upgrading a Standalone OC4J Instance". |
To upgrade a standalone instance of OracleAS Web Cache Release 2 (9.0.2 or 9.0.3) to Oracle Application Server 10g (9.0.4), perform the steps described in Section 3.4, "Upgrading a Standalone OracleAS Web Cache Instance" before you invoke the OracleAS Upgrade Assistant.
To upgrade from Release 1 to Release 2, follow the instructions in Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2) in the Oracle9iAS Release 2 (9.0.2) documentation library.
To upgrade from Release 1 (1.0.2.2) to 10g (9.0.4), you must first upgrade from Release 1 (1.0.2.2) to Release 2 (9.0.2), and then upgrade from Release 2 (9.0.2) to 10g (9.0.4).
To upgrade Oracle Application Server Discoverer from Release 1 (1.0.2.2) to 10g (9.0.4), follow the instructions in the Oracle Application Server Discoverer Configuration Guide in the Oracle Application Server documentation library.
The upgrade of applications that use JServ is not discussed in this guide. The material in the section titled "Migrating JServ to OC4J" in Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2), in the Oracle9iAS Release 2 (9.0.2) documentation library, may be of some help in adapting such applications to the Oracle Application Server Containers for J2EE servlet environment in Oracle Application Server 10g (9.0.4).
You can expand to a larger (i.e., containing more components) middle tier installation type. For example, you can expand a J2EE and Web Cache middle tier to a Portal and Wireless middle tier.
To expand a middle tier in conjunction with an upgrade:
Upgrade the existing middle tier from Release 2 (9.0.2) or Release 2 (9.0.3) to 10g (9.0.4).
Expand the upgraded middle tier.
|
 Copyright © 2003 Oracle Corporation All rights reserved |
|
