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
- Start the Qshell environment.
On
the CL command line, type the command:
STRQSH
- Enter the following command to launch Java EE
application clients:
app_client_root/bin/launchClient
where app_client_root is /QIBM/ProdData/WebSphere/AppServer/V8/Base or /QIBM/ProdData/WebSphere/AppServer/V8/ND.
- 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 [-CCname=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.
By default, the launchClient command
uses your_server_name 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.
Example
You can store launchClient values in a properties file,
which is a good method for distributing default values. You can then
override one or more values on the command line. The format of the
file is one launchClient -CC parameter
per line without the -CC prefix. For example:
verbose=true classpath=c:\mydir\util.jar;c:\mydir\harness.jar;c:\production\G19
\global.jar BootstrapHost=abc.westcoast.mycompany.com tracefile=c:\WebSphere\mylog.txt
verbose=true classpath=/usr/lpp/mydir/util.jar;/usr/lpp/mydir/harness.jar;/usr/lpp
/production/G19/global.jar BootstrapHost=abc.westcoast.mycompany.com tracefile=/usr
/lpp/WebSphere/mylog.txt