Setting up the server-management environment for Liberty by using collectives
To set up the server-management environment for the Liberty by using collectives, define the appropriate features in the server.xml file and run the corresponding collective command-line tasks to establish the administrative domain security configuration.
About this task
You can use collectives to manage multiple servers from a single management domain. For high availability, you can configure collective replica sets, clusters, or scaling. For general information about collectives, see Collective architecture.
Liberty provides multiple-server management in the following features:
collectiveController-1.0feature enables controller functionality for a management collective and includes collective- and cluster-management MBeans that are accessible using the REST JMX connector that is provided by the
restConnector-2.0feature is tolerated. The collective controller acts as a storage and collaboration mechanism to which collective members can connect. The administrative domain security configuration for the
collectiveController-1.0feature is established using the collective command-line create and replicate tasks. For details about the feature, see Collective Controller.
collectiveController-1.0feature 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.0feature to work with collective members from single-server products.
collectiveMember-1.0feature enables a server to be a member of a management collective and be managed by the collective controller. The administrative domain security configuration for the
collectiveMember-1.0feature is established using the collective command-line join task. For details about the feature, see Collective Member.Tip: All servers enabled with the
collectiveController-1.0feature are managed; therefore, you do not need to specify
collectiveMember-1.0if the server already has the
The cluster member feature enables a collective member to participate in a static cluster. For details about the feature, see Static Cluster Member.
Configure a server to act as collective controller.
- Create a collective controller server by using commands and then configure the controller server.xml file. See step 1 of Configuring a Liberty collective.
- Create a collective controller by using developer tools. See step 1 of Configuring a Liberty collective using the developer tools.
Join a server to a collective as a member.
- Join a server to a collective using commands and then configure the member server.xml file. See step 2 of Configuring a Liberty collective.
- Join a server to a collective using developer tools. See step 2 of Configuring a Liberty collective using the developer tools.
Change the collective configuration as needed for your environment.
- Register host computers with a collective.
- Override host information by revising parameters
hostAuthInfoelement of the member server.xml file.
- Set up Remote Execution and Access (RXA) to enable collective controllers to start and stop servers.
- Set the
JAVA_HOMEvariable for Liberty collective members.