WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Using command line tools

WebSphere Application Server Network Deployment 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 WebSphere Application Server Network Deployment 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. See Deploying and managing using scripting for more information about using the wsadmin scripting program. You can also use the V6 administrative console which runs in the deployment manager for the cell. For more information about using the administrative console, see Deploying and managing with the GUI.

All command line tools function relative to a particular profile. If you run a command from a app_server_root/bin directory, the command runs within the default profile. To specify a different profile, use one of the following methods:
  • Specify the -profileName option. The profile that you specify with this option will be used instead of the default profile. For example:
    1. Change to the app_server_root/bin directory.
    2. Type the following command: 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. For example, run the command from the bin directory of the MyProfile profile:
    1. Change to the profile_root/bin directory.
    2. Type the following command: startServer server1

    In this example, the command will function inside the MyProfile profile.

For more information about using profiles, including how to obtain a list of profiles, see the wasprofile command article.

To use the command line tools, perform the following steps:

Procedure

  1. Open a system command prompt.
  2. Change directories to the app_server_root/bin directory.
  3. Run the command.

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.




Sub-topics
Example: Security and the command line tools
wasprofile command
startServer command
stopServer command
startManager command
stopManager command
startNode command
stopNode command
addNode command
serverStatus command
removeNode command
cleanupNode command
syncNode command
backupConfig command
restoreConfig command
EARExpander command
GenPluginCfg command
versionInfo command
genVersionReport command
historyInfo command
genHistoryReport command
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/txml_command.html

© Copyright IBM Corporation 2004, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)