Install Blue Prism Hub with Decision

You can now run the Hub installer, see Install Blue Prism Hub. On the Blue Prism Decision Setup (Optional) screen, enter the URL of where the Decision Model Service is running followed by the port number. The URL must match the FQDN that was specified in the certificate and point to the Model Service. The port number must match that was specified when the Model Service was set to run.

The URL should be in the format https://<FQDN>:<port number>.
For example, https://decision.blueprism.com:50051, or http://decision.local:50051.

If you have already installed Hub 4.7 without Decision, see Troubleshooting the installation for information on updating your installation.

Mandatory configuration

Once Hub is installed, you also need to carry out the following configuration on the server.

Decision DNS resolution

Blue Prism applications communicate with each other using their respective machine names. It is therefore necessary to ensure that these can be resolved successfully, and that firewall rules allow appropriate communication on the defined ports.

It may be necessary to set up DNS servers, Windows DNS search suffixes or local hosts file to support this.

Enterprise organizations often use formal DNS management utilities, however for tactical or experimental configurations it may be appropriate to use local host files to manipulate DNS.

  1. On the Hub web server, open the hosts file using a text editor. The hosts file is typically located in C:\Windows\System32\drivers\etc.

    You must be logged in with administrator level access to change this file.

  2. Enter the IP address and host name for Decision at the end of the list, for example:

  3. Save and exit the text editor.

IIS ownership over the Decision certificates

On the Hub web server, you also need to give access for IIS users to the certificates created for Decision. To do this:

  1. Open Manage Computer Certificates, and locate the required certificate.
  2. Right-click the certificate, select All Tasks, and then Manage Private Keys....
  3. Add IIS_IUSRS with the Read permission.
  4. Click Apply.
  5. Repeat for all the appropriate certificates. For a list, see Generate an SSL Certificate.