Skip to main content

Pega Robot Runtime architecture overview

Architecture overview

The Robotic Automation Architecture is made up of multiple supporting software components that work together to support the deployment, assignment, and management and execution of your robotic automation. The system is divided into client-side components that are used to execute robotic automation and server-side components that are used to manage robotic automation.

The following image shows the robotic architecture overview for version 19.1. Click the + icons to understand more about the components.
 

Architecture: Runtime Start Process Flow

The Loader authenticates the Runtime system and requests the package from the Package Downloader. Package Downloader requests package assignment from Robot Manager and then the package binaries from the Package Server. The package binaries and package manifests are stored on a local drive. The Loader inspects the package manifest and, if required, the Loader requests the runtime version from the Updater Service. The Updater Service then downloads the required Runtime version binaries from the Synchronization Server. Once that is taken care the Loader then launches the Robot Runtime.


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

50% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice