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. You can use RXA to remotely start and stop servers, including servers on your local computer.
Before you begin
Stabilized feature: The Server Message Block (SMB) protocol allows for remote method execution on Windows and is used by collectives. Version 1 of the SMB
protocol (SMBv1) is insecure and should be disabled. As an alternative, install
Cygwin as a SSH service on collective members and use SSH to connect to them. RXA
is not compatible with Windows OpenSSH. Disable Windows OpenSSH before installing and running
Cygwin.
Procedure
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.
You can use the testConnection command to verify connectivity. The command validates RXA connectivity between the controller and the host where the member resides.
wlp/bin/collective testConnection hostName --host=controllerHost
--port=controllerHTTPSPort --user=controllerAdmin
--password=controllerAdminPassword--autoAcceptCertificates
Alternatively, use the simplified
--controller
option to provide the controller specific
informationwlp/bin/collective testConnection hostName
--controller=user[:password]@host:HttpsPort
--autoAcceptCertificates