Setting up SSH on Windows servers

WebSphere Automation requires remote access to managed servers to apply security fixes or to collect the heap dump information. WebSphere Automation and the managed servers must be properly configured to allow for remote access.

Before you begin

Each Windows server must have Win32-OpenSSH External link icon installed. WebSphere Automation connects to monitored servers over SSH using a specified user account. Therefore, each server must also be configured and accessible using the same user account and SSH key. The user account must have permissions to run the wsadmin script (for WebSphere Application Server) or the server script (for WebSphere Application Server Liberty) and access the heap dump file that is generated by WebSphere Application Server or WebSphere Application Server Liberty.

Make sure that servers to be managed meet the prerequisites in Managed server requirements.

If you have an existing SSH key that you want to use, skip this step and proceed to Setting up WebSphere Automation for SSH to Windows servers.

Procedure

Since the same SSH key and user is used to access all WebSphere Application Server and WebSphere Application Server Liberty servers, create a separate user and SSH key specifically for use by WebSphere Automation.

Avoid using privileged user accounts such as Administrator or root. See Setting up SSH on Linux or Unix servers for instructions on how to generate a new SSH key.

What to do next

Proceed to Setting up WebSphere Automation for SSH to Windows servers.