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:

1. Create the Business Components project and the JClient project before creating your archive files to ensure that you archive the latest source files.
2. Using the provided script, create the middle-tier bc4jlib.ear archive file before running the JClient Java Web Start Wizard.

   Note, be sure to follow the steps to modify the create_jclient_ear.bat script when you decide, for security reasons, to make the password for the Java keystore different from the password used to protect the JAR signing key. You will not be able to run the JClient Java Web Start Wizard until you have successfully generated the bc4jlib.ear archive.

3. 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.

4. If for security reasons the password used for the Java keystore defined on the machine differs from the password used to protect the key and sign the code, then you must modify the ctbuild.xml ANT build file to reference the specified password:

   1. Open the ctbuild.xml file and add the property for the key password below the other signing properties:

      <!--properties related to signing-->
<property name="alias" value="ADFJClientTrust"/>
<property name="storepass" value="welcome"/>
<property name="keypass" value="myPassword"/>

   2. Change the sign target from the following:

      <target name="sign" depends="jar">
   <signjar jar="${mt.jar.name}" alias="${alias}" storepass="${storepass}"/>
   <signjar jar="${ct.jar.name}" alias="${alias}" storepass="${storepass}"/>
</target>

      to:

      <target name="sign" depends="jar">
   <signjar jar="${mt.jar.name}" alias="${alias}" keypass="${keypass}" storepass="${storepass}"/>
   <signjar jar="${ct.jar.name}" alias="${alias}" keypass="${keypass}" storepass="${storepass}"/>
</target>

5. To create the client side archive files, right-click ctbuild.xml in the JClient project and choose:

   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 should generate 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.

6. (Optional) If you want to edit either the client_war.deploy profile or the web.xml deployment descriptor settings, right-click the profile and choose Properties.

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.

Related topics

Running JClient Applications with Web Start in JDeveloper
Deploying a JClient Web Application Archive for Java Web Start

Copyright © 1997, 2004, Oracle. All rights reserved.