Restarting a TIBCO Host

For large deployments, you might need to change the configuration of a Host frequently and then restart the Host to make sure the changes are reflected in the Administrator. Using this option, you can easily apply all the changes related to the Host.

Note: “SystemHost” (Administrator Host) cannot be restarted for security reasons.

Pre-requisites

  • TIBCO Host must be running.
  • If a source Host is provided, the Source Host must be running and it should not be in the restart process.
  • If a source Host is not provided, at least one Host must be running on the same machine (on which the Host is to be restarted) and it should not be in the restart process.

GUI

Using the GUI, you can restart a single Host or multiple running Hosts which are on the same machine and bound to the same Administrator.

  1. Navigate to Infrastructure > Hosts.
  2. In the Hosts list, select one or more Hosts.
  3. Click Restart.

    The Nodes on the Host are stopped first and then the Host is stopped. After that, TIBCO Host is started with the clear cache mode.

On a successful restart, the Host State displays as "Running". Any nodes (with start-up type of "Automatic") also restart following the TIBCO Host restart. The overall action takes longer to complete, the more nodes there are to be restarted.

CLI

Using the CLI, you can also restart TIBCO Hosts which are on different machines but bound to the same Administrator.

The data.xml file is identical to that shown for start action.

Example of build.xml

<target name="restart">
		<AMXAdminTask
			remote="true"
			propsFile="${instanceProperties}"
			action="restart"
			dataFile="${dataFile}"
			objectSelector="Host"
			failOnError="false"/>
</target>

Example of restart action using CLI

Command: 

D:\installation\data\admin\amxadmin\samples> ant -f host_build.xml restart

Sample output: 

Buildfile: host_build.xml

restart:
[AMXAdminTask] 26 Jun 2017 16:49:45  INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode
[AMXAdminTask] 26 Jun 2017 16:49:45  INFO - Connecting to AMX Admin server at 'http://kavalask-w540:8120' as user 'root'.
[AMXAdminTask] 26 Jun 2017 16:49:46  INFO - Executing action 'restart' for 1 objects from data file 'D:\installation\data\admin\amxadmin\samples\host_data.xml'
[AMXAdminTask] 26 Jun 2017 16:49:47  INFO - Restarting Host 'SecondHost' in background
[AMXAdminTask] 26 Jun 2017 16:49:47  INFO - Action finished in Admin at 26/6/17 4:49 PM in 0.125 seconds. Waiting for runtime tasks to be finished. Action tracked in log(s) by action-id [root:Host-Restart:15]
[AMXAdminTask] 26 Jun 2017 16:49:48  INFO - .
[AMXAdminTask] 26 Jun 2017 16:49:52  INFO - .
[AMXAdminTask] 26 Jun 2017 16:49:57  INFO - .
[AMXAdminTask] 26 Jun 2017 16:50:00  INFO - Host Restart finished successfully
[AMXAdminTask] 26 Jun 2017 16:50:00  INFO - Action finished at 26/6/17 4:50 PM in 13.704 seconds

BUILD SUCCESSFUL
Total time: 17 seconds

What to Expect After Restarting a TIBCO Host

  • Launches the TIBCO Host executable on the remote machine (same as the Source TIBCO Host).
  • During this process, the Action History displays as "In Progress (Restart)" .
  • On successful restart, the Host state displays as "Running" and Action History displays "Restart Successful".
  • On a failure to start or register, the Host state displays as "Stopped" if it fails after stop action otherwise it displays its previous state and Action History displays as "Restart Failed". The tibcohost.log on the remote machine will provide more information for restart errors.
  • Any nodes (with startup type "Automatic") also restart following the TIBCO Host restart. The higher the number of Nodes to be restarted, the longer it takes for the overall action to complete.
  • This action cannot be performed on a newly created Host in a remote or different CONFIG_HOME as there will be no running Host to perform the action.