Upgrade from v9.2.10 to v9.2.11

The guide describes the steps to apply patch_9.2.10 to SPA v9.2.9.

Prerequisites

You have WorkFusion SPA 9.2.10 installed.
All actions for applying patch_9.2.11 must be performed as <WF_USER>. The Root user is not required.
You have set the value of INSTALL_DIR in the /patches/patch_9.2.11/vars file according to the relevant path.

Upgrade procedure

Prepare all nodes for patching

On each Linux server, create the <install_dir>/patches/patch_9.2.11 directory, download, and extract the patch into it:

$ mkdir -pv <install_dir>/patches/patch_9.2.11
$ cd <install_dir>/patches/patch_9.2.11
$ curl -o 'patch_9.2.11.tar.gz' '<patch download url>'
$ tar xzf patch_9.2.11.tar.gz

You will see the following directory structure:

-rwxrwxr-x.  1 wfuser wfuser      18453 Feb  9 07:16 patch_9.2.11.sh
-rw-rw-r--.  1 wfuser wfuser 3502219630 Feb  9 08:49 patch_9.2.11.tar.gz
drwxrwxr-x. 16 wfuser wfuser        226 Feb  7 10:12 sources
-rw-rw-r--.  1 wfuser wfuser        171 Feb  9 07:01 vars

On the DB server, in file <install_dir>/patches/patch_9.2.11/vars, fill in the credentials for the MySQL and Nexus servers and port for Nexus server:

export MYSQL_ADMIN='<put your mysql admin username here>'
export MYSQL_PASS='<put your mysql admin password here>'
export NEXUS_PORT='put your nexus port here'
export WORKFUSION_NEXUS_DEPLOYMENT_USER='put your nexus deployment password here'
export WORKFUSION_NEXUS_DEPLOYMENT_PASS='put your nexus deployment password here'

On the DB server, verify the correctness of the specified credentials:

$ source <install_dir>/patches/patch_9.2.11/vars
$ <install_dir>/mysql/usr/bin/mysqlcheck -h 127.0.0.1 -P 3306 -u$MYSQL_ADMIN -p$MYSQL_PASS --check-upgrade --all-databases

You will see a similar output:

mysql.columns_priv                                 OK
mysql.db                                           OK

........ (lots of similar output) .....

wfdb.worker_interest                               OK
wfdb.workeractivitylog_test                        OK

On each Linux server, stop all WorkFusion services:
```
$ wfmanager stop all
```

Upgrade DB server

To upgrade DB on the DB server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_db

You will see the following output:

Wed Feb  9 09:08:25 UTC 2022 Upgrading components on DB server
Wed Feb  9 09:08:25 UTC 2022 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Feb  9 09:08:28 UTC 2022 Extracting nginx binary
Wed Feb  9 09:08:31 UTC 2022 Nginx update completed
Wed Feb  9 09:08:32 UTC 2022 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’ 

--- similar output ---

Wed Oct 28 10:05:46 UTC 2020 Mysql update completed. Check for any errors in output
Wed Oct 28 10:05:47 UTC 2020 DB server patching completed

Inspect the output of the MySQL status for any errors or not-ok statuses. It must return the status 'OK' for each test, as in the example earlier. If the check is successful, execute the following commands to update the database schema:

$ cd <install_dir>
$ mysql/usr/bin/mysql_upgrade -h 127.0.0.1 -P 3306 -u$MYSQL_ADMIN -p$MYSQL_PASS

In case the execution is successful and has no errors in the output, restart the MySQL process:

$ wfmanager restart mysql

Upgrade VDS Master server

warning

DB server should be upgraded before VDS master server.

To upgrade VDS Master, on the vdsmaster server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_vdsmaster

You will see the following output:

Wed Feb  9 09:26:36 UTC 2022 Upgrading components on VDS master 
Wed Feb  9 09:26:36 UTC 2022 Backing up java binaries...
mkdir: created directory ‘backup/java_8u311’
Wed Feb  9 09:26:36 UTC 2022 Extracting java binary
Wed Feb  9 09:26:39 UTC 2022 Java update completed
Wed Feb  9 09:26:39 UTC 2022 Backing up rabbitmq binaries...

