Upgrade from v9.2.13 to v9.2.14

The guide describes the steps to apply the 9.2.14 patch to SPA v9.2.13.

Prerequisites

To apply the patch, meet the following prerequisites:

You have WorkFusion SPA 9.2.13 installed.
Perform all actions for applying the 9.2.14 patch as <WF_USER>.
You have set the values of all variables in the /patches/patch_9.2.14/vars file according to the relevant path.

Upgrade procedure

Prepare servers for patching

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

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

You will see the following directory structure:

-rwxrwxr-x.  1 wfuser wfuser      18453 Jan  4 07:16 patch_9.2.14.sh
-rw-rw-r--.  1 wfuser wfuser  204328474 Jan  4 08:49 patch_9.2.14.tar.gz
drwxrwxr-x. 16 wfuser wfuser        226 Jan  4 10:12 sources
-rw-rw-r--.  1 wfuser wfuser        171 Jan  4 07:01 vars

On the DB server, in the <install_dir>/patches/patch_9.2.14/vars file, fill in the credentials for the MySQL server:

export INSTALL_DIR='put install_dir path'
export MYSQL_ADMIN='put mysql admin user'
export MYSQL_PASS='put mysql admin password'

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

$ source <install_dir>/patches/patch_9.2.14/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 the database, on the DB server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.14
$ source vars
$ ./patch_9.2.14.sh upgrade_db

You will see a similar output:

Wed Jan  4 13:55:07 UTC 2023 Updating components on DB server
Wed Jan  4 13:55:07 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:55:07 UTC 2023 Extracting java binary
Wed Jan  4 13:55:10 UTC 2023 Java update completed
Wed Jan  4 13:55:10 UTC 2023 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1.22.0’
Wed Jan  4 13:55:13 UTC 2023 Extracting nginx binary
Wed Jan  4 13:55:16 UTC 2023 Nginx update completed
Wed Jan  4 13:55:17 UTC 2023 Extracting mysql components...
Wed Jan  4 13:55:25 UTC 2023 Restoring mysql configuration...
Wed Jan  4 13:55:25 UTC 2023 Verifying mysql upgrade status
mysql: started
Wait for mysql is available OK

        --- similar output ---
mysql: stopped
Wed Jan  4 13:55:41 UTC 2023 Mysql update completed. Check for any errors in output
Wed Jan  4 13:55:41 UTC 2023 DB server upgrade completed

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

$ wfmanager start mysql 
$ # wait till mysql has started
$ cd <install_dir>
$ mysql/usr/bin/mysql_upgrade -h 127.0.0.1 -P 3306 -u$MYSQL_ADMIN -p$MYSQL_PASS

Upgrade VDS Master server

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

$ cd <install_dir>/patches/patch_9.2.14
$ source vars
$ ./patch_9.2.14.sh upgrade_vdsmaster

You will see a similar output:

Wed Jan  4 13:56:05 UTC 2023 Upgrading components on VDS master 
Wed Jan  4 13:56:05 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:56:05 UTC 2023 Extracting java binary
Wed Jan  4 13:56:09 UTC 2023 Java update completed
Wed Jan  4 13:56:09 UTC 2023 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1.22.0’
Wed Jan  4 13:56:12 UTC 2023 Extracting nginx binary
Wed Jan  4 13:56:15 UTC 2023 Nginx update completed
Wed Jan  4 13:56:16 UTC 2023 VDS master upgrade completed

Upgrade VDS Slave server

To upgrade the VDS slave components, on the vdsslave server, execute the following command:

$ cd <install_dir>/patches/patch_9.2.14
$ source vars
$ ./patch_9.2.14.sh upgrade_vdsslave

You will see a similar output:

Wed Jan  4 13:56:05 UTC 2021 Upgrading components on VDS slave
Wed Jan  4 13:56:05 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:56:05 UTC 2023 Extracting java binary
Wed Jan  4 13:56:09 UTC 2023 Java update completed
Wed Jan  4 13:56:09 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.14
$ source vars
$ ./patch_9.2.14.sh upgrade_apm

You will see a similar output:

Wed Jan  4 13:56:05 UTC 2023 Upgrading components on APM server
Wed Jan  4 13:56:05 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:56:05 UTC 2023 Extracting java binary
Wed Jan  4 13:56:09 UTC 2023 Java update completed
Wed Jan  4 13:56:09 UTC 2023 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1.22.0’
Wed Jan  4 13:56:12 UTC 2023 Extracting nginx binary
Wed Jan  4 13:56:15 UTC 2023 Nginx update completed
Wed Jan  4 13:56:16 UTC 2023 APM server upgrade completed

Upgrade OCR server

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

$ cd <install_dir>/patches/patch_9.2.14
$ source vars
$ ./patch_9.2.14.sh upgrade_ocr

You will see a similar output:

Wed Jan  4 13:56:05 UTC 2023 Upgrading components on the OCR server
Wed Jan  4 13:56:05 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:56:05 UTC 2023 Extracting java binary
Wed Jan  4 13:56:09 UTC 2023 Java update completed
Wed Jan  4 13:56:09 UTC 2023 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1.22.0’
Wed Jan  4 13:56:12 UTC 2023 Extracting nginx binary
Wed Jan  4 13:56:15 UTC 2023 Nginx update completed
Wed Jan  4 13:56:16 UTC 2023 OCR server upgrade completed

Upgrade APP server

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

$ cd <install_dir>/patches/patch_9.2.14
$ source vars
$ ./patch_9.2.14.sh upgrade_ct

You will see a similar output:

Wed Jan  4 13:56:05 UTC 2023 Upgrading components on APP server
Wed Jan  4 13:56:05 UTC 2023 Backing up java binaries...
mkdir: created directory ‘backup/java_8u331’
Wed Jan  4 13:56:05 UTC 2023 Extracting java binary
Wed Jan  4 13:56:09 UTC 2023 Java update completed
Wed Jan  4 13:56:09 UTC 2023 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1.22.0’
Wed Jan  4 13:56:12 UTC 2023 Extracting nginx binary
Wed Jan  4 13:56:15 UTC 2023 Nginx update completed
Wed Jan  4 13:56:16 UTC 2023 APP server upgrade completed

Prepare Nginx on all Linux servers

On all Linux servers, except VDSslave, run the following command as a user with root permissions to allow Nginx to listen to port 443:

$ sudo /usr/sbin/setcap CAP_NET_BIND_SERVICE=+eip <install dir>/nginx/bin/nginx

Start WorkFusion services

On all Linux servers, in the following order: 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 servers for patching

Upgrade DB server

Upgrade VDS Master server

Upgrade VDS Slave server

Upgrade APM server

Upgrade OCR server

Upgrade APP server

Prepare Nginx on all Linux servers

Start WorkFusion services

Post-upgrade steps