Most customers have chosen to host the RPA Supervisor application with Internet Information Services (IIS) from Microsoft. You may choose your own hosting method, or set up IIS hosting with our guide provided below.
⚠️ Reach out to support at rpasupervisor dot com if you choose your own hosting.
Hosting the application with IIS is only a recommendation, you may host it with your
platform if it supports hosting ASP.NET applications.
Install IIS (Internet Information Services)
On the Windows Server, enable the Web Server (IIS) server role and establish role services.
- Start Server Manager on your Windows Server.
- Use the Add Roles and Features wizard from the Manage menu.
- On the Server Roles step, check the box for Web Server (IIS).
- Enable WebSockets in the Role Services step. To enable WebSockets, expand the following nodes: World Wide Web Services > Application Development Features. Select the WebSocket Protocol feature.
- Follow the wizard and complete the installation. If the IIS installation requires a restart, restart the system.
Install .NET Core Hosting Bundle
.NET Core Runtime & Hosting (minimum version 2.2.5) is required to run RPA Supervisor.
- Suggested version 2.2.7 can be downloaded here.
- Install the Hosting Bundle by running the downloaded application file.
- Restart the system.
- Extract the application folders RPAS.API (version).zip and RPAS.Dashboard (version).zip from RPA Supervisor (Version Number).zip to the wwwroot folder, typically found in C:\inetpub\wwwroot. The result will be:
- C:\inetpub\wwwroot\RPAS.API (version)
- C:\inetpub\wwwroot\RPAS.Dashboard (version)
- Remove version numbers from both the folders, RPAS.API
1.95and RPAS.Dashboard 1.95. The result should be:
- Extract the configuration files from RPA Supervisor config files.zip and add the config file to each of the folders:
- Start the Internet Information Services (IIS) Manager and ensure that the two folders are visible under Sites > Default Web Site.
- Create a new Application Pool. Select Application Pools in the left side-menu, and click Add Application Pool in the Actions menu on the right.
Give the pool a name, and set .NET CLR version to “No Managed Code”.
Leave other options default. Click OK to close the dialog.
- Define specific identity user to run the application pool. Advanced Settings > Process Model set the Identity to the Service User created during the Installation Preparations. Activate Load User Profile by setting the value to True. Click OK and then OK to close the dialogs.
- Right-Click the website folders and select Convert to Application.
- Select the newly created application pool, Enable Preload, and click OK.
- It is required to convert the RPAS.API folder.
We recommend converting the RPAS.Dashboard as well. You may use the same Application Pool for both folders.
- Acquire a web site certificate from your IT-department. Your IT-department will most likely have a wild card certificate that you may use for the RPA Supervisor website. A wild card certificate for customer.com will allow you to set up rpasupervisor.customer.com as your web site hostname.
💡 You may create a self-signed certificate to use temporarily
A self-signed certificate can be acceptable on closed networks such as an Intranet.
- Select the parent site, typically named Default Web Site, and click Bindings… on the side-menu.
- Click Edit on the https binding.
- Set the host name to the chosen host name for the web site.
💡 Make a note of your chosen host name. It will be required in Step 7
- Select a SSL certificate from the dropdown, or by clicking Select to choose from available certificates based on the host name entered.
- Click OK and then Close to close the site binding dialogs.
(Optional) Apply HTTP headers for increased security
To get a full score in security tests you will need to add a few optional headers in your IIS setup.
Requirements before implementing
Strict-Transport-Security: Requires the use of the SSL certificate. A self-hosted certificate will not be usable with this setting.
X-Frame-Options: sameorigin means that the web site possibly wont load from other sources than the originating web site address. This may prevent you from accessing the web site if you we're to access it by embedding into Teams or similar.
Read more about each header
Headers to apply
X-Content-Type-Options: no sniff
How to apply the headers: https://docubrain.com/kb/adding-http-headers-increase-iis-security