Setting up RXA for Liberty collective operations
Liberty collective controllers use the Tivoli® Remote Execution and Access (RXA) toolkit to perform selected operations on collective members. Use RXA to remotely start and stop servers, including starting and stopping servers on your local computer.
Procedure
Install and enable SSH on your machine. For Linux and UNIX machines, ensure that the configuration is set according to the following instructions. For z/OS® machines, consult the following instructions for guidance.
To enable SSH, configure OpenSSH 3.6.1, OpenSSH 4.7 (on AIX), or Oracle SSH 1.1 so that it supports RXA connections. OpenSSH 3.7.1 or later contains security enhancements not available in earlier releases and is recommended.
RXA does not supply SSH code for UNIX operating systems. You must ensure that SSH is installed and enabled on all machines that include collective members.
In all UNIX environments except Solaris, the Bourne shell (sh) is used. On Solaris machines, the Korn shell (ksh) is used instead due to problems encountered with the Bourne shell (sh).
To use password-based authentication for SSH communications, edit the /etc/ssh/sshd_config file on each machine that includes one or more collective members. Set the PasswordAuthentication property to yes. For example:
The default value for the PasswordAuthentication property is no.PasswordAuthentication yesAfter you change this setting, stop and restart the SSH daemon by using the following commands:/etc/init.d/sshd stop /etc/init.d/sshd start
What to do next
If you modify the server.xml of a managed server, manually start the server so that it publishes the new data to the controller.
After you enable RXA, test the host configuration and verify RXA connectivity.

Task topic