Stopping Nodes

You can stop a node using the Administrator GUI or CLI. If the Administrator server is not running, you can stop the node by stopping the TIBCO Host instance that manages the node.

GUI

Procedure

  1. Infrastructure > Nodes
  2. Click one or more nodes.
  3. Choose a stop option.
    Option Description
    Stop or Stop > Stop Stops the nodes. Components running on the node are notified and allowed to finish work. The components may take a few minutes to an hour to stop.
    Stop > Stop immediately Stops the nodes. Components running on the node are notified and allowed to perform clean up operations such as closing connections. The components typically take a few seconds to stop.
    Stop > Terminate node process Stops the nodes. Supported only for nodes running on a host of type TIBCO Host. Components running on the node are not notified before the node is stopped.

CLI

Procedure

  1. In the data file, specify an Environment and one or more Node definitions in base format. You can also use a data file previously used to create the nodes in which the nodes are specified in full format. 
    <Environment name="DevEnvironment" 
		<Node name="node1"/>
		<Node name="node2"/>
</Environment>
  2. In the build file, set the action attribute of the AMXAdminTask element to stop, the options attribute to nothing, immediate, or terminate, and the objectSelector attribute to Environment/Node. 
    <AMXAdminTask action="stop" objectSelector="Environment/Node" />

Handling Nodes Configured for Manual Startup

For more information on handling Nodes configured for manual startup, refer to Handling Nodes Configured for Manual Startup.