InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.2: WebSphere Control Program (wscp) >
6.6.0.2.2.2: Command syntax and usage >
6.6.0.2.2.2.1: Basic syntax

6.6.0.2.2.2.1: Basic syntax

The syntax for the wscp command is as follows:
wscp [ -h  ]  [ -c command ] [ -f  Tcl_file_name]
[ -p  properties_file_name] [ -x  extension_class] [ [ -- ] options ] [-node node_name]

The command options and arguments are as follows:

  • The -h option displays help for the command.

  • The -c option indicates command-line mode. The command argument specifies a single command to be executed by wscp. This option can be repeated multiple times on the command line. See 6.6.0.2.2.2.8: Detailed syntax for more information on the command argument.

  • The -f option evaluates the specified file (script) of Tcl commands. Scripts can have arguments, which are specified following the double hyphen (- -). This option can be repeated multiple times on the command line. See 6.6.0.2.2.2.7: Running scripts.

  • The -p option loads the specified properties file. This option can be repeated multiple times on the command line.

  • The -x option loads the specified Tcl extension class. This option can be repeated multiple times on the command line.

  • The options following the double hyphen (- -) are used to set Tcl argc and argv variables as specified. The double hyphen is necessary only if an option can otherwise be mistaken for a wscp shell option.

For example, to invoke wscp and load the init.tcl script, issue the following command:

wscp -f init.tcl

If no command-line options or files are specified, an interactive shell (Tcl interpreter) is invoked, which is terminated by the exit command. Command-line options not supported by wscp, or specified after the double hyphen (- -) on the command line, are used to set the Tcl argc or argv variables. These variables can be interpreted by Tcl extensions or other commands.

The wscp shell evaluates Tcl commands in the order specified on the command line, so any extensions must be loaded prior to invoking commands dependent on those extensions. The following extensions are automatically loaded:

  • com.ibm.ejs.sm.ejscp.EjscpExtension, the class for the wscp commands

  • com.ibm. ejs.sm.ejscp.ContextExtension, the class for manipulating Java Naming and Directory Interface (JNDI) contexts

  • com.ibm.ejs.sm.ejscp.DrAdminExtension, the class for tracing the wscp client, WebSphere application servers, and the WebSphere administrative server

  • com.ibm.ejs.sm.ejscp.RemoteExtension, the class for the wscp Remote extension.

  • com.ibm.ejs.sm.ejscp.PmiServiceExtension, the class for monitoring application server performance.

  • com.ibm.ejs.sm.ejscp.SecurityConfigExtension, the class for setting basic security defaults.

  • com.ibm.ejs.sm.ejscp.SecurityRoleAssignmentExtension, the class for manipulating J2EE security roles.

After a command or script is executed, control is returned to the shell.

The wscp commands can be run as individual wscp invocations from the operating system prompt (command-line mode), as scripts, or interactively in a wscp session (interactive mode).

Go to previous article: 6.6.0.2.2.2: Command syntax and usage Go to next article: 6.6.0.2.2.2.2: Invoking and terminating wscp

 

 
Go to previous article: 6.6.0.2.2.2: Command syntax and usage Go to next article: 6.6.0.2.2.2.2: Invoking and terminating wscp