Network Deployment (Distributed operating systems), v8.0 > Reference > Command-line utilities
stopManager command
The stopManager command reads the configuration file for the WAS ND manager process.
It sends a Java Management Extensions (JMX) command to the manager telling it to shut down. By default, the stopManager command waits for the manager to complete the shutdown process before it returns control to the command line. There is a -nowait option to return immediately, as well as other options to control the behavior of the stopManager command. For more information about where to run this command, see Using command-line tools.
If you are using a Windows operating system and the we have the dmgr running as a Windows service, the stopManager command stops the associated Windows service and it is responsible for stopping the dmgr.
The command syntax is as follows:
stopManager [options]
Parameters
The following options are available for the stopManager command:
-nowait
Tells the stopManager command not to wait for successful shutdown of the dmgr process.
-quiet
Suppresses the progress information that the stopManager command prints in normal mode.
-logfile <fileName>
Location of the log file to which trace information is written. By default, the log file is named stopServer.log and is created in your logs directory.
-profileName
Defines the profile of the Application Server process in a multi-profile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.
-replacelog
Replaces the log file instead of appending to the current log.
-trace
Generates trace information to a file for debugging purposes. The trace output is written to the stopmanager.log file which is located in the PROFILE_ROOT/logs directory.
-timeout <seconds>
Waiting time for the manager to complete shutdown before timing out and returning an error.
-statusport <portNumber>
An optional parameter that allows an administrator to set the port number for dmgr status callback. The tool opens this port and waits for status callback from the dmgr just before the dmgr has completely stopped. If the parameter is not set, an unused port is automatically allocated.
-conntype <type>
Specifies the Java Management Extensions (JMX) connector type to use for connecting to the dmgr. Valid types are SOAP or RMI.
-port <portNumber>
Deployment manager JMX port to use explicitly, so that you can avoid reading the configuration files to obtain information.
-username <name>
User name for authentication if security is enabled in the dmgr. Acts the same as the -user option.
-user <name>
User name for authentication if security is enabled in the dmgr. Acts the same as the -username option.
-password <password>
Password for authentication if security is enabled in the dmgr. If you are running in a secure environment but have not provided a user ID and password, you receive the following error message:
ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.To solve this problem, provide the user ID and password information.
-help
Prints a usage statement.
-?
Prints a usage statement.
Usage scenario
The following examples demonstrate correct syntax:
stopManager stopManager -nowait stopManager -trace (produces the stopmanager.log file)
Use command-line tools