![](../graphics/a.gif) |
|
|
NAME
stop-node-agent - stops a node agent
SYNOPSIS
stop-node-agent [agentdir nodeagent_path [terse=false] [echo=false] [interactive=true] ] [nodeagent_name]
The local stop-node-agent command is used to stop a node agent. If the agent directory is not specified, the node agent in the default install_dir/nodeagents directory is stopped. If there is more than one domain, the domain_name operand must be identified. The stop-node-agent command stops all managed server instances of the node agent.
This command is supported in local mode only.
- agentdir
-
Like a Domain Administration Server (DAS), each node agent resides in a top level directory named agentdir/nodeagent_name.
If specified, the path must be accessible in the filesystem. If not specified, the node agent is created in the default install_dir/nodeagents directory.
- t terse
-
Indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well-formatted data for consumption by a script. Default is false.
- e echo
-
Setting to true will echo the command line statement on to the standard output. Default is false.
- I Interactive
-
If set to true (default), only the required options are prompted.
-
nodeagent_name
-
This is the name of the node agent to stop.
Example 1. Using stop-node-agent
This is a basic example of how to use the command.
%asadmin>stop-node-agent nodeagent1
Where: % is the command line prompt. Node agent, nodeagent1, located in default install_dir/nodeagents is stopped.
- 0
-
command executed successfully
- 1
-
error in executing the command
start-node-agent(1), delete-node-agent(1), list-node-agents(1), create-node-agent(1)
J2EE SDK 1.4 | Go To Top | Last Changed 31 Jan 2005 |
Company Info
|
Contact
|
Copyright 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|