| Oracle® Application Server Upgrade and Compatibility Guide 10g (10.1.4.0.1) for UNIX Part Number B28188-01 |
|
|
View PDF |
| Oracle® Application Server Upgrade and Compatibility Guide 10g (10.1.4.0.1) for UNIX Part Number B28188-01 |
|
|
View PDF |
This chapter provides information you need to understand how Oracle Identity Management 10g (10.1.4.0.1) operates with previous versions of Oracle Application Server.
Before you proceed with your upgrade, review the information in this chapter to be sure all upgraded components and features will work in your Oracle Application Server environment.
This chapter contains the following sections:
Release 3 (10.1.4.0.1) Identity Management Compatibility Issues
Release 3 (10.1.4.0.1) OracleAS Metadata Repository Compatibility Issues
Release 3 (10.1.4.0.1) Database Version Compatibility Issues
The Oracle Identity Management Release 3 (10.1.4.0.1) compatibility matrix is shown in Table 3-1. Before you use the compatibility matrix, you should be familiar with the Oracle Application Server installation types.
For example, if you want to upgrade a 10g (9.0.4) OracleAS Identity Management installation to Release 3 (10.1.4.0.1), you can use the compatibility matrix as follows:
Locate the column in the table that represents 10g (10.1.4.0.1) OracleAS Identity Management.
Locate the row that represents the type and the version of the Oracle homes you are currently running.
For example, if you are running 10g (9.0.4) middle tiers, locate the 9.0.4 Middle Tier row of the table.
The OracleAS Identity Management column of that row indicates that you can run 10g (9.0.4) middle tiers with an upgraded Release 3 (10.1.4.0.1) OracleAS Identity Management; however, there are potential problems and solutions you might have to consider before you can run this configuration.
If there are problems and solutions to consider, follow the reference in the intersecting table cell to learn more about which of the compatibility problems and solutions apply to the selected configuration.
|
Note: Some of the workarounds and issues described in this chapter are the result of incompatibilities with the version of the database used to host the OracleAS Metadata Repository. For more information, see Section 3.4, "Release 3 (10.1.4.0.1) Database Version Compatibility Issues". |
Table 3-1 Oracle Application Server Compatibility Topics
| 10.1.4.0.1 OracleAS Identity Management | 10.1.4.0.1 OracleAS Metadata Repository | |
|---|---|---|
|
9.0.4 Middle Tiers |
Supported. |
Not Supported. See Section 3.3.1. |
|
9.0.4 OracleAS Identity Management |
Not supported. See Section 3.5.3. |
Supported. |
|
9.0.4 OracleAS Metadata Repository |
Supported, but only when upgrading OracleAS Identity Management from 10g (9.0.4) or 10g Release 2 (10.1.2). See Section 3.2.1 |
Not Applicable. |
|
10.1.2.0.0 Middle Tiers |
Supported. |
Supported. |
|
10.1.2.0.0 OracleAS Identity Management |
Not supported. See Section 3.5.3. |
Supported. |
|
10.1.2.0.0 OracleAS Metadata Repository |
Supported, but only when upgrading OracleAS Identity Management from 10g (9.0.4) or 10g Release 2 (10.1.2). See Section 3.2.1 |
Not Applicable. |
|
10.1.2.0.1 Standard Edition One Middle Tier |
Supported. |
Supported. |
|
10.1.2.0.1 Standard Edition One Identity Management |
Not supported. See Section 3.5.3. |
Supported. |
|
10.1.2.0.1 Standard Edition One Metadata Repository |
Supported, but only when upgrading OracleAS Identity Management from 10g (9.0.4) or 10g Release 2 (10.1.2). See Section 3.2.1. |
Not Applicable |
|
10.1.2.0.2 Middle Tiers |
Supported. |
Supported. |
|
10.1.2.0.2 Identity Management |
Supported. |
Supported. |
|
10.1.2.0.2 Metadata Repository |
Supported, but only when upgrading OracleAS Identity Management from 10g (9.0.4) or 10g Release 2 (10.1.2). See Section 3.2.1 |
Not Applicable. |
|
10.1.3.0.0 Middle Tiers |
Supported as a security provider and for OracleAS Single Sign-On. |
Not Applicable because Oracle Application Server Release 3 (10.1.3) middle tiers do not require an OracleAS Metadata Repository. |
The following sections list the compatibility issues you should be aware of when you are installing or upgrading to 10g (10.1.4.0.1) OracleAS Identity Management in a mixed version environment:
You cannot install Oracle Identity Management 10g (10.1.4.0.1) against an existing 10g (9.0.4) OracleAS Metadata Repository.
However, when you upgrade OracleAS Identity Management to 10g (10.1.4.0.1), the upgrade procedure automatically upgrades the Identity Management schemas in the OracleAS Metadata Repository.
As a result, if you are running 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Identity Management against a 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Metadata Repository, you can upgrade OracleAS Identity Management to 10g (10.1.4.0.1) as long as the database that hosts the OracleAS Metadata Repository is a supported version.
Specifically, consider the following OracleAS Identity Management upgrade scenarios:
If you are using a colocated Infrastructure, you can upgrade OracleAS Identity Management to Release 3 (10.1.4.0.1) because in this scenario, the OracleAS Identity Management upgrade procedure automatically upgrades the database to a supported version and upgrades the OracleAS Identity Management schemas. The other component schemas, however, are upgraded and verified only if you run the Metadata Repository Upgrade Assistant (MRUA).
If you are using a non-colocated Infrastructure, you can upgrade OracleAS Identity Management to Release 3 (10.1.4.0.1), but you must first ensure that the database that hosts the OracleAS Metadata Repository is a supported version. This means you will likely have to upgrade the database first, either by using Oracle Universal Installer (if it is a seed database) or by manually upgrading the database if it is a OracleAS RepCA database.
The following sections list the compatibility issues you should be aware of when you are installing or upgrading to a Release 3 (10.1.4.0.1) OracleAS Metadata Repository in a mixed version environment:
You cannot run a Release 3 (10.1.4.0.1) OracleAS Metadata Repository with Oracle Application Server 10g (9.0.4) middle tiers.
This is because the Release 3 (10.1.4.0.1) OracleAS Metadata Repository contains the 10g Release 2 (10.1.2.0.2) component schemas, which are not compatible with 10g (9.0.4) middle tiers.
If you are upgrading from 10g (9.0.4), you must first upgrade your 10g (9.0.4) middle tiers to 10g Release 2 (10.1.2). Then, you can upgrade the OracleAS Metadata Repository to Release 3 (10.1.4.0.1).
A discussion of version compatibility is not complete without mentioning the version of the database used for the OracleAS Infrastructure components.
For information on the supported database versions for Release 3 (10.1.4.0.1), see Chapter 6, "Upgrading the Database That Hosts the OracleAS Metadata Repository".
The following sections describe the issues and workarounds you may encounter when running 10g (10.1.4.0.1) with earlier versions of Oracle Application Server:
If you install a 10g Release 2 (10.1.2) OracleAS Portal middle tier against a 10g (9.0.4) OracleAS Metadata Repository, you must run the OracleAS Upgrade Assistant from the 10g Release 2 (10.1.2) middle tier before you can access the OracleAS Portal using the 10g Release 2 (10.1.2) middle tier URL.
If you do not run the Upgrade Assistant, you can only access Portal using the 9.0.x middle tier URL.
An exception to this case is if no 9.0.x middle tier was ever installed against the 10g (9.0.4) OracleAS Metadata Repository. In this case, since the 10g Release 2 (10.1.2) middle tier is the first middle tier to be installed against the OracleAS Metadata Repository, you can access OracleAS Portal without running the Upgrade Assistant.
When you install Release 3 (10.1.4.0.1) Identity Management, you must identify a Release 3 (10.1.4.0.1) OracleAS Metadata Repository. This is because the Release 3 (10.1.4.0.1) OracleAS Identity Management components require the Release 3 (10.1.4.0.1) Identity Management schemas.
As a result of this requirement, you cannot specify a 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Metadata Repository while installing the Release 3 (10.1.4.0.1) OracleAS Identity Management.
The following sections provide information about the requirements you must consider when running Release 3 (10.1.4.0.1) Identity Management in an environment with multiple versions of Oracle Application Server:
OracleAS Identity Management Components Must Be the Same Version as Their Required Schemas
OracleAS Identity Management Components Must Use an Oracle Internet Directory Of the Same Version
The OracleAS Metadata Repository contains schemas that are required by OracleAS Identity Management.
If you use the Oracle Universal Installer to upgrade Identity Management to 10g (10.1.4.0.1), then the upgraded Identity Management components can use a previous version of the OracleAS Metadata Repository for their Identity Management schemas. This is because the Identity Management schemas in the OracleAS Metadata Repository are updated as part of the Identity Management upgrade process.
However, if you install a new Identity Management Release 3 (10.1.4.0.1) Oracle home, then you cannot select a previous version of the OracleAS Metadata Repository to store the Identity Management schemas. Instead, when the installation procedure prompts you for an existing OracleAS Metadata Repository, you must specify an existing Release 3 (10.1.4.0.1) Metadata Repository. The Release 3 (10.1.4.0.1) OracleAS Metadata Repository you specify can be a freshly installed Release 3 (10.1.4.0.1) repository, or it can be a OracleAS Metadata Repository that was upgraded to Release 3 (10.1.4.0.1).
OracleAS Identity Management consists of multiple components, such as Oracle Delegated Administration Services, Oracle Application Server Single Sign-On, Oracle Application Server Certificate Authority, and Oracle Directory Integration Platform. These components require Oracle Internet Directory.
If you decide to install these individual OracleAS Identity Management Release 3 (10.1.4.0.1) components, you cannot install those components against a10g (9.0.4) or 10g Release 2 (10.1.2) Oracle Internet Directory.
Instead, you must first either upgrade the Oracle Internet Directory to Release 3 (10.1.4.0.1) or install a new Release 3 (10.1.4.0.1) Oracle Internet Directory.
