10.1.6

Edit

Upgrade from 10.1.6.0 to 10.1.6.0.1

The guide describes how to upgrade from v.10.1.6.0 to the 10.1.6.0.1 version of WorkFusion Intelligent Automation Cloud.

Remember to execute all patch actions as the APPLICATION_USER. No root user is required. This patch also assumes executing database migrations; thus, it requires a valid user with the dba role (mssql_dba_user, as set in config.yml file).

Prerequisites

  • You have WorkFusion Intelligent Automation Cloud 10.1.6.0 up and running.

  • All business processes in Control Tower are stopped.

  • All workers in Marathon are destroyed.

    To destroy workers, go to the Marathon UI, on the top right side next to "worker" group, click More ("..."), and select Destroy item > Destroy Group.

Back up database

As this patch assumes applying database migrations, we recommend backing up the database before applying the patch so that you can restore it later.

Download and extract patch

To download and extract the patch, connect to the APP server via SSH and run the following commands as APPLICATION_USER:

  1. Change directory to PACKAGE_DIR (where the installer was extracted during the initial installation of 10.1.6.0, for example: INSTALL_DIR/wf_installer). Ensure that PACKAGE_DIR is writable for APPLICATION_USER:

    $ cd PACKAGE_DIR
$ sudo chown -R APPLICATION_USER ./

  2. Create the patches directory, if it doesn't exist, and download the patch:

    $ mkdir -pv patches
$ cd patches/
$ curl -o 'patch_10.1.6.0.1.tar.gz' 'patch_url'

    If Internet access is not available, download the patch to PACKAGE_DIR/patches/ directory with any known method.

  3. Extract the patch:

    $ tar xzf patch_10.1.6.0.1.tar.gz

    After the extraction, in the PACKAGE_DIR/patches/, you will find the patch_10.1.6.0.1.sh script and the patch_10.1.6.0.1 directory:

    $ ls -la
drwxr-xr-x.  3 wfuser wfuser   62 Jan 29 14:15 .
drwxr-xr-x. 15 wfuser wfuser 4096 Jan 29 09:47 ..
-rwxrwxr-x.  1 wfuser wfuser 1910 Jan 29 14:10 patch_10.1.6.0.1.sh
drwxr-xr-x.  6 wfuser wfuser  116 Jan 29 10:59 patch_10.1.6.0.1
important

If you patch the system in the Multi-point (Legacy) way, repeat these steps on all Linux servers.

Apply patch

Apply the patch, depending on your installation approach:

For single-point setup

To apply the patch:

  1. Run the commands from the APP server (6-server topology) or first INT server (8-server and HA topology):

    $ export ANSIBLE_PRIVATE_KEY_FILE="</path/to/ssh_key>"   # Path to SSH key for connection to all Linux servers as <linux_installation_user>
$ export ANSIBLE_VAULT_PASS="<your-ansible-vault-pass>"  # Optional. If you run this command you'll not be prompted to enter config decryption password while applying patch.

$ cd patches/
$ ./patch_10.1.6.0.1.sh apply int         # update INT server to 10.1.6.0.1 state
$ ./patch_10.1.6.0.1.sh apply bep-master  # update BEP Master server to 10.1.6.0.1 state
$ ./patch_10.1.6.0.1.sh apply app         # update Application server(s) to 10.1.6.0.1 state

The patching is completed. It may require about five minutes for Control Tower to start. If you see error 503 in the browser right after the patching, wait a bit.

For legacy setup (multi-point)

To apply the patch:

  1. Run the commands from the APP server (6-server topology) or on the Linux servers in the following order: INT → BEP Master → APP (8-server and HA topology):

    $ cd PACKAGE_DIR/patches/
$ export ANSIBLE_VAULT_PASS="<your-ansible-vault-pass>"  # Optional. If you run this command, you'll not be prompted to enter the password for configuration decryption

$ ./patch_10.1.6.0.1.sh apply int --limit <current-hostname>        # Run on INT server(s) to update it to 10.1.6.0.1 state
$ ./patch_10.1.6.0.1.sh apply bep-master --limit <current-hostname> # Run on BEP Master server(s) to update it to 10.1.6.0.1 state
$ ./patch_10.1.6.0.1.sh apply app  --limit <current-hostname> # Run on Application server(s) update them to 10.1.6.0.1 state

# <current-hostname> is the hostname of the server on which you're executing the command

The patching is completed. It may require about five minutes for Control Tower to start. If you see error 503 in the browser right after the patching, wait a bit.

Verify installation

Once the update is completed, check WorkFusion Platform with Business Process (BP) and Manual Task. The OCR must be activated.

To verify the update, run the following command from the APP server:

$ ./install.sh check app -e test_rpa=true -e test_ie=true -e test_desktop=true -e test_ocr=true -e test_ml=true

Rollback changes

You can revert the changes in the same manner as you have installed the update, but the option rollback is used instead of apply.

To roll the changes back:

  1. Run the following commands as APPLICATION_USER according to your way of installation:

    • For the single-point setup, run the commands from the APP server (6-server topology) or first INT server (8-server and HA topology):

      $ cd PATCH_DIR
$ ./patch_10.1.6.0.1.sh rollback int         # Will bring desired server to 10.1.6.0 state
$ ./patch_10.1.6.0.1.sh rollback bep-master  # Will bring desired server to 10.1.6.0 state.
$ ./patch_10.1.6.0.1.sh rollback app         # Will bring desired server to 10.1.6.0 state.

    • For the multi-point setup, run the each command on the respective server (for example, ./patch_10.1.6.0.1.sh rollback int on INT, ./patch_10.1.6.0.1.sh rollback bep-master on BEP Master, and so on):

      $ cd <patch-dir>
$ ./patch_10.1.6.0.1.sh rollback int --limit <current-hostname>        # Will bring desired server to 10.1.6.0 state
$ ./patch_10.1.6.0.1.sh rollback bep-master --limit <current-hostname> # Will bring desired server to 10.1.6.0 state.
$ ./patch_10.1.6.0.1.sh rollback app --limit <current-hostname>        # Will bring desired server to 10.1.6.0 state.

# <current-hostname> is the hostname of the server on which you're executing the command

    At that time, all services are stopped, as we still need to revert database changes. To do that:

  2. Restore the database from the backup.

  3. Execute the following command on all servers to start services:

    wfmanager start all

  4. Run the following commands on all APP servers to disable maintenance mode for failover scripts:

    cd <install dir>/failover/bin/
maintenance-workfusion.sh disable
maintenance-workspace.sh disable
maintenance-bot-manager.sh disable
maintenance-sqc.sh disable

The rollback is completed. It may require about five minutes for Control Tower to start. If you see error 503 in the browser right after the patching, wait a bit.

← Set up Disaster RecoveryNext →