Skip Headers

Oracle® Application Development Framework Developer's Guide 10g Release 3 (10.1.3) B25386-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# 22.6 Deploying to Oracle Application Server

This section describes deployment details specific to Oracle Application Server:

- Section 22.6.1, "Oracle Application Server Versions Supported"

- Section 22.6.2, "Oracle Application Server Release 2 (10.1.2) Deployment Notes"

- Section 22.6.3, "Oracle Application Server Deployment Methods"

- Section 22.6.4, "Oracle Application Server Deployment to Test Environments ("Automatic Deployment")"

- Section 22.6.5, "Oracle Application Server Deployment to Clustered Topologies"

## 22.6.1 Oracle Application Server Versions Supported

Table 22-2 shows the supported versions of Oracle Application Server:

Table 22-2 Support Matrix for Oracle Application Server

Oracle Application Server Version | JDK Version | J2EE Version
--- | --- | ---
Release 3 (10.1.3) | 1.5_05 | 1.4
Release 2 (10.1.2) | 1.4 | 1.3

## 22.6.2 Oracle Application Server Release 2 (10.1.2) Deployment Notes

If you are deploying to Oracle Application Server Release 2 (10.1.2), you have to perform some additional steps before you can run your ADF applications:

- This version of Oracle Application Server supports JDK 1.4. This means that you need to configure JDeveloper to build your applications with JDK 1.4 instead of JDK 1.5. See Section 22.11, "Deploying to Application Servers That Support JDK 1.4" for details.

- You need to install the ADF runtime libraries on the application server. This is because the ADF runtime libraries that were shipped with Release 2 (10.1.2) need to be updated. To install the ADF runtime libraries, see Section 22.12.1, "Installing the ADF Runtime Libraries from JDeveloper".

- Note that Oracle Application Server Release 2 (10.1.2) supports J2EE 1.3, while JDeveloper 10.1.3 supports J2EE 1.4. This means that if you are using J2EE 1.3 components (such as EJB 2.0), you have to ensure that JDeveloper creates the appropriate configuration files for that version. Configuration files for J2EE 1.3 and 1.4 are different.

  Table 22-3 lists the configuration files that need to be J2EE 1.3-compliant, and how to configure JDeveloper to generate the appropriate version of the files.

  Table 22-3 Configuring JDeveloper to Generate Configuration Files That Are J2EE 1.3-Compliant

  Configuration File | How to Configure JDeveloper to Generate Appropriate Version of the File
  --- | ---
  `application.xml` `web.xml` | Select the project in the Applications Navigator. Select File > New to display the New Gallery. In Categories, expand General and select Deployment Descriptors. In Items, select J2EE Deployment Descriptor Wizard and click OK. Click Next in the wizard to display the Select Descriptor page. On the Select Descriptor page, select application.xml (or web.xml) and click Next. On the Select Version page, select 1.3 (2.3 if you are configuring `web.xml`) and click Next. On the Summary page, click Finish.
  `orion-application.xml` `data-sources.xml` `oc4j-connectors.xml` | Select the project in the Applications Navigator. Select File > New to display the New Gallery. In Categories, expand General and select Deployment Descriptors. In Items, select OC4J Deployment Descriptor Wizard and click OK. Click Next in the wizard to display the Select Descriptor page. On the Select Descriptor page, select the file you want to configure and click Next. On the Select Version page, select the appropriate version and click Next. For `orion-application.xml`, select 1.2. For `data-sources.xml`, select 1.0. For `oc4j-connectors.xml`, select 10.0. On the Summary page, click Finish.

## 22.6.3 Oracle Application Server Deployment Methods

Instead of deploying applications directly from JDeveloper, you can use JDeveloper to create the archive file, and then deploy the archive file using these methods:

- Using Application Server Control Console. For details, see the "Deploying with Application Server Control Console" chapter in the Oracle Containers for J2EE Deployment Guide.

- Using `admin_client.jar`. For details, see the "Deploying with the admin_client.jar Utility" chapter in the Oracle Containers for J2EE Deployment Guide.

You can access the Oracle Containers for J2EE Deployment Guide from the Oracle Application Server documentation library.

## 22.6.4 Oracle Application Server Deployment to Test Environments ("Automatic Deployment")

If you are deploying to a standalone OC4J environment that is not a production environment, you can configure OC4J to automatically deploy your application. This method is not recommended for production environments.

For details, see the "Automatic Deployment in OC4J" chapter in the Oracle Containers for J2EE Deployment Guide.

## 22.6.5 Oracle Application Server Deployment to Clustered Topologies

To deploy to clustered topologies, you can use any of the following methods:

- In JDeveloper, you can deploy to a "group" of Oracle Application Server instances. To do this, ensure that the connection to the Oracle Application Server is set to "group" instead of "single instance".

- You can use the `admin_client.jar` command-line utility. This utility enables you to deploy the application to all nodes in a cluster using a single command. `admin_client.jar` is shipped with Oracle Application Server 10.1.3.

  For details, see the "Deploying with the admin_client.jar Utility" chapter in the Oracle Containers for J2EE Deployment Guide.