After deploying a Java EE client application onto a machine with
an Application Client installation or in a WebSphere® Application Server node,
you can start the application by using the launchClient command
on that machine.
Before you begin
Before you can use the
launchclient command to
run a Java EE client application, you must have deployed the application.
This
task only applies to Java™ EE client applications.
About this task
The Java Platform, Enterprise Edition (Java EE)
specification requires support for a client container that runs Java applications
(known as Java EE client applications) and provides Java EE
services to the applications. Java EE services include naming, security,
and resource connections.
Procedure
- Enter the following command to launch Java EE application clients:
app_client_root/bin/launchClient
- Pass parameters to the launchClient command or to your
application client program as well. The launchClient command allows
you to do both. The launchClient command requires that
the first parameter is either:
- An EAR file specifying the application client to launch.
- A request for launchClient usage information.
The following example illustrates the command line invocation syntax
for the launchClient tool:
launchClient [-profileName pName | -JVMOptions options | -help | -?] <userapp> [-CC<name>=<value>] [app args]
All other parameters intended for the launchClient command
must begin with the -CC prefix. Parameters that are not EAR files, or usage
requests, or that do not begin with the -CC prefix, are ignored by the application
client run time, and are passed directly to the application client program.
The
launchClient command
retrieves parameters from three places:
- The command line
- A properties file
- System properties
The parameters are resolved in the order listed above, with command line
values having the highest priority and system properties the lowest. Using
this prioritization you can set and override default values.
- Specify the server name.
By
default, the launchClient command uses the localhost for the BootstrapHost property
value.
This
setting is effective for testing your application client when it is installed
on the same computer as the server. However, in other cases override this
value with the name of your server. You can override the
BootstrapHost value
by invoking
launchClient command with the following parameters:
launchClient myapp.ear -CCBootstrapHost=abc.midwest.mycompany.com
You
can also override the default by specifying the value in a properties file
and passing the file name to the launchClient shell.
Security is controlled
by the server. You do not need to configure security on the client because
the client assumes that security is enabled. If server security is not enabled,
then the server ignores the security request, and the application client functions
as expected.