+

Search Tips   |   Advanced Search

Client application Java Network Launcher Protocol deployment descriptor file

The deployment descriptor file is the main Java Network Launcher Protocol (JNLP) descriptor file for the client application.


Location

The client application has an Application Clients runtime dependency that provides the following:

If the Application Clients run-time dependency is not met, it is downloaded and installed in Java Web Start (JWS), as described by the Application Clients run-time installer JNLP descriptor file. For example:


Usage notes

The client application must also include the WebSphereClientLauncher.jar file, which contains the launcher class, com.ibm.websphere.client.launcher.ClientLauncher, that completes one of the following actions:

The JNLP specification requires all the resource (JAR or EAR) files used in a JNLP file to be signed.

We can specify the -CC arguments defined in the launchClient tool for a J2EE Application client application in application arguments section of the JNLP descriptor files. However, only -CCD is supported for a Thin Application client application to define system properties and the JNLP <property> tag can also be used to define system properties. See the following example for details:

For a J2EE Application client application, specify the following application arguments as defined in the JNLP.

  1. Specify the target server provider URL, as shown in the following example:

      <argument> >-CCDjava.naming.provider.url =corbaloc:iiop:myserver.mydomain.com:9080 </argument>

  2. Specify the SSL Key File and SSL Trust File location. These files are expected to be available in the client machine. To use the ones in the Application Clients run-time dependency installed in JWS cache, specify these application arguments: 
    <argument> -CCDcom.ibm.ssl.keyStore=${WAS_ROOT}/etc/key.p12 </argument>
<argument> -CCDcom.ibm.ssl.trustStore=${WAS_ROOT}/etc/trust.p12 </argument>

  3. Initial naming context factor, as shown in the following example:

      <argument>-CCDjava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory </argument>

    For a Thin Application client application, we also need to specify the actual location of the sas.client.props and ssl.client.props files located in the Application Clients runtime dependency installed in the JWS cache. 

    <argument>-CCDcom.ibm.CORBA.ConfigURL=file:${WAS_ROOT}/properties/sas.client.props </argument>
<argument>-CCDcom.ibm.SSL.ConfigURL=file:${WAS_ROOT}/properties/ssl.client.props </argument>

    If any of the default settings in the sas.client.props and sas.client.props file need modifying, use the -CCD to change the settings through the system properties, as shown in the following example:

      <argument>-CCDjavacom.ibm.CORBA.securityEnabled=false </argument>

    Important: The ${WAS_ROOT} token used in the JNLP file is replaced by the launcher class, com.ibm.websphere.client.launcher.ClientLauncher, to the actual location of the Application Clients run-time dependency installation in the JWS cache. If we are using JSP to dynamically create this JNLP description file, you must escape this token because it has a different meaning in JSP 2.0. See the following example for details: 

    <argument>-CCDcom.ibm.ssl.keyStore=\${WAS_ROOT}/etc/key.p12 </argument>
<argument>-CCDcom.ibm.ssl.trustStore=\${WAS_ROOT}/etc/trust.p12 </argument>


Subtopics


Related tasks

  • Preparing the application client run time dependency component for Java Web Start
  • Downloading and running a Java EE client application using Java Web Start

  • launchClient tool