Using command-line tools
The product 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.
- 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.
Examples of these tools are the startServer command, stopServer command, firststeps command, and the Profile Management Tool.
If you are using a Windows Server Core installation of Windows Server 2008, any WebSphere Application Server commands that require a graphical interface are not supported since a Windows Server Core system does not have a graphical user interface. Therefore, commands such as launchpad.exe or ifgui.bat are not supported on that type of Windows Server 2008 installation.Use the following general steps to run a command:
Procedure
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 information about the manageprofiles command topic.