4 Integrating 10g Release 3 (10.1.3) into Your Existing Environment

If you are already using Oracle Application Server 10g (9.0.4) or 10g Release 2 (10.1.2), use this chapter to understand how to integrate Oracle Application Server 10g Release 3 (10.1.3) into your existing Oracle Application Server environment.

The following sections describe how you can use your existing Oracle Application Server components with your new 10g Release 3 (10.1.3) installations:

Installing 10g Release 3 (10.1.3) Middle Tiers in an Existing Oracle Application Server Environment
Using Existing OracleAS Infrastructure Components
Using Existing Oracle HTTP Server Instances
Using an Existing OracleAS Web Cache Installation As a Reverse Proxy

4.1 Installing 10g Release 3 (10.1.3) Middle Tiers in an Existing Oracle Application Server Environment

There are no restrictions to prevent you from installing 10g Release 3 (10.1.3) middle tiers in an existing 10g (9.0.4) or 10g Release 2 (10.1.2) environment. In fact, if necessary, you can install your new 10g Release 3 (10.1.3) middle tiers on the same host as your existing 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle homes.

As with other Oracle software products, Oracle Universal Installer will check for available ports and perform additional prerequisite checks to be sure the host computer meets the 10g Release 3 (10.1.3) hardware and software requirements.

However, while 10g Release 3 (10.1.3) middle tiers can co-exist with previous Oracle Application Server releases, there are fundamental differences between these releases. For example, 10g Release 3 (10.1.3) introduces significant changes to clustering application servers. For more information refer to the following:

4.2 Using Existing OracleAS Infrastructure Components

Your existing 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Infrastructure consists of an OracleAS Metadata Repository and OracleAS Identity Management.

Oracle Application Server 10g Release 3 (10.1.3) does not require an OracleAS Metadata Repository because none of the components delivered with this release require specific schemas or a database to host those schemas.

However, there are many reasons to configure your 10g Release 3 (10.1.3) middle tier to use your existing OracleAS Identity Management installation. Table 4-1 lists the tasks you can accomplish when you use OracleAS Identity Management with 10g Release 3 (10.1.3).

To configure your 10g Release 3 (10.1.3) instance to use OracleAS Identity Management, select the Identity Management task on the OC4J Administration page in the Application Server Control Console.

See Also:

"Configuring Instances to Use 10.1.2 Oracle Identity Management" in the Oracle Application Server Administrator's Guide

Table 4-1 Using OracleAS Identity Management with 10g Release 3 (10.1.3)

Task	For More Information
Use Oracle Internet Directory as the security provider for the J2EE applications you deploy.	"Overview of Managing Security Providers" in the Application Server Control online help
Use Oracle Internet Directory as the security provider for the 10g Release 3 (10.1.3) Application Server Control. You can then use Oracle Internet Directory to manage the administrator accounts that are used to log in to the Application Server Control Console.	"Configuring the Security Provider for Application Server Control" in the Application Server Control online help
Configure your J2EE applications to use OracleAS Single Sign-On	"About Using OracleAS Single Sign-On" in the Application Server Control online help
Use 10g Release 2 (10.1.2) Single Sign-on to authenticate connections between a Web application and its Web services. In this scenario, it is assumed that both the Web application and the Web service are configured to use the Security Assertion Markup Language (SAML).	"Configuring Single Sign-on Using SAML" in the Oracle Application Server Web Services Security Guide

4.3 Using Existing Oracle HTTP Server Instances

When you install Oracle Application Server 10g Release 3 (10.1.3), you can choose to install Oracle HTTP Server in one or more of your 10g Release 3 (10.1.3) Oracle homes. You can then configure your environment to use the Oracle HTTP Server to serve as a front-end for the J2EE applications you deploy.

Alternatively, you can configure your existing 10g Release 2 (10.1.2) Oracle HTTP Server as the front-end to your new 10g Release 3 (10.1.3) instances.

For more information, see "Configuring Oracle Application Server 10.1.2 with Oracle Application Server 10.1.3" in the Oracle Application Server Administrator's Guide.

4.4 Using an Existing OracleAS Web Cache Installation As a Reverse Proxy

You can use Release 2 (10.1.2) OracleAS Web Cache as a reverse proxy for your 10g Release 3 (10.1.3) middle-tier instance. As a reverse proxy server, OracleAS Web Cache acts a gateway to the middle-tier servers.

For more information, see "Configuring 10.1.2 OracleAS Web Cache as a Reverse Proxy" in the Oracle Application Server Administrator's Guide.