Deploying a Java Client Web Application Archive for Java Web Start

You can use JDeveloper's simple J2EE web deployment process to set up the web server before downloading and running the application using Java Web Start.

Once the application resides on the web server, it becomes very easy to maintain. Java Web Start takes care of identifying and downloading application updates each time the user runs the application.

Note: To learn how to use the keytool and jarsigner tools to digitally sign your applications and applets for security purposes, search for "Key and Certificate Management Tool" on the Java Web Start web site:
http://java.sun.com/products/javawebstart/

To deploy Java client applications to the web server:

If not already done, create a Java Client Web Archive for Java Web Start.
If not already done, create a connection to OC4J or Oracle Application Server.
Create a simple JAR archive of your Java client application.
Create a Web Start JNLP Definition for Java Clients to generate the JNLP file and HTML file for use with Java Web Start.
Select and right-click <webapp>.deploy. The context menu displays these deployment options:
1. Deploy to <Name_of_server_connection>: the web module is packaged as a WAR. JDeveloper also generates an EAR file which contains the WAR before deploying to the selected application server connection which you created earlier.
2. Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
3. Deploy to WAR file: the web module is packaged as a WAR file and saved to the local directory you specified earlier in the <webapp>Deploy profile settings. Choose this option if you want to deploy to a production web server running a non-OC4J container. Right-click the <client_war> profile in the Java client project and choose Deploy to WAR File to generate the WAR file. You must proceed to install the WAR file on the non-OC4J web server.
4. Deploy to EAR file: the web module is packaged as an Enterprise Archive (EAR) file and saved to the local directory you specified earlier in the <webapp>Deploy profile settings.
(Optional) If you want to edit either the <webapp>Deploy profile or the web.xml deployment descriptor settings, right-click its icon and choose Settings.

Notes:

If you require further assistance for any field on any page, click Help.
The Web Container in Oracle Application Server provides full support for Servlets 2.3 and JavaServer Pages (JSP) 1.2. For more information, refer to the Sun Microsystems Java Servlet Specification, Version 2.3:
http://www.javasoft.com/products/servlet/
Make sure that the web application deployment descriptor is located inside the Web Application Archive (WAR) file WEB-INF/web.xml.
For information on the deployed location of the application files including the WAR and EAR files, see the "Oracle Application Server Containers for J2EE User's Guide" provided with the Oracle Application Server documentation library.