The EAR file, WebSphereClientRuntime.ear, is provided
in the JWS directory of the Client Application for WebSphere Application Server
installation. This EAR file provides a sample Application Clients run-time
installer JNLP descriptor file and a sample Application Clients run-time library
component JNLP descriptor file. Follow the steps in this task to build the
Application Clients run-time dependency component and the Application Clients
run-time library component. Add these components to the WebSphereClientRuntime.ear file,
and then install the EAR file in an Application Server to be used by the client
application.
Why and when to perform this task
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 Clients
run-time dependency component must be built separately for each platform that
the client application supports.
Steps for this task
- Install the Application Clients on the client application supported
operating system. For example, install Application Clients in
the C:\Program Files\IBM\WebSphere\AppClient directory.
- Create the following temporary working directories:
MKDIR C:\WebApp1
MKDIR C:\WebApp1\runtime
MKDIR C:\WebApp1\runtime\Widnows
MKDIR C:\WebApp1\runtime\WebSphereJars
- Change directory to the installation bin directory. See
the following example for help:
CD C:\Program files\IBM\WebSphere\AppClient\bin
- Run the buildClientRuntime tool to generate the Application Clients
run-time JAR file in a temporary directory that contains the Java 2 Runtime
Environment that IBM provides, Application Clients run-time properties, the
SSL KeyStore and TrustStore files, and the Application Clients run-time library
JAR files. See the following example for details:
buildClientRuntime C:\WebApp1\runtime\windows\WASClient6.0_windows.jar
- 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 Application Client for WebSphere
Application Server installation. For example, copy the ..\JWS\WebSphereClientRuntimeInstaller.jar file
to the C:\WebApp1\runtime directory.
- Sign the JAR files created from the previous steps, using the Java
2 SDK jarsigner utility. See the following example for details:
cd C:\WebApp1\runtime
jarsigner -keystore myKeystore -storepass myPassword
WASClient6.0_windows.jar myKeyAliasName
jarsigner -keystore myKeystore -storepass myPassword
WebSphereClientRuntimeInstaller.jar myKeyAliasName
- This step also requires you to create a keystore
file, such as myKeystore.
- You must also create a self-signed certificate for the myKeystore file.
For more information, see the topic, "Creating self-signed
personal certificates."
- Run buildClientLibJars to copy the Application Clients run-time
library JAR files from the Application Client for WebSphere Application Server
installation to a temporary directory. All the JAR files in the temporary
directory are signed. See the following example for details:
buildClientLibJars C:\WebApp1\runtime\WebSphereJars
myKeystore myPassword myKeyAliasName
- This step also requires you to create a keystore
file, such as myKeystore.
- You must also create a self-signed certificate for the myKeystore file.
For more information, see the topic, "Creating self-signed
personal certificates."
- Add all the JAR files created in the previous steps in the C:\WebApp1 directory
to the WAR file within the WebSphereClientRuntime.ear file.
The contents of the WAR file are shown in the following example:
The root of the WAR
├───META-INF
│ MANIFEST.MF
│
├───Runtime
│ │ jnlp.jsp
│ │ WebSphereClientRuntimeInstaller.jar
│ ├───windows │
│ │ WASClient6.0_windows.jar
│ │
│ └───WebSphereJars
│ jnlp.jsp
│ activities.jar
│ :
│ (all the jars created in step 7 under
│ c:\WebApp1\Runtime\WebSphereJars)
│
├───theme
│ Master.css
│
└───WEB-INF
ibm-web-bnd.xmi
ibm-web-ext.xmi
web.xml
- Install the WebSphereClientRuntime.ear file to an Application
Server. You have just created an Application Clients run-time
dependency component and Application Clients run-time libraries for serving
J2EE Application client applications and Thin Application client applications
using Java Network Launching Protocol (JNLP) or Java Web Start (JWS).