Using the Liberty
Utilities menu in the developer tools, you can create a collective controller
or join a collective.
Using the developer tools simplifies the process of configuring a Liberty collective by providing convenient
utilities for creating collective controllers or joining collectives. For more information about Liberty collectives, see Configuring a Liberty collective.
-
Creating a collective controller:
Note: Creating a collective controller can be done only with the following editions:
- WebSphere® Application Server Network Deployment Liberty
- WebSphere Application Server for z/OS® Liberty
-
In the Servers view, right-click your Liberty server, and select .
-
In the Keystore password field, type a password for your
collective.
-
Click Finish.
Results:
An information dialog appears after the collective configuration is complete. This
dialog informs you that the server.xml file was already updated to include the
generated configuration file. If there are instructions to add the configuration lines to the
server.xml in the console output, they can be ignored. However, Administrative
Security and other settings might still need to be configured within the included configuration file
before any collective members can join.
-
Joining a collective controller:
Note: You must have a collective controller available before a server can be added to a collective.
Joining a collective can be done with the following editions:
- WebSphere Application Server Liberty
- WebSphere Application Server Liberty Core
-
In the Servers view, right-click your Liberty server, and select .
-
On the Join Collective page, specify the information of the collective
controller you would like to join.
-
In the Host field, type in the host name for the collective
controller.
-
In the Port field, type in the port number for the collective
controller.
-
In the User field, type in the user name for the collective
controller.
-
In the Password field, type in the password for the collective
controller.
-
In the Keystore password field, type the keystore password for the
collective controller if encryption was used.
-
Click Finish.
Results:
An information dialog appears after the collective configuration is complete. This
dialog informs you that the server.xml file was already updated to include the
generated configuration file. If there are instructions to add the configuration lines to the
server.xml in the console output, they can be ignored.