Fix Pack 8550

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.
Note: The collectiveController-1.0 feature and its capabilities are available only in WebSphere® Application Server Liberty Network Deployment and WebSphere Application Server Liberty for z/OS®. The feature is not available in WebSphere Application Server Liberty, WebSphere Application Server Liberty - Express®, or WebSphere Application Server Liberty Core. If you have a WebSphere Application Server Liberty Network Deployment installation, you can use its collectiveController-1.0 feature to work with collective members from WebSphere Application Server Liberty, WebSphere Application Server Liberty - Express, or WebSphere Application Server Liberty Core installations.

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.

To register a host with a collective controller, update host information, and unregister a host, use the registerHost, updateHost, and unregisterHost commands. Specify the host computer name in one of the following formats:
  • 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
Note: When a Liberty server is joined to a collective, the associated host is automatically registered with the collective controller if it has not already been registered.

A host can be registered with the collective under different names. It is important 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.


Icon that indicates the type of topic Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-iseries&topic=tagt_wlp_registerhost
File name: tagt_wlp_registerhost.html