Deploying a Java EE client application onto the client
machines where it is to run includes distributing the EAR file for
the client application and configuring resource references for use
by the client application.
Before you begin
To run a deployed Java EE client application, the application
needs access to a Application Client installation or a
WebSphere® Application Server installation.
For
information about installing the Application Client on a client machine,
refer to the Installing Application Client for WebSphere Application Server topic.
Attention: Application Client for WebSphere Application Server ships only with
the 32-bit WebSphere Application Server.
- Prerequisites
Developing a Java EE client application
About this task
Use
this topic only if you later want to use the want to
launchClient command
to run the Java client application on an Application Client installation
or in a
WebSphere Application Server node.
If
you want to download and run a Java EE
client application remotely, you can use the Java Web Start to deploy
the application onto the remote client machine with a single click
from a Web browser on the client machine. For information about using
Java Web Start to deploy Java EE client applications, see "Downloading
and running a Java EE client application by using Java Web Start".
Procedure
- Distribute the EAR file.
The client machines
configured to run a client application must have access to the EAR
file.
- If all the machines in your environment share the same image and
platform, run the Application Client Resource Configuration Tool (ACRCT)
on one machine to configure the external resources, then distribute
the configured EAR file to the other machines.
- If your environment is set up with a variety of client installations
and platforms, run the ACRCT for each unique configuration.
- You can either distribute an EAR file to the correct client machines,
or make it available on a network drive.
- Distributing EAR files is the responsibility of the system and
network administrator.
- Configure the resources for the application client. This
generally involves using the Application Client Resource Configuration
Tool (ACRCT) to configure references for the resources that the application
is to use, including resource adapters, resource providers, data sources,
and Java Message Service resources. These configurations are stored
in the client JAR file within the application EAR file. The client
runtime uses these configurations to resolve and create an instance
of the resources for the client application.
For some types of resources,
other actions are needed; for example, to install a resource adapter
and define environment variable needed to start the client application.
More information about the actions for different types of resources
is given in other configuring resources topics.
If you plan
to deploy the client application on z/OS®,
run the ACRCT on Windows. You can also run the
ACRCT for distributed platforms locally.
If the client application defines the local resources,
but the resources are installed in a different location, run the ACRCT
(clientConfig command) on the local machine to
change the configuration in the EAR file. For example, the EAR file
can contain a DB2® resource, configured as C:\DB2.
If, however, you installed DB2 in the D:\Program
Files\DB2 directory, use the ACRCT to create a local version
of the EAR file.
What to do next
After deploying the Java EE
client application, use the
launchClient command
to run the client application.