| Node State 
				 | 
 
				 The actual state of the node as reported by the runtime. 
				   
					 - Not Installed - after a node has been created and before is has been installed 
					 
 
 
					 - Not Running - after a node has been installed or when it was detected that the node ended without being stopped by the host. This applies when the process is detected as stopped. 
					 
 
 
					 - Stopping - Stopping a node is expected to be a quick activity. If the node is stuck at Stopping for more than a few minutes, checking the logs may indicate the problem. 
					 
 
 
					 - Stopped - the node was explicitly stopped. This is a normal and expected condition. 
					 
 
 
					 - Starting - Starting a node is expected to be a quick activity. If the node is stuck at Starting for more than a few minutes, checking the logs may indicate the problem. 
					 
 
 
					 - Start Failed - The host was not able to start the node process. Possible causes are that the 
						node_classpath.tra file contains errors, the JRE libraries are not found, or the OS is unable spawn additional processes. After this state ,the node is disabled and must be manually enabled. 
					 
 
 
					 - Running 
					 
 
 
				   
 
				  Note: The 
					  node.tra file has the property 
					  java.property.com.tibco.tibjms.connect.attempt.timeout=3000 to alert when EMS server in unresponsive. However, the setting does not provide an alert for closing connections and sessions. 
				    
 
				 | 
 
			 
 
			  
				| Action History 
				 | 
 
				 The outcome of the last action performed with the intent of affecting the runtime state. 
				 |