Blue Prism ATA02 - Designing a Blue Prism (Version 6.0) Environment

Login Agent must be used to initiate the login to the device vs the Citrix Client.

Only version 5 of Blue Prism is supported with XenDesktop.

Login Agent is only supported from version 7.6 of XenDesktop, due torestrictions on 3rd party credential provider support prior to this.

XenDesktop is not a supported platform for the Runtime Resource.

Surface Automation will need to be used for all automations.

An underlying disk subsystem which hosts many virtual devices can be a performance bottleneck.

Often shared hardware is over-allocated resulting in less than expected available capacity (e.g. 2 vCPUs may equate to 0.1 physical cores)

It is important to validate the actual performance of the Runtime Resources when operating on shared hardware

The performance of the Runtime Resource can impact processing throughput

All of the above

To assure performance

To maintain the latest copy of live process automations and configuration

To maintain an accurate record of the processing history

To maintain a copy of the base VM image that is used to generate Runtime Resources

To avoid losing the configuration of applications on the Runtime Resources

Provide a high performance MPLS connection between sites

Provide virtualized Interactive Clients within the same network as the Blue Prism environment

Provide fully replicated Blue Prism environments in each geographic region where users are based

Nominate a user in the central location who will receive releases from each remote user and apply them to the system

The Blue Prism interactive client can be used on its own to monitor the environment in its entirety

Monitoring of Blue Prism is not necessary

External Monitoring tools should be used to monitor system performance

Event logs should be monitored for application errors

Process execution related errors may need to be dealt with by a business operations team

Process related errors are automatically sent to the event log

By default the connection is native TCP and not encrypted

The runtime resource can be configured to use certificate-based encryption for all inbound communication

The login agent will automatically use a certificate if the runtime resource is configured to use one

The connection will be established via .NET remoting and will be encrypted as long as the “Use Secure Connections” flag is set

A central setting within Blue Prism can be used to prevent all associated Runtime Resources from accepting any instructional communications which are not encrypted.

Network latency is circumvented

There are more options for interacting directly with the applications which accelerates time required to build automations

Automations built using direct object level instrumentation are likely to be more robust

It is then possible to record an automation directly using the spying tools

This enables the use of Surface Automation, which is faster to develop

Type 1 hypervisors, such as VMWare Vsphere and Citrix XenServer should be used for production grade deployments of Blue Prism.

Type 2 hypervisors, such as Oracle Virtualbox and Vmware Workstation may be used for production grade deployments of Blue Prism.

All desktop virtualization strategies are suitable for deployment of Runtime Resources.

Consideration should be given to the system resource requirements of the automated applications, on top of the Blue Prism minimum specifications.

The Blue Prism minimum specifications should be sufficient for all use cases.

Runtime Resource

Interactive Client (for Monitoring and Control)

Interactive Client (for development)

Application Server

All of the above