Standalone deployment

Run the appropriate installer depending on whether you want to use the 32-bit or 64-bit installer.

• 32-bit Installer: BluePrismx.x.nn_x86.msi
• 64-bit Installer: BluePrismx.x.nn_x64.msi

Installers are available from the Blue Prism Portal.

Click Get started to follow the steps in the installation wizard and complete the installation. If required, you can change the language in the wizard by clicking Choose language at the top of the first screen.

Advanced install options

The following additional components are available during a Blue Prism installation if the Advanced install option is enabled on the Install location screen. Components selected by default that are not required must be deselected before proceeding with the installation.

When Blue Prism is launched for the first time it is necessary to define a connection to the SQL Server instance where the database is, or will be, hosted.

1. On the Blue Prism login screen, click Configure connection.

   

2. In the Connection Configuration dialog, specify the connection details as outlined in the image below:

   

   *If the Connection type selected includes Windows Authentication, the context of the user currently logged into the device will be used to authenticate against the SQL Server. Where possible Windows Authentication (rather than SQL Authentication) should be used.

   • SQL Server (SQL Authentication) – Connection Name (must be unique), Database Server, Database Name, User ID
   • SQL Server (Windows Authentication) – Connection Name (must be unique), Database Server, Database Name
   • Availability Group (SQL Authentication) – Connection Name (must be unique), Database Server, Database Name, User ID
   • Availability Group (Windows Authentication) – Connection Name (must be unique), Database Server, Database Name
   • SQL Server (Custom Connection String) – Connection String (the complete SQL connection string must be used)

   ** Can be left blank. Populate if there is a requirement to add custom SQL Connection Parameters such as: encrypt=true; trustservercertificate=true.

   See SQL Server Connection Properties information provided by Microsoft for a list of available values.

   If connecting to Microsoft SQL Azure, the database must be pre-existing, and the connection details provided within the Azure database configuration area should be used. Example settings (ADO.NET) are provided below:

   Connection Type	SQL Server (SQL Authentication)
   Database Server:	e12n3456.database.windows.net,1433
   Database Name:	BluePrism
   User ID:	authUser@e12n3456
   Password:	*********

3. Click Test Connection to establish if a connection can be established with the SQL Server.

   As the database does not yet exist, one of the following messages will display:

   Expected responses

   Database 'Blue Prism' does not exist.	This does not appear to be a valid Blue Prism database.
   Indicates that a successful connection was established with the server, but that the database does not yet exist.	Indicates that a successful connection was established with the server, but that it cannot be verified as a Blue Prism database. This would typically be the case where the database has been manually created but has not had the Blue Prism schema applied.
   Click OK to clear the message and then click Create Database.
   Proceed to the next step for further instructions.

   Alternative responses

   Database Valid	Unable to determine whether database exists – A network-related or instance-specific error occurred whilst establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)
   Indicates that a successful connection was established with the server and the database. Actions to Create the database can be bypassed.	Indicates that an error occurred establishing a connection with the SQL Server. Check that the details for the SQL Server instance are correct, and refer to Troubleshooting an installation.

There are two stages involved in the creation and preparation of a database for use with Blue Prism.

• Create a SQL Server database – This can either be achieved manually or by using the Create Database action.
• Apply Blue Prism schema – The database schema is applied to the database.
• The Create Database action will automatically apply the schema to a database that it creates; or to a specifiable pre-existing blank database.
• Alternatively, the schema can be applied by manually using the CreateScript.sql against a pre-existing database. The CreateScript.sql can be obtained via request from Blue Prism Customer Support or generated using the Blue Prism client – Click Generate Script at the bottom of the Create a new database or Upgrade the database screens.

All of the above is completed in a single step when using the Create Database functionality.

1. To create a database, click Create Database in the Connection Configuration dialog.

   

2. In the Create a new database dialog, enable the Drop any existing database with the specified name option if you want to purge and recreate a database that already exists.

3. Click OK to complete the database configuration.

   

Support for contained databases

Blue Prism supports the use of contained databases, hosted on Microsoft SQL Server. To use a contained database, it is necessary to manually create the database and apply the Blue Prism CreateScript.sql.

For more information, see Contained databases.

It is recommended that the installation is manually verified by carrying out some simple tasks within the system and confirming that they execute successfully.

For step-by-step instructions, see Verify an Installation.