Deploying a J2EE Enterprise Archive (EAR)

The J2EE Enterprise Archive (EAR) deployment profile provides you with centralized control over the process of application assembly. This assembling task involves selecting which already-packaged J2EE deployment profiles to include with the EAR file. You can choose to mix and match any combination of packaged WAR, EJB JAR, and/or client JAR profiles in projects within the same workspace. When you choose Deploy to <application_server_name>, JDeveloper is actually assembling a minimal EAR file which includes the packaged profile combinations and deploying the EAR to the target application server.

To deploy a J2EE Enterprise Archive (EAR):

If not already done, create an EAR deployment profile.
If not already done, create an application server connection to the target application server.
The <EAR_appname>.deploy profile appears in the Navigator below the specified project. Select and right-click . The context menu displays these deployment options:
- Deploy to <Name_of_application_server_connection>: the application is packaged as an EAR which contains all the J2EE modules for the application before deploying to the selected application server connection.
- Deploy to EAR file: the application is packaged as an EAR and saved to the local directory you specified the EAR deployment profile.
(Optional) If you want to edit the EAR deployment profile, right-click the <EAR_appname>.deploy profile and choose Settings.

Notes:

You must create the JAR or WAR file first before these packaged forms of the modules are ready to be assembled into the EAR file. In JDeveloper, choose the option to Deploy to JAR file or Deploy to WAR file to package the individual J2EE module into its specified JAR or WAR file.
At deploy-time, do not assemble EJB 1.1 and EJB 2.0 modules into a single J2EE application EAR file as deployment will fail and SQL and connection errors will be raised.
See About Deploying on Oracle9i Application Server for information on deploying the EAR file to an Oracle9i Application Server.
For Oracle Application Server deployments, see OC4J Deployment Application Directory Structure or refer to the "Oracle Application Server Containers for J2EE User's Guide" provided with the Oracle Application Server documentation library for information on the deployed location of the application files including the EAR file.
The web container in OC4J provides full support for Servlets 2.2 and Java Server Pages (JSP) 1.2. For more information, refer to the Sun Microsystems Java Servlet Specification, Version 2.2 which you can download from:
http://www.javasoft.com/products/servlet/
The EJB container in OC4J provides full support for EJB 2.0. For more information about EJB 2.0, you can download the specifications from:
http://www.javasoft.com/products/ejb/docs.html