9.2

Edit

Upgrade from v9.2.6 to v9.2.7

The guide describes the steps to apply patch_9.2.7 to SPA v9.2.4.

Prerequisites

  • You have WorkFusion SPA 9.2.6 installed.
  • All actions for applying patch_9.2.7 must be performed as <WF_USER>. The Root user is not required.

Upgrade procedure

Prepare all nodes for patching

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

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

    You will see the following directory structure:

    -rwxr-xr-x. 1 wfuser wfuser     10209 Oct 26 06:40 patch_9.2.7.sh
-rw-rw-r--. 1 wfuser wfuser 409085192 Oct 28 09:53 patch_9.2.7.tar.gz
drwxr-xr-x. 7 wfuser wfuser       111 Oct 28 09:53 sources
-rw-r--r--. 1 wfuser wfuser        43 Feb 21  2020 vars

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

    export MYSQL_ADMIN='<put your mysql admin username here>'
export MYSQL_PASS='<put your mysql admin password here>'

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

    $ source <install_dir>/patches/patch_9.2.7/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

  4. 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.7
$ ./patch_9.2.7.sh upgrade_db

You will see the following output:

Wed Oct 28 09:57:05 UTC 2020 Updating DB server to version: 9.2.7
Wed Oct 28 09:57:05 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 09:57:08 UTC 2020 Extracting java binary
Wed Oct 28 09:57:14 UTC 2020 java update completed
Wed Oct 28 10:04:32 UTC 2020 Updating PostgreSQL server to version: 9.5.23
Wed Oct 28 10:04:35 UTC 2020 Backing up PostgreSQL binaries...
mkdir: created directory ‘backup/postgres_9_5_20’
Wed Oct 28 10:04:39 UTC 2020 Extracting PostgreSQL binaries...
Wed Oct 28 10:04:43 UTC 2020 Extracting PostgreSQL additional components...
Wed Oct 28 10:04:46 UTC 2020 PostgreSQL update completed
Wed Oct 28 10:04:46 UTC 2020 Updating MongoDB server to version: 3.6.20
Wed Oct 28 10:04:49 UTC 2020 Backing up MongoDB binaries...
mkdir: created directory ‘backup/mongodb_3_6_15’
mkdir: created directory ‘backup/mongodb_3_6_15/bin’

--- similar output ---

wfdb.workeractivitylog_test                        OK
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

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

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

You will see the following output:

Wed Oct 28 10:11:00 UTC 2020 Upgrading components on VDS master 
Wed Oct 28 10:11:00 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 10:11:03 UTC 2020 Extracting java binary
Wed Oct 28 10:11:10 UTC 2020 java update completed
Wed Oct 28 10:11:11 UTC 2020 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.7
$ ./patch_9.2.7.sh upgrade_vdsslave

You will see the following output:

Wed Oct 28 10:11:38 UTC 2020 Upgrading components on VDS slave 
Wed Oct 28 10:11:38 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 10:11:41 UTC 2020 Extracting java binary
Wed Oct 28 10:11:47 UTC 2020 java update completed
Wed Oct 28 10:11:48 UTC 2020 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.7
$ ./patch_9.2.7.sh upgrade_apm

You will see the following output:

Wed Oct 28 10:13:43 UTC 2020 Upgrading components on APM server
Wed Oct 28 10:13:43 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 10:13:46 UTC 2020 Extracting java binary
Wed Oct 28 10:13:52 UTC 2020 java update completed
Wed Oct 28 10:13:53 UTC 2020 Updating MongoDB server to version: 3.6.20
Wed Oct 28 10:13:56 UTC 2020 Backing up MongoDB binaries...
--- similar output ---
Wed Oct 28 10:14:13 UTC 2020 Enabling back MongoDB user authentication
mongodb_apm: stopped
Wed Oct 28 10:14:16 UTC 2020 MongoDB update completed
Wed Oct 28 10:14:16 UTC 2020 APM server upgrade completed

Upgrade OCR server

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

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

You will see the following output:

Wed Oct 28 10:15:18 UTC 2020 Upgrading components on OCR server
Wed Oct 28 10:15:18 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 10:15:21 UTC 2020 Extracting java binary
Wed Oct 28 10:15:28 UTC 2020 java update completed
Wed Oct 28 10:15:29 UTC 2020 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.7
$ ./patch_9.2.7.sh upgrade_ct

You will see the following output:

Wed Oct 28 10:17:21 UTC 2020 Upgrading components on APP server
Wed Oct 28 10:17:21 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u251’
Wed Oct 28 10:17:24 UTC 2020 Extracting java binary
Wed Oct 28 10:17:30 UTC 2020 java update completed
Wed Oct 28 10:17:31 UTC 2020 Backup current RPA manager artifact (rpa_manager.war)
mkdir: created directory ‘backup/9.2.6’
mkdir: created directory ‘backup/9.2.6/rpa_manager’
Wed Oct 28 10:17:34 UTC 2020 Updating RPA manager artifact...
Wed Oct 28 10:17:37 UTC 2020 RPA manager update completed
Wed Oct 28 10:17:38 UTC 2020 APP server upgrade completed

Upgrade RPA server

  1. Back up the current installation by renaming the RPA directory (for example, from C:\RPA to C:\RPA_old).

  2. 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 required configuration files.

  3. Install a new version of RPA, as described in 9.2.x RPA Windows Server installation.

  4. 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

  5. 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
← PreviousNext →