NamedPipe connection is an interprocess communication (IPC) method that enables communication between two processes, potentially on different machines, using a name such as a file path or identifier.

In Automation 360, NamedPipe connections are used to facilitate secure, high-performance communication between the Bot Agent and Control Room components on the same machine, particularly in environments where network-based communication is restricted or less desirable.

You can customize the number of NamedPipe Client connections in order to enhance the Control Room response rate for automation executions and limit the network traffic. You must add the max.namedpipe.client.per.session= key to configure the number of NamedPipe Client connections.

Any user who has access to the device where the Bot Agent is installed can add the max.namedpipe.client.per.session= key in the nodemanager.properties file.

Procedure

  1. Navigate to C:\Program Files\Automation Anywhere\Bot Agent\config.
  2. Edit the nodemanager.properties file.
    Note: If the value of NamedPipe session attribute is not added in the nodemanager.properties file, then the default value is 50.
  3. Add max.namedpipe.client.per.session= key.
  4. Enter the number for NamedPipe Client connections that you want to set.
    For example, if you want to limit the number of connections to 25, enter max.namedpipe.client.per.session=25. However, there is no upper limit.
    Note: An error message is displayed when the number of actual connections exceed the limit that you have set in max.namedpipe.client.per.session=.
  5. Save the file and restart the Bot Agent service.
    Limit is set for the number of NamedPipe Client connections.