The stopManager command reads the configuration file for the Network
Deployment 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 the Using command tools article.
Note: Although the stopServer command returns control when the server completes shut down, it can return before the OS/400 process has terminated. Depending upon the amount of memory which the Java Virtual Machine must return to the memory pool, the process may take several seconds or minutes to completely end. You should not attempt to start the server again until the process has terminated. Use the WRKACTJOB SBS(subsystem) CL command to determine if the process has terminated completely. By default, subsystem is QWAS6.
Syntax
The command syntax is as follows:
stopManager [<server>] [options]
Parameters
The following options are available for the stopManager command:
-nowait
Tells the stopManager command not to wait for successful shutdown of the deployment manager process.
-quiet
Suppresses the progress information that the stopManager command prints in normal mode.
-logfile <fileName>
The location of the log file to which information is written.
-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
Enables tracing of the native process code that starts the application server. The trace output is written to file jobname/jobuser/jobnum located under /QIBM/UserData/WebSphere/AppServer/V6/service/trace.
-timeout <seconds>
The waiting time for the manager to complete shutdown before timing out and returning an error.
-statusport <portNumber>
That an administrator can set the port number for server status callback.
-conntype <type>
The Java Management Extensions (JMX) connector type to use for connecting to the deployment manager. Valid types are Simple Object Access Protocol (SOAP) or Remote Method Invocation (RMI).
-port <portNumber>
The deployment manager JMX port to use explicitly, so that you can avoid reading the configuration files to obtain information.
-username <name>
The user name for authentication if security is enabled in the deployment manager. Acts the same as the -user option.
-user <name>
The user name for authentication if security is enabled in the deployment manager. Acts the same as the -username option.
-password <password>
The password for authentication if security is enabled in the deployment manager.
Note: 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 -profileName dmgr (stops the deployment manager for the dmgr profile)
stopManager -nowait
stopManager -trace (produces trace files under /QIBM/UserData/WebSphere/AppServer/V6/service/trace)