Creating a Deployment Profile for All J2EE Modules (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.

Note: If you have an existing EAR file, you can use the JDeveloper EAR import facility to import the EAR into any project.

To create a deployment profile for all J2EE Modules (EAR):

In the Navigator, select the <projectname>.jpr in which you want to create the EAR deployment profile.
Choose File | New to open the New Gallery.
In the Categories tree, expand General and select Deployment Profiles.
In the Items list, double-click EAR File - J2EE Application.
Click OK.
Specify a location for the <EAR_appname>.deploy profile or accept the defaults.
Click Save.
The EAR Deployment Profile Settings panel displays. Configure the settings for each page as appropriate:
1. General Page
2. EAR Options Page
3. Application Assembly Page
4. Platform Page (Optional) If you want to pass command line parameters to any of the supported target connection types, click the appropriate node: Standalone OC4J, iAS Remote DCM, iAS Local DCM, WebLogic 6.x, or WebLogic 7.x.
Click OK when you are done.
The newly created <EAR_appname>.deploy profile appears in the Navigator below the specified project.
To deploy the EAR deployment profile, see Deploying a J2EE Enterprise Archive (EAR).
(Optional) See Adding a Resource Adapter Archive (RAR) to the EAR.
(Optional) If you want to edit the EAR deployment profile, right-click the <EAR_appname>.deploy profile and choose Settings.

Notes:

If you create a J2EE deployment profile without specifying default connection or target platform information in Platform page of the Settings dialog, JDeveloper will produce a vanilla J2EE EAR file that does not contain any platform-specific deployment descriptor files, such as orion-application.xml, even if such files are contained in the project.
If the EAR file is missing the needed platform-specific deployment descriptor files or contains an auto-generated file instead of the file from your project, then you need to specify either a target connection with the deployment profile or a default target platform (when not deploying to a connection) in the profile's Platform page.

To specify a target connection with the deployment profile, use this procedure:
1. Right-click the deployment profile (for example webapp1.deploy), and choose Settings from the context menu. The Deployment Profile Settings page appears.
2. Select Platform in left pane, then select a default connection from the Target Connection dropdown list box in the right pane.
3. Click OK to save these selections. If you selected an Oracle server as the default connection or target platform, the orion-application.xml file for this deployment should now be correct.
To package a JAR, WAR, or EAR file without deploying to a running application server, use this procedure:
1. Define a connection type corresponding to the target platform. The server does not need to be running, so it's not necessary to test the connection.
2. Right-click the profile and select Settings | Platform.
3. Select the Target Connection that you just created.

The J2EE application is deployed to the target directory on your application server. For Oracle Application Server, see OC4J Deployment Application Directory Structure or refer to the "Oracle Application Server Containers for J2EE User's Guide" Part Number B10322-01
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.1. 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