Registering host computers with a Liberty collective
You can register a host computer with a Liberty collective controller, update host information, or unregister a host. Registration enables the collective controller to access applications, command files, and other resources on the host. Registered hosts are members of the collective.
Before you begin
- Construct a Liberty collective. See Configuring a Liberty collective.
The collectiveController-1.0 feature and its capabilities are available only in multiple-server products such as WebSphere® Application Server Network Deployment Liberty and WebSphere Application Server for z/OS® Liberty. The feature is not available in single-server products such as WebSphere Application Server Liberty, or WebSphere Application Server Liberty Core. If you have a multiple-server product installation, you can use its collectiveController-1.0 feature to work with collective members from single-server products.
- If you need to enable connections to servers on local and remote hosts, complete the steps for
your host operating system in Setting up RXA for Liberty collective operations. The topic provides information about
the Tivoli Remote Execution and Access (RXA) toolkit and
enabling Secure Shell (SSH) protocol. You can use RXA to remotely start and stop servers, including
starting and stopping servers on your local computer, and to transfer files to and from registered
hosts.
Note: In Windows, system environment variables are visible only inside the shell that RXA connects to. Setting PATH in the command window is not sufficient. You must set PATH in the system variable section of the environment variables, or use -hostJavaHome <PATH TO IBM JAVA> with the updateHost option.
About this task
A host computer is not required to have any WebSphere Application Server products installed. There are no software requirements for a host beyond its operating system. The host can be the same computer on which the product is installed or a different computer.
- Fully qualified domain name servers (DNS) host name string, such as xmachine.ibm.com
- Default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
A host can be registered with the collective under different names. Ensure that the host name specified for registerHost, updateHost, and unregisterHost be consistent with the host name used for the registered collective members. The defaultHostName variable in the registered server member's server.xml file controls the host name to which the server considers itself to belong.
Procedure
What to do next
For information about all parameters of the registerHost, updateHost, and unregisterHost commands, see the API documentation for the CollectiveRegistration MBean.