There are several command line tools that you can use to start, stop, and monitor WebSphere server processes and nodes. These tools only work on local servers and nodes. They cannot operate on a remote server or node.

To administer a remote server, you can use the wsadmin scripting program connected to the deployment manager for the cell in which the target server or node is configured.

You can also use the administrative console which runs in the deployment manager for the cell.

Unless otherwise specified, all of the WebSphere Application Server scripts are located in this directory:

• WebSphere Application Server

  /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin

• WebSphere Application Server Network Deployment

  /QIBM/ProdData/WebSphere/AppServer/V6/ND/bin

See also...

• Configure Qshell to run WebSphere Application Server scripts
• Qshell environment variables
• Example: Security and the command line tools

Parameter values that specify a server name, a node name or a cell name are case sensitive. For example, if you want to start the application server MyServer for the profile test, invoke...

startServer MyServer -profileName test

If you specify myserver for the server name, the startServer script fails.

Profile names and iSeries host names are not case sensitive.

Most of command line tools function relative to a particular profile. To determine if a script requires the -profileName parameter, refer to the documentation for that script. If you run a command from...

install_root/bin

...and do not specify the -profileName parameter, the default profile for the product is used to set profile specific variables. The value of install_root for the Express and Base editions is...

/QIBM/ProdData/WebSphere/AppServer/V6/Base

The value of install_root for Network Deployment is...

/QIBM/ProdData/WebSphere/AppServer/V6/ND

To specify a different profile...

• Specify the -profileName option to use the non-default profile...

  cd install_root/WebSphere/AppServer/bin
  startServer server1 -profileName AppServerProfile

  In this example, the command starts the application server named server1 which exists in the configuration for the AppServerProfile profile.

• Run the command from the bin directory of a specific profile...

  cd profile_root/bin
  startServer server1

  When a profile is created, a proxy script is created in the profile's bin directory for each script in the install_root/bin directory that is applicable to the type of profile created. When a proxy script is invoked, the profile specific variables for the script are set based on the profile from which the script is invoked.

  In this example, the command starts the application server named server1 which exists in the configuration for the MyProfile profile.

• Set the WAS_USER_SCRIPT environment variable to the setupCmdLine script for the profile.

  1. Run...

     export WAS_USER_SCRIPT=profile_root/bin/setupCmdLine

  2. Invoke the script located under install_root/bin

  For example,

  export WAS_USER_SCRIPT=/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/mytest/bin/setupCmdLine
  /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin/startServer mytest

  In this example the mytest application server configured under the mytest profile is started.

To use the command line tools

1. STRQSH
2. cd WAS_HOME/bin
3. Run the command.

Sub-topics