Deploying a J2EE Enterprise Archive

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 deploy an application to an application server connection , JDeveloper assembles a minimal EAR file which includes the packaged profile combinations and deploys it to the EAR to the target application server.

To deploy a J2EE Enterprise Archive (EAR File):

Create an EAR File deployment profile.
Create a connection to the target application server.
Select the deployment profile in the Navigator, right-click, and choose one of the deployment options:
- Deploy to | <application server connection>: the web module is packaged as an EAR file and is deployed to the selected application server connection.
- Deploy to EAR file: the web module is packaged as an EAR file and is saved to the location specified in the EAR deployment profile.

To edit the EAR deployment profile, select it in the Navigator, right-click, and choose Properties.

Notes:

If you have an existing EAR file, you can use the JDeveloper EAR import facility to import the EAR into any project.
If you create a J2EE deployment profile without specifying default connection or target platform, JDeveloper will produce a vanilla EAR file that does not contain any platform-specific deployment descriptor files, even if such files are contained in the project.

If the deployed EAR file is missing the needed platform-specific deployment descriptor files or contains auto-generated descriptor files instead of those from your project, then you need to specify either a target connection with the deployment profile or a default target platform.

To specify a target connection with the deployment profile, in the Platform page choose a connection from the T arget Connection dropdown list.

JAR and WAR files to be included in an EAR file must be created before the EAR file is deployed. For the included application's deployment profiles, choose Deploy to J AR file or Deploy to WAR file to create these subordinate archives.
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.