Upgrade from v9.2.4 to v9.2.6
The guide describes the steps to apply patch_9.2.6 to SPA v9.2.4.
Prerequisites
- You have WorkFusion SPA 9.2.4 installed.
- All actions for applying patch_9.2.6 must be performed as <WF_USER>. The Root user is not required.
Upgrade procedure
Prepare all nodes for patching
On the BI server stop all services. From the <install dir>/10.5/bin directory (for example, C:\WorkFusionAnalyticsServer\10.5\bin), execute the following command:
$ tabadmin stopOn each Linux server, create the <install_dir>/patches/patch_9.2.6 directory, download and extract the patch into it:
$ mkdir -pv <install_dir>/patches/patch_9.2.6 $ cd <install_dir>/patches/patch_9.2.6 $ curl -o 'patch_9.2.6.tar.gz' '<patch download url>' $ tar xzf patch_9.2.6.tar.gzYou will see the following directory structure as a result:
-rwxrwxr-x. 1 wfuser wfuser 5325 Mar 24 14:06 patch_9.2.6.sh -rw-rw-r--. 1 wfuser wfuser 259786116 Apr 1 16:51 patch.tar.gz drwxrwxr-x. 5 wfuser wfuser 44 Mar 24 13:26 sourcesOn the DB server, in the <install_dir>/patches/patch_9.2.6/vars file, 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>'On the DB server, verify the correctness of the specified credentials:
$ source <install_dir>/patches/patch_9.2.6/vars $ <install_dir>/mysql/usr/bin/mysqlcheck -h 127.0.0.1 -P 3306 -u$MYSQL_ADMIN -p$MYSQL_PASS --check-upgrade --all-databasesYou will see a similar output:
mysql.columns_priv OK mysql.db OK ........ (lots of similar output) ..... wfdb.worker_interest OK wfdb.workeractivitylog_test OKOn 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.6
$ ./patch_9.2.6.sh upgrade_db
You will see the following output:
Wed Apr 1 16:55:16 UTC 2020 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Apr 1 16:55:19 UTC 2020 Extracting nginx binary
Wed Apr 1 16:55:22 UTC 2020 Nginx update completed
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
Wed Apr 1 16:56:04 UTC 2020 Upgrading components on DB server
Wed Apr 1 16:56:07 UTC 2020 Extracting mysql components...
Wed Apr 1 16:56:17 UTC 2020 Restoring mysql configuration...
Wed Apr 1 16:56:20 UTC 2020 Adapting mysql configuration to new version...
Wed Apr 1 16:56:23 UTC 2020 Verifying mysql upgrade status
mysql: started
mysqlcheck: [Warning] Using a password on the command line interface can be insecure.
mysql.columns_priv OK
--- similar output ---
wfdb.workeractivitylog_test OK
Wed Apr 1 15:56:40 UTC 2020 Mysql update completed. Check for any errors in output
Wed Apr 1 15:56:41 UTC 2020 DB server upgrade 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 was successful (no errors in 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.6
$ ./patch_9.2.6.sh upgrade_vdsmaster
You will see the following output:
Wed Apr 1 16:55:16 UTC 2020 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Apr 1 16:55:19 UTC 2020 Extracting nginx binary
Wed Apr 1 16:55:22 UTC 2020 Nginx update completed
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
Upgrade VDS Slave server
To upgrade VDS Master, on the vdsmaster server, execute the following command:
$ cd <install_dir>/patches/patch_9.2.6
$ ./patch_9.2.6.sh upgrade_vdsslave
You will see the following output:
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
Upgrade APM server
To upgrade APM, on the APM server, execute the following command:
$ cd <install_dir>/patches/patch_9.2.6
$ ./patch_9.2.6.sh upgrade_apm
You will see the following output:
Wed Apr 1 16:55:16 UTC 2020 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Apr 1 16:55:19 UTC 2020 Extracting nginx binary
Wed Apr 1 16:55:22 UTC 2020 Nginx update completed
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
Upgrade OCR server
To update OCR, on the OCR server, execute the following command:
$ cd <install_dir>/patches/patch_9.2.6
$ ./patch_9.2.6.sh upgrade_ocr
You will see the following output:
Wed Apr 1 16:55:16 UTC 2020 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Apr 1 16:55:19 UTC 2020 Extracting nginx binary
Wed Apr 1 16:55:22 UTC 2020 Nginx update completed
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
Upgrade APP server
To upgrade APP, on the APP server, execute the following command:
$ cd <install_dir>/patches/patch_9.2.6
$ ./patch_9.2.6.sh upgrade_ct
You will see the following output:
Wed Apr 1 16:55:16 UTC 2020 Backing up nginx binaries...
mkdir: created directory ‘backup/nginx_1_12_2’
Wed Apr 1 16:55:19 UTC 2020 Extracting nginx binary
Wed Apr 1 16:55:22 UTC 2020 Nginx update completed
Wed Apr 1 16:55:23 UTC 2020 Backing up java binaries...
mkdir: created directory ‘backup/java_8u144’
Wed Apr 1 16:55:26 UTC 2020 Extracting java binary
Wed Apr 1 16:55:33 UTC 2020 java update completed
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 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
Restart the RPA server.
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 listening to port 443:
$ sudo /usr/sbin/setcap CAP_NET_BIND_SERVICE=+eip <install dir>/nginx/bin/nginx
Upgrade Java on BI server
On the BI server, make a backup of the
INSTALL_DIR\10.5\repository\jre directory.On the BI server, download and extract contents of the jre1.8.0_251.zip archive to
INSTALL_DIR\10.5\repository\jre directory.On the BI server, from the /10.5/bin directory, execute the following command to start services:
$ tabadmin start
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
You can check a business process on the APP server 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