How to connect to putty using Uipath terminal activity

Help Activities
, ,
1

I want to understand what parameters needs to be filled in terminal connection while trying to connect to Putty in UiPath i.e whether to use direct connection, IBM EHLLAPI , attachmate reflection etc.
I tried using direct connection but the parameters which I was using was unable to connect to putty terminal. Also, the application which I am trying to interact within putty is an .net application plus terminal which is an SSH.

2

Hi @Yelugam_Sarvesh_Cognizant

Welcome to UiPath,

Pls check this,

OR

Unable to open putty window using Start Process activty? - Help / Activities - UiPath Community Forum

Happy Automation

3

https://forum.uipath.com/search?q=putty

4

@Yelugam_Sarvesh_Cognizant,

Try this answer from the LLM. Share the screenshot if the below approaches don’t work

Based on the UiPath documentation, setting up a terminal connection in UiPath (especially with a third‐party emulator like PuTTY) depends on the type of provider you select. In the connection dialog you’ll notice that depending on the provider (for example, Direct/UiPath implementation, IBM EHLLAPI, or Attachmate Reflection) the required fields change.

For example:

  1. Direct Connection / UiPath Implementation
    – This option is used when you do not rely on a pre‐configured profile or a DLL from a third-party emulator. In this case you must manually enter:
  • Address: This is the server’s hostname or IP where the SSH service runs.
  • Port: Typically, for SSH connections (like those made with PuTTY) you would use port 22 (unless your environment uses a different one).
  • Terminal Type: For a Putty SSH terminal, you’d usually select “VT” (VT100/VT220-like terminals are typically used for SSH sessions).Note: If you’re working with a .NET application inside the PuTTY terminal, choosing the UiPath implementation with these parameters can often be the simplest method if you are not integrating with legacy terminal emulators.
  1. IBM EHLLAPI
    – This option is intended for emulators that implement the EHLLAPI standard (such as IBM Personal Communications, Attachmate Extra, or Micro Focus Rumba). In this case you are not providing a typical address and port. Instead you need to:
  • Launch the terminal emulator (PuTTY in your case would need to support or be configured to expose EHLLAPI, which is not common).
  • Fill in additional fields such as the path to the EHLLAPI DLL (for IBM Personal Communications it would be something like “pcshll32.dll”) and provide a session short name for an existing session.Remark: This method is more suitable if you are working with the traditional mainframe emulators rather than PuTTY.
  1. Attachmate Reflection (or similar providers)
    – If you were connecting via a profile file (for example, a rd5x/rd3x file for TN3270/TN5250 sessions), you would browse for the profile file.Note: This provider is not usually used for SSH connections via PuTTY.

Given that your target application is a .NET application running within an SSH session in PuTTY, the recommended approach is to use the Direct connection (often implemented by UiPath as the “UiPath implementation”). In that case, you should:

  • Use the Direct Connection fields and provide the following:
    • Address: Enter the SSH server’s address.
    • Port: Use your SSH port (commonly 22).
    • Terminal Type: Choose the VT type (which fits most SSH sessions).

If your parameters using direct connection were not working, please verify that:

  • The SSH server is reachable from the UiPath robot machine, and there are no firewall or network issues.
  • The port number provided is indeed the one that the SSH server is listening on.
  • The terminal type (VT) matches the type that PuTTY is expecting, or adjust accordingly if your SSH server requires a different terminal type.

By ensuring these settings, you should be able to connect to your Putty (SSH) session from within UiPath. For additional details, you can refer to the UiPath KB article on automating terminals and mainframes

5

  1. Install UiPath Terminal Activities Package

  2. Use ‘Terminal Session’ Activity
    Drag and drop the Terminal Session activity into your workflow.
    In the Connection Type, select “Windows-based” (for connecting via PuTTY).

  3. Configure Terminal Session
    Set Connection Type = “Windows-based”.
    Provider = “UiPath.Internal.Terminal.Windsp”.
    (This uses the built-in Windows terminal emulator like PuTTY.)

  4. Set Arguments (if needed)