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.
If you are using the Windows platform and the you have the deployment manager running as a Windows service, the stopManager command will start the associated Windows service and it will be responsible for starting the deployment manager.
The command syntax is as followsstopManager [options]
The following options are available for the stopManager command:
- Tells the stopManager command not to wait for successful shutdown of the deployment manager process.
- Suppresses the progress information that the stopManager command prints in normal mode.
- -logfile <fileName>
- Specifies the location of the log file to which information is written.
- 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.
- Replaces the log file instead of appending to the current log.
- Generates trace information to a file for debugging purposes.
- -timeout <seconds>
- Specifies the waiting time for the manager to complete shutdown before timing out and returning an error.
- -statusport <portNumber>
- Specifies that an administrator can set the port number for server status callback.
- -conntype <type>
- Specifies the Java Management Extensions (JMX) connector type to use for connecting to the deployment manager. Valid types are Simple Object Access Protocol (SOAP) or RMI.
- -port <portNumber>
- Specifies the deployment manager JMX port to use explicitly, so that one can avoid reading the configuration files to obtain information.
- -username <name>
- Specifies the user name for authentication if security is enabled in the deployment manager. Acts the same as the -user option.
- -user <name>
- Specifies the user name for authentication if security is enabled in the deployment manager. Acts the same as the -username option.
- -password <password>
- Specifies 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 messageTo solve this problem, provide the user ID and password information.ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.
- Prints a usage statement.
- Prints a usage statement.
The following examples demonstrate correct syntaxstopManager stopManager -nowait stopManager -trace (produces the stopmanager.log file)