Install RPA Windows server
RPA deployment diagram

note
To learn more about deployment, refer to Deploy RPA. For the general deployment architecture, refer to Installation overview | Deployment diagram.
Prerequisites
- The APP server of your WorkFusion Intelligent Automation Cloud Enterprise is installed.
- The
rpa.ymlfile is filled in correctly on the APP server. - RPA Windows users are created in advance and logged in at least once.
- RPA Windows users listed in
rpa.ymlexist on RPA server(s), the passwords are correct, and the users are members of required groups (the Master user is a member of Administrators, while RPA Unit users are members of Remote Desktop Users). Log in via RDP as a user of each type to check.
important
If rpa.yml contains wrong credentials or hostnames, correct them:
On the APP server, open
rpa.ymlfor editing, and specify correct values:./install.sh edit_rpa_config appPush the provided configuration from
rpa.ymlto Secrets Vault and initialize the machines table in the database with correct data:./install.sh configure bot-manager
Upload RPA installer to RPA server(s)
The product installer workfusion-full-package-<version>.tar.gz file contains the RPA installer RPAInstaller-<version>.zip file.
To copy the RPA installer from the APP server to all existing RPA servers:
On the APP server, replace
/opt/workfusion/wf_installerwith correctPACKAGE_DIRfor your environment.Generate configuration files for the RPA installer, and make the installer and configs downloadable from the APP server over HTTP by running the following commands:
$ cd /opt/workfusion/wf_installer $ ./install.sh generate_conf rpa $ python -m SimpleHTTPServer 9999note
The 9999 port is used as an example. You can use any free port on the APP server accessible from the RPA servers. You can stop the HTTP server after copying.
Connect to the RPA server via RDP and download the RPA installer and configs from the APP server.
- On the RPA server, launch PowerShell ISE as Administrator.
- Copy the script below and execute it in PowerShell on the RPA server(s). Before the execution, remember to modify the first four lines according to your configuration:
current_host,download_from,rpa_installer, andinstall_dir.
$current_host = "host-rpa.example.com" # DNS name of this RPA server (which you're logged in to) $download_from = "host-app.example.com:9999" # DNS name of APP server and port from which to download RPAInstaller $rpa_installer = "RPAInstaller-<version>.zip" # RPA Installer file name on APP server (check it in the sources/ directory on APP server) $install_dir = "C:\RPA" # RPA Installation Directory on this server (it will be created if it doesn't exist) # Creating install_dir New-Item -ItemType directory -Path ${install_dir} -Force # Downloading RPA installer and configs $wc = New-Object net.webclient $wc.Downloadfile("http://${download_from}/sources/${rpa_installer}", "${install_dir}\RPAInstaller.zip") $wc.Downloadfile("http://${download_from}/win_confs/rpa_configs/${current_host}/rpa_installer_conf.zip", "${install_dir}\rpa_installer_conf.zip") # Unpacking RPA installer and configs Add-Type -assembly "system.io.compression.filesystem" [System.IO.Compression.ZipFile]::ExtractToDirectory("${install_dir}\RPAInstaller.zip", "${install_dir}\RPAInstaller") [System.IO.Compression.ZipFile]::ExtractToDirectory("${install_dir}\rpa_installer_conf.zip", "${install_dir}\RPAInstaller")The script runs for about 10 seconds. After execution, you will see the following files.

On the APP server, press
Ctrl+Cto stop sharing files.
Install RPA server
To install the RPA components:
Right-click
RPAInstaller.exeand select Run as administrator. The RPA Setup Wizard appears.Accept the License Agreement and click Next.

Specify the RPA installation directory. Use the same value as in the script earlier. In this example, it is
C:/RPA.
Select the RPA Server type.

Specify the path to the folder with certificates:
<rpa_install_dir>/RPAInstaller/certificates.
Set up the network configuration:
- Select the Nginx config file location:
<rpa_install_dir>/RPAInstaller/nginx.conf. - Specify My Machine DNS name, which is the DNS name of the current RPA server.
- In the ZooKeeper field, use the value of the
int_hostnamessetting (seehosts.ymlon the APP server). The default ZooKeeper port is 2181 unless you haven't modified it inports.yml.

- Select the Nginx config file location:
Choose RPA Windows users, on behalf of which RPA Units act. If the users exist on this RPA server and credentials are set correctly in
rpa.yml(refer to RPA requirements), the dropdown list contains all the Windows users mentioned inrpa.ymlfor this RPA server.- Development (1 RPA Unit): specify only one RPA Unit.

- Production (multiple RPA Units):
To add an RPA Unit, click Add Bot and select an RPA Unit user from the dropdown list. If the needed user is missing in the list, you can create a Windows user or log in as the Active Directory user during this step and reopen the dropdown list afterward.
To delete an RPA Unit, click the Close button next to it.

Click Install and wait for the installation process to complete.
Click Finish and reboot the server.
At this point, the RPA installation is complete. Repeat the above steps on each RPA server in your environment, if you have several RPA servers.
Configure RPA users in Secrets Vault manually (optional)
tip
If you followed the installation guide carefully, you don't need to perform this step.
If you have filled in rpa.yml correctly during the APP server installation, all the settings from rpa.yml are pushed to Secrets Vault automatically. Remember to fill in rpa.yml during the preparation for the APP server installation.
If for any reason the configuration from rpa.yml has not been pushed to Secrets Vault or pushed with wrong values, you can update it using the following ways:
Automatically. Fill in
rpa.ymlcorrectly on the APP server and run the command:./install.sh configure bot-managerManually. In case of the VDI Server installation, configure only the Master user.
- Log in to Control Tower, and on the main page, go to System Settings > Secrets Vault.
- Add a record for the Master user. Click Add and fill in the fields as on the example.

- Add a record for the RPA Unit user(s). Click Add and fill in the fields as on the example.

- Create similar records for all users on all RPA servers (if you have several of them). On each RPA server, only one Master user, but multiple RPA Unit users can exist. The following example shows a case when one RPA server is used, with one Master user and one RPA Unit user.

Verify Internet Explorer settings (optional)
Verify the Internet Explorer settings only if you use this browser. Check the settings for each added user. For more details, go to Configure Internet Explorer for RPA.
Check RPA installation
To check the status of installed RPA server components:
Reboot your RPA server after the installation is finished (if you haven't done it yet).
If you don't have an RDS License for this RPA server and use an RDP connection to your RPA server, disconnect RDP to release the connection needed for RPA processes.
Make sure that RPA Units are available and WebDrivers exist on the connected RPA Units. Open the following link as any user on the RPA machine: http://localhost:1500{unit_id}/grid/console. On evoking the command, view the list of available RPA Units in your browser.
To check the RPA Worker, open the following link in your browser as any user on the RPA machine: http://localhost:1520{unit_id}/health. You will get the following response:
[ { "status": "UP", "details": { "rabbit": { "status": "UP", "details": { "version": "3.7.14" } }, "diskSpace": { "status": "UP", "details": { "total": 53317988352, "free": 25653489664, "threshold": 10485760 } }, "refreshScope": { "status": "UP" }, "zookeeper": { "status": "UP", "details": { "connectionString": "hostname.workfusion.com:port", "state": "STARTED" } } } } ]Open Bot Manager and make sure that your RPA Windows server hostname is available, and you can send commands to RPA Worker.
Run any RPA task and view logs in Kibana.