Blue Prism Installation Engineer key terms

The Microsoft SQL Server database that stores process definitions, queues, schedules, audit logs, and configuration for a Blue Prism environment. Every runtime resource and interactive client connects to it.

The text value, stored in configuration, that tells a Blue Prism component which database server, instance, and database to connect to, including authentication method and optional encryption settings.

The character-set and sort rules configured on the SQL Server instance and database. Blue Prism requires a case-insensitive collation, and a mismatch can cause installation or runtime failures.

The vendor-supplied SQL script that builds the Blue Prism schema, tables, stored procedures, and default data in an empty database during a fresh installation.

The controlled process of applying newer database scripts and component installers so an existing Blue Prism environment matches a later product version while preserving data.

A documented set of steps, backups, and decision points that let a team restore the previous working state if an upgrade or migration fails partway through.

Moving Blue Prism configuration, processes, and data between environments or servers, for example from development to production or from an old host to new infrastructure.

Bringing a packaged Blue Prism release file into a target environment, which creates or updates processes, objects, and related components after validation checks.

The formal process of recording, approving, scheduling, and reviewing infrastructure or configuration changes so that production impact is understood and auditable.

The Blue Prism desktop application used by developers and administrators to build processes, configure settings, and monitor the environment. It connects directly to the database.

A machine licensed and configured to execute Blue Prism processes and objects, typically running unattended under a dedicated service account on a server.

A Blue Prism component that brokers connections between clients or runtime resources and the database, centralizing configuration and reducing direct database exposure.

Distributing connection or work requests across multiple application servers or runtime resources so no single host is overwhelmed and availability improves.

Designing the platform so that failure of a single server, database node, or network path does not stop automation from running, usually through redundancy and failover.

The plans, backups, and alternate infrastructure that allow Blue Prism services and data to be restored at an acceptable time after a major outage or site loss.

The defined frequency, retention, and storage locations for database and configuration backups, plus the testing regime that proves restores actually work.

A documented list of operating system versions, SQL Server requirements, .NET components, permissions, and ports that must be satisfied before installing Blue Prism components.

A dedicated, non-interactive Windows account under which Blue Prism services and runtime resources run, granted only the database and file permissions they need.

Granting each account, role, or user only the permissions required for its function, minimizing the blast radius of mistakes or compromised credentials.

Assigning permissions in Blue Prism through roles that bundle rights, so users inherit capabilities from their role rather than from individual per-user settings.

Creating, modifying, and disabling Blue Prism user accounts, including linking them to directory identities and assigning the correct roles and permissions.

An authentication arrangement where users log in once with their corporate identity and Blue Prism accepts that authenticated session instead of a separate password.

Configuring Blue Prism to authenticate users against directory accounts and groups, so access follows existing joiner, mover, and leaver processes.

A SQL Server connection mode where the operating system identity of the calling process is used to authenticate, avoiding stored database passwords.

A network access rule permitting traffic on specific ports between Blue Prism clients, application servers, runtime resources, and the database server.

The delay in data traveling between Blue Prism components and the database; high latency degrades interactive client responsiveness and can cause timeouts.

A logical grouping of runtime resources that work can be assigned to, enabling capacity management and predictable scheduling across machines.

The Blue Prism feature that starts sessions and queues work at defined times or intervals, relying on correctly configured resources and calendars.

The record of each process or object run, including start and end times, status, resource used, and error details, used for monitoring and troubleshooting.

The tamper-evident record of configuration and security-relevant changes in Blue Prism, such as user edits, permission changes, and release imports.

A structured post-installation check confirming connectivity, licensing, permissions, scheduling, and a test process run before the environment is declared live.

A short, high-value test executed after installation or upgrade to prove the core path works, such as logging in and running a simple process end to end.

Applying and verifying the Blue Prism licence so the correct number of interactive clients and runtime resources are permitted to operate.

The routine of tracking, testing, and applying operating system, database, and Blue Prism updates on a planned cadence to reduce security and stability risk.

A local file on a Blue Prism component that holds connection details and component settings, which must be consistent across machines in the same environment.

A numbered network endpoint a Blue Prism component listens on or connects to; correct port configuration is essential for client, server, and database communication.

The diagnostic output written by Blue Prism components and Windows event logs, examined to identify the cause of connection, permission, or runtime failures.

The protected repository where Blue Prism keeps credentials used by processes, separated from process logic and protected by access controls and encryption.