ATA02 Designing a Blue Prism (Version 6.0) Environment Questions and Answers

Blue Prism Interactive Clients

Blue Prism Application Server(s)

Other Blue Prism Runtime Resources

Third party systems accessing Blue Prism web services

Blue Prism Credential Manager

Policies applied by Active Directory such as multi-factor authentication and password complexity are applied to Blue Prism

It makes it possible to add custom security roles in Blue Prism

Users are assigned security roles based on their group membership in Active Directory

Data encryption between Blue Prism devices is provided by default

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

Existing Data Center and Virtualization strategies

Support of the components

Desktop and Application Virtualization Strategies

Availability

All of the above

Whether windows authentication or SQL Native authentication will be used for the Database Connection.

Backup and log truncation should be reviewed according to business criticality

Database and Log backup.

Ensuring that the application servers have full sysadmin rights to the database.

Proximity of the database server to the Blue Prism Application server.

Selection of the database platform, between SQL server and Oracle.

Ensuring that the database server can be accessed from all Runtime Resources within the network.

There may be additional implications to the overall complexity of the architecture, due to the additional components involved in the virtualization technology

It will only ever be possible to use Surface Automation to Automate these applications

The Login Agent application must be available prior to User Login

The mapping between virtualized applications and users is often 1:1. This needs to be considered when designing the credential management approach for the Runtime Resources

Customizations to the application may be lost after the user is logged out or the system is rebooted, unless additional mechanisms are used to preserve them

Surface Automation will always need to be used in these scenarios

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

Interactive Clients should never be virtualized

For Process Development - it helps to ensure the Interactive Client has the same configuration as the virtualized Runtime Resources

Where the developers are geographically separate to the Blue Prism environment

To ensure a high-latency connection between the Interactive Client and the Application Server

Whenever runtime resources are virtualized

There is no difference, the terms are synonymous

A Process represents a definition of the automation steps and logic; Runtime Resources execute the steps defined within a Process

A Process represents a definition of the automation steps and logic; and a Runtime Resource is an executable containing all of the logic within a single process.

A Runtime Resource represents a collection of Processes which is used as part of Release Management

The level of session logging that is configured for each stage of each Business Object and Process

Session logging archiving policy

The number of Blue Prism users

The number of Runtime Resources that are registered

Whether Active Queues are used