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.

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.

[18.0.0.1 and later]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
[18.0.0.1 and later]Alternatively, use the simplified --controller option to provide the controller specific information
wlp/bin/collective testConnection hostName 
--controller=user[:password]@host:HttpsPort
--autoAcceptCertificates

Icon that indicates the type of topic Task topic

File name: twlp_set_rxa.html