stopNode command
The stopNode command reads the configuration file for the Network
Deployment node agent process and sends a Java Management Extensions (JMX)
command telling the node agent to shut down. By default, the stopNode command
waits for the node agent to complete shutdown 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 stopNode command.
You must run this command from the install_root/bin directory of
a WebSphere Application Server installation.
If you stop the server before stopping the node agent using the stopserver
-servers command, the server will not restart when you issue a startserver command.
Syntax
The command syntax is as follows:
stopNode [options]
Parameters
The following options are available for
the stopNode command:
- -nowait
- Tells the stopNode command not to wait for successful shutdown
of the node agent process.
- -quiet
- Suppresses the progress information that the stopNode command prints
in normal mode.
- -logfile <fileNname>
- Specifies the location of the log file to which information gets written.
- -replacelog
- Replaces the log file instead of appending to the current log.
- -trace
- Generates trace information into a file for debugging purposes.
- -timeout <seconds>
- Specifies the waiting time for the agent to shut down before timing out
and returning an error.
- -statusport <portNumber>
- Specifies that an administrator can set the port number for server status
callback.
- -stopservers
- Stops all application servers on the node before stopping the node agent.
- -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 Remote Method Invocation (RMI).
- -port <portNumber>
- Specifies the node agent JMX port to use explicitly, so that you can avoid
reading configuration files to obtain the information.
- -username <name>
- Specifies the user name for authentication if security is enabled in
the node agent. Acts the same as the -user option.
- -user <name>
- Specifies the user name for authentication if security is enabled in
the node agent. Acts the same as the -username option.
- -password <password>
- Specifies the password for authentication if security is enabled in the
node agent.
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.
Note: When requesting help for the
usage statement for the stopNode command, a reference to the stopServer command
displays. All of the options displayed for this usage statement apply to the stopNode command.
- -?
- Prints a usage statement.
Note: When requesting help for the
usage statement for the stopNode command, a reference to the stopServer command
displays. All of the options displayed for this usage statement apply to the stopNode command.
Usage scenario
The following examples demonstrate
correct syntax:
stopNode
stopNode -nowait
stopNode -trace (produces the stopnode.log file)
Searchable topic ID:
rxml_stopnode
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/rxml_stopnode.html