Use command line tools

 

+

Search Tips   |   Advanced Search

 

Command line tools are used to start, stop, and monitor local appserver processes and nodes. These tools cannot operate on remote appservers or node. To administer appservers, use wsadmin connected to the dmgr for the cell.

Unless otherwise specified, all appserver commands are located in...

APP_ROOT/bin

Parameter values that specify a server name, a node name or a cell name are case sensitive.

On Windows Vista and Windows Server 2008, we can install Websphere Application Server as either Administrator or non-Administrator. When installed as Administrator, some operations, such as those involving Windows Services, require Administrator privileges. To run commands as Administrator...

1. Right-click a Command Prompt shortcut.

2. Click Run As Administrator.

3. A dialog appears asking to continue. Click Continue.

For a Windows Server Core installation of Windows Server 2008, WAS commands that require a graphical interface are not supported since a Windows Server Core system does not have a GUI. Therefore, commands such as pmt.bat or ifgui.bat are not supported.

 

To run a command

1. Open a system command prompt.

2. Determine whether to run the script from the PROFILE_ROOT or APP_ROOT.

   Most command line tools function relative to a particular profile. To determine if a command requires -profileName, refer to the documentation for that specific command.

   If we run a command from...

   APP_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...

   • From APP_ROOT/bin run...

     startServer server1 -profileName AppServerProfile

   • When a profile is created, the appserver creates a proxy script in...

     PROFILE_ROOT/bin

     ...for each script in...

     APP_ROOT/bin

     ...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. To run the command for a specific profile...

     cd PROFILE_ROOT/bin
     ./mycommand.sh

3. 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. We can override the default location for the command log file using the -logfile option for the command.

 

What to do next

To obtain a list of profiles, run manageprofiles.sh

Example: Security and the command line tools
manageprofiles
startServer
stopServer
stopManager
startNode
stopNode
addNode
serverStatus
removeNode
cleanupNode
syncNode
renameNode
backupConfig
restoreConfig
EARExpander
GenPluginCfg
versionInfo
genVersionReport
historyInfo
genHistoryReport
registerNode
deregisterNode
revokeCertificate
requestCertificate
createCertRequest
queryCertificate

 

Related tasks

Getting started with scripting

 

Related information

retrieveSigners