Runtime State
Hosts and Nodes are the runtime processes that Administrator interacts with. They have a state that is displayed in Administrator under the Runtime State column.
The runtime state typically changes when you invoke an action in Administrator. For example, a node goes into a Running state shortly after you execute the Start action on it. The runtime state might also change due to events that occur outside of Administrator. Powering down a machine stops nodes, booting a machine starts them. If you end the node process, its state changes to Not Running.
As the runtime state changes dynamically, Administrator tracks state changes in real time through notification messages it receives from the notification server. Refresh the Administrator UI periodically to display the updated status of the objects.
Applications also have a runtime state. The Administrator displays the state of an application by aggregating and summarizing the state based on all its components, including the bindings, that are distributed on multiple nodes. For example, if an application fails to start, the runtime state displays Start Failed. If some application components are running and some are explicitly stopped, the runtime state shows Partially Running.
When a runtime action has completed for some components, the runtime state shows Partially runtime action. For example, when you undeploy an application you might see Partially Undeployed.