RPA Genie Architecture

RPA Genie Logical Architecture

RPA Genie Platform has three layers:

Client

This layer consists of RPA Genie Studio and RPA Genie Agent. Studio helps the user to design the process automation and through Agent the user is able to run the automation that was created using the Studio.

Server

This layer consists of the BOT Manager and RPA Genie Service. BOT Manager is a User Interface, and the RPA Genie Service is the backend service which connects the bots. BOT Manager is built on top of a no-code platform known as “AppForms” which is another web-based application developed by ClaySys.

Data

RPA Genie uses the relational database SQL to store all the metadata of the processes that were created. It also stores the configuration related to all the bots and its processes.

RPA Genie Server Architecture

RPA Genie can be setup using Virtual Machines/Physical Machines for each of the BOTs.

Independent BOT Machines Architecture

Terminal Server Architecture

RPA Genie Data workflow

Ideally, we would need six machines to setup up the environment for Dev, QA and Production. The below diagram represents the environment setup for RPA Genie Robotic Automation.

Additional dev machines can be spawned based on the developers working on the automation and additional QA or Prod machines can be spawned based on the number of processes that need to be run in parallel.

Bot Manager

RPA Genie Bot Manager is a web application that connects multiple bots and can manage each of the bots connected to it. Using this component, you can connect multiple bots to the bot manager and add, schedule., monitor the automations and also control automated bots and process. A separate instance of Bot Manager is needed for Dev and QA. A single instance can be used for UAT and production.

Dev Environment

This is where the development takes place. RPA Genie Studio will be installed in this environment which the developers can then use to configure the automation. There can be multiple dev machines based on the number of developers working on the process automations. Once the development is finished, it will be published to the Bot Manager. The Dev Agent and Studio will be connected to the DEV Bot Manager instance.

QA Environment

This is where the testing takes place and RPA Genie Agent will be installed in this environment. Once the development is done, it will be published to the Bot Manager which will then be deployed to the QA bots. QA bots will also be connected to the QA Bot Manager instance.

Production Environment

This machine, like QA will have RPA Genie Agent installed. Once the testing has been completed with the QA bots, it can be pushed to Production. Production environment can be spawned to multiple bot machines based on the number of processes that need to be run in parallel. All these Bot instances will be connected to the PROD\UAT Bot Manager instance. The BOT machines can be either separate VMs/Physical Machines, or it can also be a single Terminal Server which can have multiple instances of BOT users. Please refer RPA Genie Server Architecture for more information.

UAT/Stage Environment (Optional)

This environment will mimic the Production environment. This is optional and is only needed if you want the bots to be tested with the production application before it is released to production.