InfoCenter Home >
4: Developing applications >
4.7: Java Clients >
4.7.6: Packaging and distributing Java client applications
4.7.6: Packaging and distributing Java client applications
After a client application has been developed the next step in the process is packaging
and distributing the client application for use on client machines.
Packaging consists of pulling together the various artifacts that the client
application requires. Distributing applies
to making the client application available on the target client machines.
Each of the WebSphere Java clients differ slightly from each other in the
packaging and distributing phases of the development process.
These differences are described below.
Application client type |
Packaging |
Distribution |
J2EE Application Client
|
Packaging of the WebSphere J2EE Application Client is accomplished through
the Application Assembly Tool (AAT).
This tool generates an Enterprise Archive (.ear) file as
the output from the the assembly and deployment process. The .ear file
contains all of the class files that are required by the client application to run.
The .ear file must be deployed. The deployment can be done through
the Application Assembly Tool or when the EJB modules within the .ear
file are installed in WebSphere Application Server. The deployment phase
generates the client bindings needed by the client application.
|
Distributing the J2EE Application Client .ear file to the target
client machine that has WebSphere J2EE Application Client installed, is a manual
process.
WebSphere Application Server does not provide any tooling to assist
in the distribution of the J2EE Application Client .ear files.
The J2EE Application Client might require further configuration
if the application makes use of external resources (such as: JDBC,
JavaMail, JMS or URL). Perform this configuration with the
Application Client Resource Configuration Tool.
When the resource configuration is complete, the application can be started
using the launchClient command.
|
Java Application Thin Client
|
The Java application thin client is packaged by manually collecting
appropriate JAR files and Java classes to support the client application.
The Enterprise Java Beans that the client application uses, require that
client side bindings are available on the client target machine.
The client side bindings are available from the deployed EJB JAR files.
The .jar files, containing the Enterprise Java Beans, are invoked by the application.
These JAR files are located in directory:
product_installation\InstalledApps\<YourEJBapplication.ear>\
|
Distributing the Java application thin client JAR files to the target client machine
where WebSphere Java Thin Application Client is installed, is a manual process.
WebSphere Application Server does not provide any tooling to assist in the
distribution of the JAR files.
When the client application files are present on the target client machine,
you must set up the environment. WebSphere Application Server provides a command
that assists users in setting up the environment by defining several environment
variables. Use the
setupClient command located in the
product_installation\bin directory.
After running this command, add your client application JAR files to the CLASSPATH
or use the -classpath parameter on the java command.
|
Applet Client
|
The Applet client is packaged manually by collecting the appropriate JAR files,
Java classes, and HTML files to support the Applet.
The Enterprise Java Beans that the Applet uses, require client
side bindings.
The client side bindings are available from the deployed EJB JAR files. What .jar files are used
depends on the Enterprise Java Beans invoked. These JAR files are located in
the product_installation\InstalledApps\<YourEJBapplication.ear>\ directory.
|
Distributing the Applet client to the target client machine
that has the Applet client installed or to the target WebServer machine
(if you want to make the Applet available for download), is a manual process.
WebSphere Application Server does not provide any tooling to assist in the distribution of the JAR files.
|
|
|