Starting a TIBCO Host

As a Service or Executable Process

You first start the SystemHost TIBCO Host instance and can then start other TIBCO Host instances. The process for starting a SystemHost TIBCO Host instance is different on Windows and on Linux.

  • Windows
    • If you created a Windows desktop shortcut, double-click the shortcut.
    • If SystemHost is registered as a Windows service:
      1. Open the Windows Services application.
      2. Click TIBCO ActiveMatrix Admin-enterpriseName-adminServerName.
      3. Click Start.
    • Run CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\host\bin\tibcohost.exe.
  • UNIX

    Run CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/host/bin/tibcohost.

    Certain caveats apply to specific UNIX versions.

    Linux: Disable SELinux with the command sudo echo 0 > /selinux/enforce before running tibcohost.

The tibcohost process is started and the node processes managed by SystemHost, including tibamx_SystemNode, are started.

Using GUI

  1. Navigate to Hosts list.
  2. In the Hosts list, select one or more Hosts.
  3. Choose a start option.
    • Start: Starts TIBCO Host.
    • Start with ClearCache: Starts TIBCO Host with clear cache mode.

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

Using CLI

The data.xml file is identical to that shown for install action. An example of a build.xml file is shown below: 

<AMXAdminTask action="start" objectSelector="Host" options="..."/>

The options attribute is optional. The only value supported for this action is clearCache, which is equivalent to the tibcohost command-line argument -clean (applies to the startNodes command).

What to Expect After Starting a TIBCO Host

  • Launches the TIBCO Host executable on the remote machine (same as the Source TIBCO Host).
  • 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.
  • Automatically registers the TIBCO Host, if it was started the first time after its installation. During this process, the Action History displays as "Start (In Progress)" .
  • On successful start (and registration), the Host state displays as "Running".
  • On a failure to start or register, the Host state displays as "Installed" and Action History displays as "Start Failed" or "Bind Failed" as applicable. The tibcohost.log on the remote machine will provide more information for start errors, and SystemNode.log for registration errors.
  • Register action gets successfully invoked even if a valid management URL is not available. Previously, the register action would fail with an UnknownHost exception.
  • Any nodes (with startup type "Automatic") also start following the TIBCO Host start. The higher the number of Nodes to be started, the longer it takes for the overall action to complete.
    Note: The TIBCO Host instance is always launched as a Windows Service if the Install as Windows Service option is selected.
  • A TIBCO Host instance must be able to connect to the notification server on the configured port (by default, 7222). If this port is blocked by a firewall (the default on Windows systems), the instance will not start.