This topic describes the Java 2 Platform Enterprise Edition (J2EE) command line syntax for the launchClient tool for WebSphere Application Server.
You can use the launchClient command from a node within a Network Deployment environment. However, do not attempt to use the launchClient command from the Deployment Manager.
launchClient [-profileName pName | -JVMOptions options | -help | -?] <userapp> [-CC<name>=<value>] [app args]where
The default is default_profile.
The first parameter must be -help, -? or contain no parameter at all. The -profileName pName and -JVMOptions options are optional parameters. If used, they must appear before the <userapp> parameter. All other parameters are optional and can appear in any order after the <userapp> parameter. The J2EE Application client run time ignores any optional parameters that do not begin with a -CC prefix and passes those parameters to the application client.
Supported arguments include:
The default is the value of the -CCBootstrapHost parameter or the value, localhost, if the -CCBootstrapHost parameter is not specified.
-CCproviderURL=corbaloc:iiop:myserver.mycompany.com:9810,:mybackupserver.mycompany.com:2809This value is mapped to the java.naming.provider.url system property.
For more information on basic and advanced trace formatting, see Interpreting trace output.
The following examples demonstrate correct syntax.
launchClient c:\earfiles\myapp.ear -CCBootstrapHost=myWASServer -CCverbose=true app_parm1 app_parm2
./launchClient.sh /usr/earfiles/myapp.ear -CCBootstrapHost=myWASServer
-CCverbose=true app_parm1 app_parm2