Application Server and Component Installation
Installing the pieces in the right order
Blue Prism is a multi-component product, and the order of installation matters. The database is prepared first, then the application server components are installed and configured to point at that database, and only then are interactive clients installed and connected. Candidates should be able to describe what each component does: the application server hosts the services that coordinate sessions and process execution, the interactive client provides the development and control interface, and additional components handle runtime resources and supporting services.
A recurring exam theme is service account configuration. Services should run under a dedicated domain account, not Local System, so that database authentication and file share access behave predictably across the estate. The account needs log-on-as-service rights and appropriate database permissions. Another theme is installation media and licensing - the licence must be applied and validated before the environment is considered functional.
Traps to watch for: assuming a successful installer run means a working environment (it does not; connection tests and licence checks are separate), forgetting that the client version must match the application server version, and overlooking that Windows firewall rules may block the client-to-server connection even when the service is running.
Rule of thumb: install and verify one tier at a time, confirming database connectivity from the application server before introducing any clients.
Worked example: an installer completes without error, but clients cannot connect. The engineer checks the service is running under the correct account, confirms the firewall allows the client port, and verifies client and server versions match.