WebSphere Application Server provides many
tools that you can call from a command line.
About this task
There are several command line tools that you can use to start,
stop, and monitor application 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.
The following information is common for each
command:
- Unless otherwise specified, all of the application server commands are
located in the app_server_root/bin
directory.
- 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.
Note on running command line tools on the Microsoft® Windows Vista™ operating system: On the Windows Vista operating system, it
is possible to install Websphere Application Server as either Administrator
or non-Administrator. When it is installed as Administrator, certain operations
(such as those involving Windows Services) require Administrator privileges.
In order to ensure that Websphere Application Server command line tools have
sufficient privileges, run them as Administrator. When you run these command
line tools from a Command Prompt, run them from a Command Prompt window that
is launched by performing the following actions:
Use the following general steps to run a command:
Procedure
- Open a system command prompt.
- Determine whether to run the script from the profile or application
server root directory.
Most command line tools function relative
to a particular profile. To determine if a command requires the -profileName
parameter, refer to the documentation for that specific command. If you run
a command from the
app_server_root/bin directory
and do not specify the -profileName parameter, the default profile for the
product sets profile-specific variables. To specify a different profile, use
one of the following options:
- Run the command of interest.
Results
The command runs the requested function and displays the results
on the screen.
Refer to the command log file for additional information.
When you use the -trace option for the command, the additional trace data
is captured in the command log file. The directory location for the log files
is under the default system log root directory, except for commands related
to a specific server instance, in which case the log directory for that server
is used. You can override the default location for the command log file using
the -logfile option for the command.
What to do next
For more information about using profiles,
including how to obtain a list of profiles, see the manageprofiles command article.
To use the
command line tools, perform the following steps: