Blue Prism architecture overview

There are two main deployment architecture options:

• Standard Blue Prism Enterprise – This can be installed and used independently of other components.
• Standard Blue Prism Enterprise, plus Hub Control Room – This requires the Hub platform, Authentication Server, and the Blue Prism API, which establishes a connection between the Hub Control Room and Blue Prism.

Each implementation of a Blue Prism environment consists of a database along with any of the composite components, each of which provide functionality based on the requirements of the business.

System architecture changes in Blue Prism Enterprise version 7

The following system architecture components were introduced for Blue Prism version 7:

• Controlling digital workers at scale – With Application Server Controlled Resources (ASCR), interactive clients communicate with available runtime resources via the application server, meaning that individual connections don’t need to be made.

• Native messaging host for browser extensions – A native messaging host application is used to communicate with each of the browser extensions (Chrome, Edge, and Firefox).

• Authentication Server (optional) – A centralized way of providing common authentication for users across Blue Prism Enterprise, the Blue Prism API, and Hub.

• Browser-based Control Room (optional) – Provides dashboards and data views that allow users to view and manage Blue Prism activity for all their environments.

• Blue Prism API (optional) – Provides a common interface for components such as the Hub Control Room to connect with the Blue Prism database.