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.0

    The collectiveController-1.0 feature 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-1.0 feature. The restConnector-2.0 feature 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.0 feature is established using the collective command-line create and replicate tasks. For details about the feature, see Collective Controller.

    For distributed platformsFor IBM i platformsThe 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.

  • collectiveMember-1.0
    The collectiveMember-1.0 feature 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.0 feature 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.0 feature are managed; therefore, you do not need to specify collectiveMember-1.0 if the server already has the collectiveController-1.0 feature enabled.
  • clusterMember-1.0

    The cluster member feature enables a collective member to participate in a static cluster. For details about the feature, see Static Cluster Member.

Procedure