Creating a JClient Web Archive for Java Web Start

You can use JDeveloper's 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.

To create the JClient web application archive for Java Web Start:

Create the Business Components project and the JClient project before creating your archive files to ensure that you archive the latest source files.
Create the middle-tier bc4jlib.ear archive file before running the JClient Java Web Start Wizard.
Run the JClient Java Web Start Wizard to generate the JNLP files for use with Java Web Start. The wizard also generates an Ant build file ctbuild.xml and an already configured client_war.deploy profile.
To create the client side archive files, right-click ctbuild.xml in the JClient project and choose either:
Build Target | sign -- to require authentication of the archive, this will sign your the contained JAR files and is a required step.

The build file generates two signed archive files in your project's public_html directory: client.jar and mymt.zip. These archives are referenced by the generated client_war.deploy profile.
(Optional) If you want to edit either the client_war.deploy profile or the web.xml deployment descriptor settings, right-click the appropriate icon and choose Settings.

By default, you can run the WAR components in JDeveloper's embedded OC4J server to test the application. When you are ready to deploy the resulting WAR and EAR files to the target application server, make sure to create an application server connection.