To set up the server-management environment for the Liberty profile 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
- collectiveController-1.0
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. - collectiveMember-1.0
These features can be combined in various servers to define a custom management topology.
The collectiveController-1.0 feature enables controller functionality for a management collective and includes collective- and cluster-management MBeans that are accessible using the JMX/REST connector that is provided by the restConnector-1.0 feature. 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.0 feature is established using the collective command-line create and replicate tasks.
The collectiveMember-1.0 feature enables a server to be a member of a management collective, allowing it to be managed by the collective controller. The administrative domain security configuration for the collectiveMember-1.0 feature is established using the collective command-line join task.
Subtopics
- Configuring a Liberty collective
You can organize Liberty servers into collectives to support clustering, administration, and other operations that act on multiple Liberty servers at a time in order to efficiently and accurately deliver application services to your organization. - 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. - Overriding Liberty server host information
The collectiveMember-1.0 feature enables a server to be managed by the collective controller. Most server host information can be automatically detected. In certain scenarios, however, you must provide additional host information so that the collective controller can establish a connection to the server. - Setting the JAVA_HOME variable for Liberty collective members
All Liberty collective members should have a Java™ Runtime Environment (JRE) installed that meets the minimum requirements of the Liberty server. - Configuring Liberty collective replica sets
You can configure collective replica sets. - Liberty profile: Collective architecture
The set of Liberty servers in a single management domain is called a "collective." A collective consists of at least one server with the collectiveController-1.0 feature enabled that is called a “collective controller.” Optionally, a collective can have many servers with the collectiveMember-1.0 feature enabled that are called "collective members" and a collective can be configured to have many collective controllers. - Liberty profile: Collective security
This article provides an overview of collective security. - Configuring a Liberty collective
You can organize Liberty servers into collectives to support clustering, administration, and other operations that act on multiple Liberty servers at a time in order to efficiently and accurately deliver application services to your organization. - Overriding Liberty server host information
The collectiveMember-1.0 feature enables a server to be managed by the collective controller. Most server host information can be automatically detected. In certain scenarios, however, you must provide additional host information so that the collective controller can establish a connection to the server. - Starting and stopping a Liberty collective member
The collective controller provides a ServerCommands MBean that can be used to start or stop a collective member. - 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. - File transfer in a Liberty collective
The FileTransfer and FileService MBeans can be used in a Liberty collective to perform file actions on any Liberty server in the collective. This includes both Liberty servers configured as collective controllers and those configured as collective members. - Setting the JAVA_HOME variable for Liberty collective members
All Liberty collective members should have a Java Runtime Environment (JRE) installed that meets the minimum requirements of the Liberty server. - Liberty collective troubleshooting
This article contains a list of common issues that you might encounter.
Task topic