Deploying a J2EE Client Module (client JAR)

A J2EE Client module is packaged as a client JAR file which contains one or more Java application components and a client deployment descriptor file named application-client.xml. Once you've created the deployment profile containing the Java application components and the deployment descriptor file and packaged them into a standard J2EE archive, you can proceed to deploy the client JAR to the application server.

To deploy a J2EE Client module in JDeveloper:

If not already done, create a J2EE client JAR deployment profile.
If not already done, create an application server connection to the target application server before deploying the client JAR.
Select and right-click the client deployment profile icon which appears in the Navigator below the specified project. The context menu displays these deployment options:
1. Deploy to JAR file: the Client module is packaged as an client JAR file and saved to the local project directory.
2. Deploy to EAR file: the Client module is packaged as an Enterprise Archive (EAR) file and saved to the local project directory.
3. Deploy to <Name_of_application_server_connection>: the Client module is packaged as a client JAR. JDeveloper also generates an EAR file which contains the client JAR before deploying to the target application server connection.
Choose one of these deployment options.
The client module is deployed to the target application server directory.
(Optional) If you want to edit either the the client deployment profile or the application-client.xml deployment descriptor settings, right-click its icon and choose Settings.

Notes:

For OC4J deployments, see OC4J Deployment Application Directory Structure or refer to the "Oracle Application Server Containers for J2EE User's Guide" which is provided with the Oracle Application Server documentation library.
Oracle9 Application Server provides full support for J2EE client applications. For more information, refer to "Chapter 9, Application Clients in the J2EE Platform Specification 1.2":
http://www.javasoft.com/j2ee/download.html
Make sure that the client deployment descriptor is located inside the client JAR file META-INF/application-client.xml.
JDeveloper recognizes the deployment descriptor file in the META-INF/application-client.xml found in the first entry of the sourcepath. Any other names and locations for application-client.xml file will be ignored.