Install RPA Windows server
tip
To learn more about deployment, see Deploy RPA. For the general deployment architecture, refer to Installation overview | Deployment diagram.
Prerequisites
Before you start the installation process, mind the following conditions:
- The Master server of your WorkFusion IA Cloud Enterprise is installed.
- On the Master server, the
rpa.ymlfile is filled in correctly. - RPA Windows users are created in advance and logged in at least once.
- The RPA Windows users listed in
rpa.ymlexist on RPA server(s), the passwords are correct, and all users are members of the Remote Desktop Users group. To check this, log in via RDP as a user of each type. - VDI installation is possible on Windows 10.
important
If rpa.yml contains wrong credentials or hostnames, correct them:
On the Master server, open
rpa.ymlfor editing, and specify correct values:./install.sh edit_rpa_config masterPush the provided configuration from
rpa.ymlto Secrets Vault. In the database, initialize the machines table with correct data:./install.sh configure bot-manager -c local
Upload RPA installer
The product installer workfusion-full-package-<version>.tar.gz contains the RPA installer RPAInstaller-<version>.zip file.
To copy the RPA installer from the Master server to all existing RPA servers:
On the Master 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 Master server over HTTP by running the following commands:
$ cd /opt/workfusion/wf_installer $ ./install.sh generate_conf rpa $ python -m http.server 9999note
The 9999 port is used as an example. You can use any free port on the Master server accessible from the RPA servers and stop the HTTP server after copying.
Connect to the RPA server via RDP and download the RPA installer and configuration files from the Master server:
- On the RPA server, launch PowerShell ISE as Administrator.
- Copy the script below and execute it in PowerShell on the RPA servers. 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—the one you're logged in to $download_from = "host-master.example.com:9999" # DNS name of Master server and port from which to download RPAInstaller $rpa_installer = "RPAInstaller-<version>.zip" # RPA Installer file name on the Master server (check it in sources/ directory on Master server) $install_dir = "C:\RPA" # RPA Installation Directory on this server (it will be created if it doesn't exist) $package_dir = "${install_dir}\RPAInstaller" # RPA Installer package Directory on this server # Delete previous version of package directory if exists If (Test-Path $package_dir){ Get-ChildItem -Path $package_dir -Recurse | Remove-Item -force -recurse Remove-Item $package_dir -Force } # 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 see the following files:

On the Master server, press
Ctrl+Cto stop sharing files.
Install RPA server
note
You can install an RPA server on a VDI host managed by the Citrix Virtual App and Desktop environment. In this case, the installation process does not differ from the standard RPA Windows server installation.
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, for example,
<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—the DNS name of the current RPA server.
- In the ZooKeeper field, use the value of the
master_hostnamessetting (seehosts.ymlon the Master server). The default ZooKeeper port is 2181 unless you haven't modified it inports.yml.

- Select the Nginx config file location:
Choose the RPA Windows users on behalf of which the RPA Units will act. If the users exist on the RPA server and credentials are set correctly in
rpa.yml(refer to RPA requirements), the drop-down list contains all the Windows users mentioned in therpa.ymlfile for this RPA server.- VDI instance or Workstation (1 RPA Unit): specify only one RPA Unit.

- Enterprise Server (multiple RPA Units):
To add an RPA Unit, click Add Bot and select an RPA Unit user from the drop-down 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 drop-down 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
tip
The step is optional.
If you filled in rpa.yml correctly during the Master server installation, all the settings from rpa.yml are automatically pushed to Secrets Vault. Remember to fill in rpa.yml during the preparation for the Master server installation.
If for any reason, the configuration from rpa.yml wasn't pushed to Secrets Vault or was pushed with wrong values, you can update it in one of the following ways:
Automatically. Fill in
rpa.ymlcorrectly on the Master 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 a Master user. Click Add and fill in the fields as in the example.

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

- Create similar records for all users on all RPA servers. 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
tip
The step is optional.
You have to verify the Internet Explorer settings only if you use it. Check the settings for each added user. For more details, go to Configuring Internet Explorer for RPA.
Change RPA Units resolution
tip
The step is optional.
By default, the WFRDP Client has a resolution of 1270*700. To change the resolution, refer to Change RPA Unit resolution.
Check RPA installation
To check the status of installed RPA server components:
Reboot your RPA server after the installation is finished.
If you don't have an RDS License for this RPA server and you are using an RDP connection to your RPA server, disconnect RDP to release the connection needed for RPA processes.
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 your RPA Windows server hostname is available, and you can send commands to the RPA Worker.
Run any RPA task and view logs in Kibana.