This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.
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. The MBean startServer and stopServer methods start and stop a member. You also can run server start and stop commands from a command line.
Prerequisites
- The member server must have the collectiveMember-1.0 feature enabled in its server.xml file.
- The member must be joined to the collective. See Configuring a Liberty collective.
Set up
To enable the collective controller to stop and start a member server, it might be necessary to
add the <hostAuthInfo> element to the member's server.xml
file. By default, each member attempts to use SSH key-based authentication. A pair of RSA keys is
generated on server startup under ${server.config.dir}/resources/security/ssh.
The public key is added to the user's authorized_keys file automatically. The
private key is sent to the controller. If SSH is not available:
For Windows members, you must provide an administrator user ID and password in the <hostAuthInfo> element.
For AIX®, HP-UX, Linux, Solaris, or z/OS® members, use of SSH key-based authentication is recommended. To use a username and password for authentication, specify them in a <hostAuthInfo> element in the server.xml file.
See Overriding Liberty server host information and Setting up RXA for Liberty collective operations for details.
Procedure
- Use the ServerCommands MBean startServer and
stopServer methods to start and stop a collective member.
For information on running the ServerCommands MBean from the controller, see the API documentation for the ServerCommands MBean.
- Run server start and stop commands from a command line. See Starting and stopping a server from the command line.