--- similar output ---

 Wed Feb  9 09:27:39 UTC 2022 VDS master upgrade completed"

Upgrade VDS Slave server

To upgrade VDS Master, on the vdsmaster server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_vdsslave

You will see the following output:

Mon Jun  7 13:48:14 UTC 2021 Upgrading components on VDS slave
Mon Jun  7 13:48:14 UTC 2021 Backing up java binaries...

--- similar output ---

Mon Jun  7 13:48:37 UTC 2021 VDS slave upgrade completed

Upgrade APM server

To upgrade APM, on the APM server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_apm

You will see the following output:

Mon Jun  7 13:50:41 UTC 2021 Upgrading components on APM server 

--- similar output ---

Mon Jun  7 13:48:37 UTC 2021 APM sever upgrade completed

Upgrade OCR server

To update OCR, on the OCR server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_ocr

You will see the following output:

Mon Jun  7 13:48:14 UTC 2021 Upgrading components on OCR server

--- similar output ---

Mon Jun  7 13:48:37 UTC 2021 OCR server upgrade completed

Upgrade APP server

To upgrade APP, on the APP server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.11
$ ./patch_9.2.11.sh upgrade_ct

You will see the following output:

Mon Jun  7 13:48:14 UTC 2021 Upgrading components on APP server 

--- similar output ---

Mon Jun  7 13:48:37 UTC 2021 APP server upgrade completed

note

Patch script creates configuration file rpa-manager/grid-router/logback.xml with default settings. If you have custom settings in configuration file rpa-manager/grid-router/log4j.properties, you should manually convert this config file to rpa-manager/grid-router/logback.xml. You can find original settings in backup file backup/rpa_manager_9.2.2.7/log4j.properties and use online converter

https://logback.qos.ch/translator/.

Upgrade RPA server

Back up the current installation by renaming the RPA directory (for example, from C:\RPA to C:\RPA_old).
Uninstall RPA using the respective item from Programs and Features in Control Panel. Reboot the server when requested.

caution

Do not delete the C:\RPA directory itself. It still contains the required configuration files.
Install a new version of RPA, as described in RPA Windows Server installation.
From the backup directory, restore the following files to their corresponding paths:
- File nginx.conf from the C:\RPA_old\nginx\conf directory
- All files from the C:\RPA_old\rpa-grid directory, except rpa-desktop <version>.jar and directories 'dependency', 'drivers', 'extensions'
- All files from the C:\RPA_old\wfagent\conf directory
- All files from the C:\RPA_old\wfagent\bin directory
- File CA.crt from C:\RPA_old\filebeat\ssl\ to C:\RPA\filebeat\ssl\CA.crt
- All files from C:\RPA_old\nginx\ssl\ to C:\RPA\nginx\ssl\
- Update the Chrome driver in C:\RPA\rpa-grid\drivers\windows\x32 to the same version as the Chrome browser on RPA server.
Restart the RPA server.

Start WorkFusion services on all Linux servers

On all Linux servers, DB > VDSmaster > APP > OCR > APM > VDSslave, run the following command as <WF_USER>.

$ wfmanager start all

Post-upgrade steps

After the upgrade, on the APP server, check a Business Process as <WF_USER>:

$ cd /tmp/workfusion-full-package-9.2.2.0-35/
$ ./install.sh check_raw app -e @/tmp/config_overrides.yml -e test_rpa=true -e test_ocr=true -e test_ml=true

WorkFusion Documentation

9.2

General services

APP

DB

OCR

VDS

OOTB configuration

Infrastructure scaling

Run preinstall manually

Using TLS certificates

Elastic Monitoring

Prerequisites

Upgrade procedure

Prepare all nodes for patching

Upgrade DB server

Upgrade VDS Master server

warning

Upgrade VDS Slave server

Upgrade APM server

Upgrade OCR server

Upgrade APP server

note

Upgrade RPA server

caution

Start WorkFusion services on all Linux servers

Post-upgrade steps