Fix Pack 8550

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.

Prerequisites

Set up

To enable the collective controller to stop and start a member server, it may be necessary to add the <hostAuthInfo> element to the member's server.xml file. By default, each member will attempt to use SSH key-based authentication. A pair of RSA keys are 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.
    <hostAuthInfo rpcHost="member_host_name"
              rpcUser="admin_user_ID"
              rpcUserPassword="admin_password"
              />
  • For Linux, AIX®, HP-UX, or Solaris members, use of SSH key-based authentication is recommended. If you would like to use a username and password for authentication, specify them in the server.xml file.
    <hostAuthInfo rpcHost="member_host_name"
              rpcUser="user_ID"
              rpcUserPassword="password"
              />

For information on how to construct a Liberty collective, see Configuring a Liberty collective.

For information on running the ServerCommands MBean from the controller, see the API documentation for the ServerCommands MBean.

See Overriding Liberty server host information for more details.


Icon that indicates the type of topic Reference topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Wednesday, 22 May 2013
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=ragt_wlp_servercommand
File name: ragt_wlp_servercommand.html