application client commands
The client command supports create, run, debug, package and help actions.
wlp/bin directory contains
scripts that are called
client.bat to help with running
client applications. The syntax of these scripts are as follows:
client<action> client_name [options]
where the value of action represents the operation that you can perform on an application client.
clientscript supports the following actions:
- A command that creates a new application client.
- A command that launches the application client in the foreground.
- A command that runs the named application client in the console foreground after a debugger
connects to the debug port. The default port is
- A command that packages an application client.
- A command that gets command-line script help, including details of more options.
clientscript supports the following options:
- --archive="path to the target archive file"
- Specify the archive target to be generated by the package action. You can specify the target as
an absolute path or as a relative path. If this option is omitted, the archive file is created in
the client output directory. The target file name extension might influence the format of the
generated archive. The default archive format for the package action is
paxon z/OS® and
zipon all other platforms. The
jararchive format produces a self-extracting jar file that similar to the original installer archive.
- Clean all cached information related to this client instance.
- A comma-delimited list of values. The valid values vary depending on the action.
- Specify the name of the template to use when creating a new client.
- Automatically accept and store the signer certificate in the client truststore without being prompted to examine the server certificate.
The following examples show the application client command actions that you can run on other systems:
client.bat create client_name client.bat run client_name client.bat help
client create client_name client run client_name client help