Binding Hosts to an Administrator Server

When you bind a host to an Administrator server, the host and all the nodes the host manages are managed by the server.

Prerequisites

When the host is created, it must be configured to use the same Enterprise Message Service notification server and enterprise name as the Administrator server to which it will be bound.

Note: If you create a TIBCO Host instance, you cannot use that instance with an older version of the Administrator server.

Procedure

  1. Select Infrastructure > Hosts.
    The Hosts screen displays.
  2. Choose whether to discover hosts or register a known host.
    Option Description
    Discover
    1. Click Discover.
    2. Click Start Discovery.
    3. In the Discovered Hosts list, check the checkboxes next to each host to bind and type a name in the Name column.
    4. From Assign to Environment drop-down list, select an environment or All.
    5. Click Bind.
    Register
    1. Click Register.
    2. In the Name field, type a name for the host.
    3. In the Management URL field, change the machine and port to the machine and port of the host to bind.
    4. To enable secure communication between the host and Administrator server, check the Secure checkbox.
    If a host is bound to another Administrator server, the bind fails. Otherwise, the host binds to the Administrator server.
  3. If the host is bound to another server you can take control of it by checking the Force Bind checkbox and clicking Bind.
    First run with Force Bind unchecked to see if the host is already bound. That way you can investigate if this is really a host you should be binding to. If you determine that it you can take control of the host from another Administrator server, only then should you use the force option.
    With the Force Bind checked, even if the host is already bound, the bind does not throw an error. Instead the host severs its connection with the existing Administrator server, and bind to this Administrator server.