Support Import

BotStack

Multi-SoloBot hosting on one Server

ProcessRobot now supports the ability for multiple Robots to execute Processes on a single Windows Server.

In environments where a single Robot is installed, the flow of execution is the following:

On machine A, Solobot A logs in and executes Processes using User’s A credentials:

SoloBot A > Machine A > User A (Autologin)

In a Multi-SoloBot environment, it is possible to assign multiple SoloBots to a single Windows Server machine using different User credentials. Each User will launch an RDP session on the Server, as per the following scheme:

  • SoloBot A > Machine A > Remote Desktop session from User A

  • SoloBot B > Machine A > Remote Desktop session from User B

  • SoloBot C > Machine A > Remote Desktop session from User C

…and so on.

multi-solobot1.png

In this regard, ProcessRobot will allow multiple SoloBots on the same Server to be connected under different Users; in the same way as when one initiates a remote desktop session on a server.

The instances will be spawned from a single installation per server. A single installation of the SoloBot software is required on the workstation. The multiple Robots and Users will then be declared in the Control Desk.

This feature will utilize the machine in the best manner, in order to run multiple Processes on multiple SoloBots, taking maximum advantage of the available hardware resources.

Overview

multi-solobot2.png

A single Machine Agent on the Windows Server SoloBot machine will be able to establish multiple RDP connections to itself, one connection per registered SoloBot. Login in each of these connections will be achieved by using the credentials of the Active Directory User account assigned to each SoloBot.

Process Flow Overview

multi-solobot3.png

The Process Flow of initiating the execution of a Process on a SoloBot may follow one of two possible paths, depending on whether the Active Directory User is already logged in.

If the User is logged in:

The ProcessRobot Server sends a signal to the Machine Agent, which in turn sends a signal to the User Agent, which runs the Process.

If the User is NOT logged in:

The ProcessRobot Server sends a signal to the Machine Agent, which initiates a RDP session (to machine it resides), logs in with the User's credentials, starts the User Agent, which then runs the Process.

Note:

High density scenarios are supported only for different User instances.

In cases where Users are logged in, ProcessRobot supports the use of SideBots as well