This topic describes the Java™ Platform, Enterprise Edition (Java EE) command line syntax for the launchClient tool for WebSphere® Application Server.
You can use the launchClient command from a node within a WebSphere Application Server, Network Deployment environment. However, do not attempt to use the launchClient command from the Manager.
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]
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 Java EE 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, your.server.name, 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, refer to the Interpreting trace output topic.
If you are using an EJB client application with security enabled, edit the sas.client.props file, which is located in the profile_root/properties directory. Within the file, change the com.ibm.CORBA.loginSource value to none.
For more information on the sas.client.props utility, refer to the Manually encoding passwords in properties files and the PropFilePasswordEncoder command reference topics.
wsadmin -conntype RMI -port rmiportnumber -user userid -password password
Using Jython:
wsadmin -lang jython -conntype RMI -port rmiportnumber -user userid -password password
rmiportnumber for your connection displays in the administrative console as BOOTSTRAP_ADDRESS.
If Kerberos (KRB5) is enabled for administrative authentication, the authentication target supports BasicAuth and KRB5. To use KRB5, update the sas.client.props, soap.client.props, and ipc.client.props files, according to the connector type.
The following examples demonstrate correct syntax.
/QIBM/ProdData/WebSphere/AppServer/V7/Base/bin/launchClient
/home/earfiles/myapp.ear -profileName myprofile -CCBootstrapHost=myWASServer
-CCverbose=true app_parm1 app_parm2