Setting up WebSphere Automation for WinRM to Windows servers

To collect the heap dump information from managed servers, both WebSphere Automation and the servers must be properly configured to communicate by using SSH. Configure WebSphere Automation to communicate with WinRM on your Windows servers.

About this task

WebSphere Automation must be configured with the SSH key, user, and other necessary connection parameters to access the WebSphere Application Server or WebSphere Application Server Liberty servers remotely.

Procedure

Create the wsa-ansible-win secret in the WebSphere Automation namespace with your SSH connection parameters:

oc create secret generic wsa-ansible-win \
   --from-literal=ansible_user=<winrm_username> \
   --from-literal=ansible_connection=winrm \
   --from-literal=ansible_winrm_server_cert_validation=ignore \
   --from-literal=ansible_port=<winrm_port> \
   --from-literal=ansible_winrm_scheme=https \
   --from-literal=ansible_winrm_transport=certificate \
   --from-literal=ansible_python_interpreter=<path_to_python> \
   --from-file=ansible_winrm_cert_pem=<ansible_winrm_cert_pem> \
   --from-file=ansible_winrm_cert_key_pem=<ansible_winrm_cert_key_pem>

Refer to the following example.

oc create secret generic wsa-ansible-win \
   --from-literal=ansible_user=ansiblerunner \
   --from-literal=ansible_connection=winrm \
   --from-literal=ansible_winrm_server_cert_validation=ignore \
   --from-literal=ansible_port=5986 \
   --from-literal=ansible_winrm_scheme=https \
   --from-literal=ansible_winrm_transport=certificate \
   --from-literal="ansible_python_interpreter=C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.9" \
   --from-file=ansible_winrm_cert_pem=./ansible_winrm_cert_pem \
   --from-file=ansible_winrm_cert_key_pem=./ansible_winrm_cert_key_pem

If the Python executable on the target machine is not in the system path, or is not named python or python3, the ansible_python_interpreter parameter must added during the secret creation.