For a J2EE application client application and or Thin application
client application to be launched using Java Web Start (JWS), an Java Runtime
Environment that IBM provides, the library JAR files and properties files
bundled in Application Client for WebSphere Application Server must be installed
in the JWS. This article provides the steps to build the Application Client
run-time dependency component from an Application Client installation. It
is packaged as a Web Archive Resource (WAR) file that can be installed in
an Application Server.
Before you begin
Install the Application Client for WebSphere Application Server for
the platform to which the client application deploys. If there is a requirement
to deploy the client application to multiple platforms, the Application Client
run-time dependency component must be built separately for each platform that
client application supports.
For example, if the
client application deploys to both the Windows platform and Linux platform,
follows the steps for this task to build the Application Client run-time dependency
component for Windows on a Windows platform machine with the Application Client
for WebSphere Application Server for Windows installed. Now, repeat the steps
for this task to build the Application Client run-time dependency component
for Linux on a Linux platform machine with the Application Client for WebSphere
Application Server for Linux installed.
Procedure
- Install the Application Client for WebSphere Application Server
for the client application supported operating systems.
Install
Application Client in the C:\Program Files\IBM\WebSphere\AppClient directory.
- Change the directory to the installation bin directory.
![[Windows]](../../windows.gif)
For example:
CD C:\Program files\IBM\WebSphere\AppClient\bin
- Run the buildClientRuntime tool to generate the Application Client
run-time JAR file in a temporary directory which contains the Java 2 Runtime
Environment, Application Client run-time properties, the SSL KeyStore and
TrustStore file, and the Application Client run-time library JAR files.
If
you are building an Application Client run-time JAR file only for serving
Thin application client applications and not for J2EE application client applications,
you can reduce the size of the generated JAR file by not including the Application
Client run-time library JAR files. An extra parameter is passed to the buildClientRuntime
tool.
- Copy the WebSphereClientRuntimeInstaller.jar file to the
same location of the JAR file generated in the previous step. This
JAR file is located in the JWS directory of the WebSphere Application Server
clients installation.
![[Windows]](../../windows.gif)
For example:
copy ..\JWS\WebSphereClientRuntimeInstaller.jar C:\WebApp1\runtime
- Sign the JAR files created from the previous steps, using the Java
2 SDK jarsigner utility.
- Create an Application Client run-time installer JNLP descriptor
file or a JavaServer Pages (JSP) file if it is generated dynamically in the
same temporary directory as previous step. See the sample JNLP file shown
in the Example section of this topic.
- Package the two signed JAR files and the Application Client run-time
installer JNLP descriptor file into a WAR file. This WAR file is packaged
into an EAR file that can be deployed to an Application Server.
Results
Your Web application is ready to serve the Application Client run
time and the JRE environment.