Blue Prism Installation Engineer flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Standalone vs multi-server install

Standalone places application server, database, and client on one host. Multi-server separates the application server tier from the database tier for production scale and resilience.

Runtime resource account rights

The Windows account running a runtime resource needs log on as a batch job, log on as a service, and local administrator on its host during installation.

Required network ports

Clients reach application servers over the configured listening port, typically TCP 443. Application servers reach SQL Server over TCP 1433 unless a named instance uses another port.

Environment license binding

A Blue Prism license is issued per environment and bound to that environment's database. The license must be applied before users can log in and run processes.

Clock synchronization requirement

All Blue Prism hosts must share one time source and time zone. Clock skew between hosts causes authentication failures and inconsistent audit timestamps.

Database collation requirement

Create the Blue Prism database with a case-insensitive collation such as SQL_Latin1_General_CP1_CI_AS. A wrong collation causes script and query failures during setup.

Database account permissions

The creating account needs dbcreator or sysadmin on the instance. The runtime service account needs db_owner on the Blue Prism database only.

Recovery model choice

Set production databases to the Full recovery model and schedule transaction log backups. Simple recovery prevents point-in-time restore after data loss.

Integrated security connection string

Windows authentication uses Server=<host>\<instance>;Database=<name>;Integrated Security=SSPI. SQL authentication instead supplies an explicit user name and password.

Schema version match

The schema version recorded in the Blue Prism database must equal the installed Blue Prism release. A mismatch blocks client and server startup.

TCP/IP enablement

SQL Server must have the TCP/IP protocol enabled in Configuration Manager. Named instances also need SQL Browser running or an explicit port in the connection string.

Blue Prism Server service

The Blue Prism Server Windows service hosts the application server tier. It must run under a dedicated account, not LocalSystem, when the database is remote.

Installation order

Install the database first, then the Blue Prism server, then interactive clients, then runtime resources. Reversing the order leaves components unable to connect.

Resource registration step

Register each runtime resource in the client under System, then install the Runtime Resource service on the host and point it at the application server.

Client connection model

Interactive clients connect to the application server by name and port. Clients never connect directly to the SQL Server database.

Installation verification checks

Confirm the Blue Prism Server service is running, a client login succeeds, and the registered resource shows Connected in the System tab.

Firewall port alignment

Each configured application server listening port must have a matching inbound firewall rule. A port and rule mismatch is a frequent installation failure.

Native vs Active Directory auth

Native authentication uses Blue Prism-stored credentials. Active Directory authentication uses Windows single sign-on and maps group membership to Blue Prism roles.

Role-based permissions

Roles such as System Administrator, Developer, and Process Owner define what users can access. Users inherit permissions from their assigned roles.

Default admin account handling

The built-in admin account exists for initial setup only. Create named accounts, then disable or rotate the default admin credentials immediately after installation.

Encryption key backup

Encryption keys protect stored credentials. Back them up with the database, because a restore without the keys leaves credentials permanently unreadable.

Least privilege for resources

Runtime resource accounts should hold only permissions needed to run assigned processes. They should not be granted System Administrator rights.

Audit log retention

Blue Prism records logins and configuration changes in the database audit log. Retain it according to organizational policy for investigation and compliance.

Database connection failure triage

When the server service fails to start, check the connection string, TCP/IP enablement, and the runtime account's db_owner grant on the database.

Client connection failure triage

When a client cannot connect, verify the application server service state, the configured port, and firewall rules before investigating the database.

Disconnected resource causes

A disconnected resource usually means the runtime resource service is stopped, its account cannot log on interactively, or the registered name differs from the host name.

Version mismatch error

Client, application server, and database schema must all run the same Blue Prism release. Any mismatch produces connection or startup errors.

Event Viewer diagnostics

Blue Prism Server and Runtime Resource services write startup and connection failures to the Windows Application log. Check it first for service-level errors.

Upgrade sequence

Back up the database and encryption keys, upgrade the schema, then upgrade application servers, then clients and runtime resources, in that order.

No skipping major versions

In-place upgrades must pass through each supported intermediate release. Jumping directly across multiple major versions is not supported.

Release package migration

Move changes between environments by exporting and importing release packages. Copying databases breaks license binding and audit integrity.

Post-upgrade validation

After upgrading, re-verify the license, repeat the validation checklist, and confirm resources reconnect and scheduled processes execute successfully.

Resource decommissioning steps

Before shutting down a host, remove its resource registration and revoke its service account. This prevents orphaned resource entries and stale credentials.