show / hide menu

RPA Genie Architecture

RPA Genie Workflow

RPA Genie Workflow Diagram and Explanation

The architecture of RPA Genie can be categorized into two parts. One is the Server side and the other one is the Client side.

Server side

The Server side consists of a Database server and a Windows server.

Database Server: The RPA Genie database and the AppForms database will reside in the database server. The RPA Genie database is responsible for storing all the metadata related to automation, while the AppForms database contains information pertinent to the Bot Manager.

Windows Server: The RPA Genie service and the Bot Manager will be hosted on the Windows server. The RPA Genie service will establish communication between the bots and the database server. Bot Manager interacts with the RPA Genie database to access automation metadata and communicates with the RPA Genie Service through APIs. Users can access Bot Manager using a browser, similar to how you access any other web application.

Client side

The Client layer consists of RPA Genie client applications used for developing and running applications. RPA Genie Studio must be installed on machines dedicated to creating automation and configurations. All configured automation metadata is stored in the RPA Genie Database via the RPA Genie Service. The number of machines with Studio installed can be increased based on the parallel development needs for various use cases.

Subsequently, the deployed automation can be executed on bot machines as two different types: attended automation and unattended automation. The number of bot machines can be scaled according to specific use cases. These bot machines communicate with the RPA Genie Service in the Server layer through APIs.

[Attended Bot]: Attended Bots are the Bots that are ready and activated by a person whenever they are needed to execute a process. These bots need human supervision. This automation will be running on the same session in which the user is logged in.

[Unattended Bot]: Unattended Bots are the Bots that will operate on a pre-set schedule or as a trigger using logic in the process flow. These bots don’t need to be supervised by humans. This automation will be running under Remote Desktop Protocol sessions (RDP) based on the user that is configured for the bots in the bot manager.

NB: In both the Attended and Unattended Bot, The Bot manager application and Bot manager service are installed on the application server. This server will establish communication with the SQL Server via the default TCP/IP port 1433. The Bot Manager can be accessed using the URL that is configured at the time of installation.

[Example URL given in the images below to access the Bot manager is https://bmt.cunextgen.com].

Attended Bot Dataflow

*1  Bot users: If the system is a Windows desktop, only one user can log in at a time. However, on a Windows server, up to two users can log in concurrently. For terminal servers, Multiple bot sessions can be allowed concurrently. For automation requirements, it’s essential to whitelist specific URLs for downloading Chrome Driver, NuGet packages, and Edge Driver on Bot machines. This ensures seamless integration and access to necessary resources.

*2 SMTP: Depending on the SMTP server configuration, the SMTP port could be set to 25, 465, 587, or 2525. It’s crucial to whitelist at least one of these ports based on the server configuration to ensure proper communication and delivery of emails. This is optional based on process requirements.

*3 Business DB: Business DB access for Bot machine users is optional based on automation requirements. The Business Database serves the specific purpose of maintaining data separately for individual processes. Each automation has the option to utilize its own Business DB, ensuring separate data storage and management.

*4  Admin user: Users such as IT team and process contributors may manually initiate RDP sessions for purposes such as updating products and debugging.


In the attended Bot workflow, the Bots are installed on the user’s desktop, allowing users to initiate attended automation directly through the Co-Pilot from the system tray.

  • The Bot Manager serves as a valuable tool for administrative users to publish the automation that is subsequently accessible to all users for execution. Additionally, it also helps in monitoring and tracing all the automation that has been executed.
  • The Bot Manager service serves as a communicator between each individual bot and the Bot Manager application. This service is responsible for retrieving automation information and recording automation logs, which are then written to the Bot Manager.

SMTP Server

RPA Genie provides a notification alert feature enabling email notifications for various workflow actions. This functionality relies on an SMTP server to send email messages. Access should be granted from the Bot Manager Server to the SMTP server on the configured port (e.g., 25, 587, etc.). To enable bots to send SMTP emails to users based on specific process requirements, access to the SMTP server must be allowed for the designated bot machines.

Web-based Automation & NuGet Packages

For every version of Chrome and Edge, we require the respective WebDriver to be downloaded and utilized. As this is an automated process, we only need to whitelist URLs related to the WebDriver dependencies. In addition to this when utilizing NuGet packages, if a package includes secondary dependencies, whitelisting the secondary source URL enables the Genie bot to autonomously resolve these dependencies.

Chrome driver: https://storage.googleapis.com/chrome-for-testing-public/”   &https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json“

Edge driver: https://msedgedriver.azureedge.net/

NuGet: https://api.nuget.org/v3/index.json

Note: These URL’s has to be Whitelisted in RPA Genie Application level. Failure to whitelist these URLs will necessitate the manual download of all drivers and NuGet dependencies to ensure smooth automation execution.

Unattended Bot Dataflow

*1  Admin user: Users such as IT team and process contributors may manually initiate RDP sessions for purposes such as updating products and debugging.

*2  Bot users: If the system is a Windows desktop, only one user can log in at a time. However, on a Windows server, up to two users can log in concurrently. For terminal servers, Multiple bot sessions can be allowed concurrently. For automation requirements, it’s essential to whitelist specific URLs for downloading Chrome Driver, NuGet packages, and Edge Driver on Bot machines. This ensures seamless integration and access to necessary resources.

*3 Business DB: Business DB access for Bot machine users is optional based on automation requirements. The Business Database serves the specific purpose of maintaining data separately for individual processes. Each automation has the option to utilize its own Business DB, ensuring separate data storage and management.

*4 SMTP: Depending on the SMTP server configuration, the SMTP port could be set to 25, 465, 587, or 2525. It’s crucial to whitelist at least one of these ports based on the server configuration to ensure proper communication and delivery of emails. This is optional based on process requirements.

Bot Machines

In specific environments, there can be numerous bot machines, each with the capability to execute individual automation simultaneously. Additionally, these bot machines can accommodate multiple user instances or user sessions from which the bots can initiate automation. The number of bot machines can be decided as per the requirements.

Bot Manager Server

The unattended bots can be triggered with the help of the Scheduler and Start Job option that is available in the Bot Manager. Once the Job is triggered from any of the above two methods, the request will be sent to the RPA Genie Agent Service with the help of the service URL which is configured at the time of Package installation. [Example URL given the image to access the Bot manager is https://service.cunextgen.com]. Now the connection is established between the RPA Genie service and the RPA Genie Agent Service and the RDP Session with PORT 3389 will be initiated with the requested bot user. Bot admin users can directly RDP to the bot machines whenever required during inactive times/non-productive hours for example, to perform server patching, to do application upgrades, review any issues related to Bots, etc.

Bot manager

This Bot Manager serves as a valuable tool for administrative users to publish the automation that is subsequently accessible to all users for execution. Additionally, it also helps in monitoring and tracing all the automation that has been executed.

The Bot Manager application and Bot Manager service are installed on the Bot Manager server. This server will establish communication with the SQL Server via the default TCP/IP port 1433. The Bot Manager can be accessed using the URL that is configured at the time of installation. [Example URL given in the images below to access the Bot manager is https://bmt.cunextgen.com]