Stopping a TIBCO Host

As a Service or Executable Process

Windows
  • If the instance is registered as a Windows service:
    1. Open the Windows Services application.
    2. Click TIBCO ActiveMatrix hostName.
    3. Click Stop.
  • Run CONFIG_HOME\tibcohost\instanceName\host\bin\tibcohost.exe stop -wait true .
UNIX Run CONFIG_HOME/tibcohost/instanceName/host/bin/tibcohost stop -wait true.

The Node processes managed by the TIBCO Host instance are stopped and the tibcohost process is stopped.

Using GUI

  1. Navigate to Hosts list.
  2. In the Hosts list, select one or more Hosts.
  3. Choose a stop option.
    • Stop: TIBCO Host stops without waiting for each node to stop. This takes only a few seconds.
    • Stop with wait: With this option, nodes stop first, and then the host stops.
On successful stop, the Host State displays as Stopped.
Note: You cannot stop SystemHost using Administrator UI.

Using CLI

Example of data.xml

<Host name="SecondHost"/>

Attributes

Attribute

Required/Optional Description
name Required Name of the TIBCO Host instance being stopped (it must be already added)
Any other attribute The stop action ignores all other attributes. The sourceHost is also ignored, since the stop command is sent to the running TIBCO Host directly.

Example of build.xml

<AMXAdminTask action="stop" objectSelector="Host" options="..."/>
The options attribute is optional. The only value supported for this action is wait, which is equivalent to tibcohost command-line argument -wait true (applies to the stop command).

What to Expect After Stopping a TIBCO Host

  • On successful stop, the TIBCO Host instance operating process gracefully terminates. In TIBCO ActiveMatrix Administrator, the Host state displays as "Stopped".
  • On a failure to stop, the Action History displays as "Stop Failed".
  • With no options specified, the default wait mode is "false", which means the TIBCO Host stops without waiting for each node to stop. This takes only a few seconds. Specifying the wait option takes a lot longer as the host stops only after all nodes have stopped.

Handling Nodes Configured for Manual Startup

At present, when TIBCO ActiveMatrix Host is stopped, all Nodes managed by that Host are stopped irrespective of their startup mode, that is, Nodes configured for manual startup are also stopped. To prevent the stopping of Nodes configured for manual startup, a new TRA property com.tibco.amx.decouple.Manual.Nodes has been introduced. This property is used during Host startup and shutdown to determine the behavior of the Nodes configured for manual startup. As a result, the lifecycle of these Nodes is decoupled from the Host lifecycle, and as a result, the Nodes do not get affected when the Host is stopped/started, and their shutdown/startup can be handled manually.

When the property com.tibco.amx.decouple.Manual.Nodes is set to true in Host's TRA file:

  1. Host shutdown will not stop any Nodes running on that Host and only the Host will be stopped i.e. all Nodes on Host will stay in "RUNNING" state after the Host is stopped.
  2. Host startup will reconnect to all its managed Nodes that are running regardless of their startup mode i.e. the Host will acknowledge all managed Nodes that are running including the Nodes configured for manual startup. If the managed Nodes are not running:
    1. Nodes configured for automatic startup will be started.
    2. Nodes configured for manual startup will not be started.

When the property com.tibco.amx.decouple.Manual.Nodes is set to false in Host's TRA file, it will have no effect, that is, the Host and Nodes will continue to behave as before. The default value of the TRA property is false.

Note:
  • If existing Host is running as a Windows Service, the Service needs to be updated in order for the Host to pick up the property. The Service can be updated by executing the following command: 
    tibcohost.exe --update
  • If the Host is stopped with the TRA property set, it is recommended that it also be started with the TRA property set to avoid inconsistent status of Nodes. If this property is not set during Host startup, then Nodes (configured for manual startup and in RUNNING state at the time of Host being stopped with this property set), will go into STOPPED state and will need to be started manually through Administrator UI or CLI.
  • This TRA property is applicable to Hosts only and has no meaning if set in Node's TRA file.
  • The TRA property can be permanently applied the installation by adding it to the tibcohost.tra template file so that the newly created Hosts can automatically inherit it. To achieve this, add the property to tibcohost.tra template located inside the TIBCO_HOME/tibcohost/<version>/templates folder.