Update from 10.1.0 to 10.1.1

The guide describes upgrade from non-HA 10.1.0 to non-HA 10.1.1 version of WorkFusion Intelligent Automation Cloud.

Prerequisites

You have WorkFusion Intelligent Automation Cloud 10.1.0 up and running.
No Business Processes are running.

Download and extract patch

Connect to the INT server via SSH and run the following commands as <linux_installation_user>:

Change the directory to <package_dir> (where the installer was extracted during the initial installation of 10.1.0, for example: INSTALL_DIR/wf_installer). Ensure that PACKAGE_DIR is writable for <linux_installation_user>:
```
$ cd PACKAGE_DIR
$ sudo chown -R <linux_installation_user> ./
```

Create the patches directory and download the patch to it:

If the Internet access is available on the server:

$ mkdir patches
$ cd patches/
$ curl -o 'patch_10.1.0-10.1.1_non_ha.tar.gz' 'https://spa-releases.s3.amazonaws.com:443/10.1/10.1.1/patch_10.1.0-10.1.1_non_ha.tar.gz?AWSAccessKeyId=AKIAIYJMMPKAN2MQSJWA&Expires=1601397147&Signature=QTP7AXyyKUhk9ku2FhUJ%2BhEArh4%3D'

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

Extract the patch:

$ tar xzf patch_10.1.0-10.1.1_non_ha.tar.gz

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

$ ls -la
drwxr-xr-x. 12 ec2-user ec2-user       4096 Sep 27 17:20 .
drwxr-xr-x. 29 wfuser   wfuser         4096 Sep 27 15:27 ..
drwxrwxr-x.  6 ec2-user ec2-user        134 Sep 27 17:17 patch_10.1.1
-rwxrwxr-x.  1 ec2-user ec2-user       1246 Sep 27 16:00 patch_10.1.1.sh

Ensure that Nexus and MS SQL users passwords are valid in config.yml.

In most cases you don't need to change anything in config.yml. You may proceed further with the patch and skip this step. If you encounter issues (for example, error message with invalid credentials): edit config.yml, update it with valid passwords, and rerun patch. Patch is idempotent - so it is safe to rerun it.

For example, it might happen so that after the initial installation of 10.1.0, Nexus or MSSQL passwords were changed manually in the environment for some purpose. In this case you need to actualize them in config.yml, because the patch will use them during the execution (for updating DB schemas and Nexus artifacts). To edit config.yml use the following command:
```
./install.sh edit_config int
# you'll be prompted for decryption password
```
```
nexus_admin_pass
mssql_dba_pass
mssql_ct_pass
mssql_ws_pass
mssql_sqc_pass
mssql_rpa_pass
mssql_pm_pass
mssql_dm_pass
mssql_ocr_pass
mssql_automl_mms_pass
```

note

If you patch the system in the Legacy way, repeat these steps for all servers.

Apply patch

Apply the patch, depending on your installation approach.

For single-point setup

Prepare the environment variables. On the INT server, run the following commands as <linux_installation_user>:

$ 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_REMOTE_USER="<linux_installation_user>" # <linux_installation_user> provided in config.yml
$ export ANSIBLE_VAULT_PASS="<ansible_vault_password>"   # Password for decryption of config.yml. If you don't set this variable, you'll be prompted for password during setup.

run the following commands to apply the patch.

Note: before running the ./patch_10.1.1.sh apply bi command, ensure that Tableau server is activated and operational. Ensure that BI dashboards are displayed in Control Tower UI.

./patch_10.1.1.sh apply int        # update INT server to 10.1.1 state
./patch_10.1.1.sh apply bep-master # update BEP Master server to 10.1.1 state
./patch_10.1.1.sh apply bep-agent  # update BEP Agent server(s) to 10.1.1 state
./patch_10.1.1.sh apply app        # update APP server to 10.1.1 state
./patch_10.1.1.sh apply ocr        # update OCR server to 10.1.1 state
./patch_10.1.1.sh apply bi         # update BI server (Analytics Dashboards) to 10.1.1 state

Apply the patch for the RPA server. Before that, uninstall current RPA and perform clean installation of new RPA. Note that you must navigate to PACKAGE_DIR and use the install.sh script to update RPA to 10.1.1.

$ cd PACKAGE_DIR
$ ./install.sh uninstall rpa                         # Uninstall current 10.1.0 RPA
$ ./install.sh install rpa -e @manifest_10.1.1.yml   # Install new 10.1.1 RPA (it is included into patch)

Cleanup RabbitMQ queues to ensure that old workers do not spawn queues:

Stop all services on all servers. Go to PACKAGE_DIR and run the following commands as <linux_installation_user>:

$ cd PACKAGE_DIR
$ ./install.sh stop_services full -e skip_bi=true    # Stop all services on all servers before cleanup of RabbitMQ queues

Switch to the runtime user (WFUSER), and then start rabbitmq and cleanup rabbitmq queues:

$ sudo su - wfuser
$ wfmanager start rabbitmq
$ rabbitmqctl list_queues --vhost bep | awk '{ print $1 }' | xargs -L1 rabbitmqctl delete_queue --vhost bep

Switch back to <linux_installation_user>, and start all services:

$ exit   # switching back to <linux_installation_user>
$ cd PACKAGE_DIR
$ ./install.sh start_services full -e skip_bi=true    # Start all services on all servers

The patching procedure is completed. It may require Control Tower about 5 minutes to start. If you see the 503 error in your browser right now, just wait a bit.

For legacy setup (multi-point)

Apply the patch on the Linux servers. Run the following commands on each Linux server in the following order: INT → BEP Master → BEP Agent(s) → APP → OCR.

$ export ANSIBLE_VAULT_PASS="<ansible_vault_password>"  # Run on each Linux server to disable password prompt (for convenience)

./patch_10.1.1.sh apply int        # Run on INT server to update it to 10.1.1 state
./patch_10.1.1.sh apply bep-master # Run on BEP Master server to update it to 10.1.1 state
./patch_10.1.1.sh apply bep-agent  # Run on BEP Agent server(s) update them to 10.1.1 state
./patch_10.1.1.sh apply app        # Run on APP server to update it to 10.1.1 state
./patch_10.1.1.sh apply ocr        # Run on OCR server to update it to 10.1.1 state

Update the RPA server:
1. Login to the RPA server, go to Control Panel → Programs and Features, and uninstall RPA.
2. Backup current <rpa_install_dir> (for example, C:/RPA/) and remove it.
3. Download the new RPA installer. It's included into the patch and is located on the INT server in PACKAGE_DIR/sources/RPAInstaller-10.1.0.3.zip.
4. Install new RPAInstaller-10.1.0.3.zip following the guide Install RPA Windows Server.
Update BI (Analytics server).

Before updating Analytics Dashboards, ensure that Tableau is activated and operational. Ensure that dashboards are displayed in Control Tower UI. Then login to BI server, and run in powershell as administrator:
```
cd <bi_dir>\packages\bin.20183.19.0714.2346

.\tsm login -u .\<win_user> -p <win_pass>

.\tsm status
Status: RUNNING
```
Update of the BI server includes only update of Analytics Workbooks. New Workbooks package is included into the patch.
1. Login to the BI server and download the new Workbooks package from PACKAGE_DIR/sources/WorkFusionAnalyticsWorkbooks-10.1.1.0.zip on the INT server.
2. Deploy new Workbooks, as described in BI Windows Server Installation

Cleanup the RabbitMQ queues to ensure that old workers do not spawn queues:

$ wfmanager stop all        # Run on each linux server

$ wfmanager start rabbitmq  # Run on INT server
$ rabbitmqctl list_queues --vhost bep | awk '{ print $1 }' | xargs -L1 rabbitmqctl delete_queue --vhost bep   # Run on INT server

$ wfmanager start all      # Run on each linux server
Restart RPA server OR perform sign-off of BotMaster and BotUnit(s) users (these actions are equivalent).

Rollback

Rollback is performed in the same manner as the apply operation, but option rollback is used instead of apply.

$ cd <patch-dir>
$ ./patch_10.1.1.sh rollback <server-role>   # Will bring desired server to 10.1.0 state.

# Available options for <server-role>: int, bep-master, bep-agent, app, ocr, bi.

# To roll-back RPA server in single-point mode:
$ ./install.sh uninstall rpa -e @manifest_10.1.1.yml   # uninstalls 10.1.1 RPA
$ ./install.sh install rpa                             # installs 10.1.0 RPA

# To roll-back RPA server in legacy mode perform uninstall of 10.1.1 RPA and install of 10.1.0 RPA manually.

Check the update

Once the update is completed, check WorkFusion Platform with Business Process (BP) and Manual Task. The OCR must be activated. For more information, see Post-installation steps.

WorkFusion Documentation

10.1.2

Prepare for installation

High availability setup

Standard setup

High availability setup

Standard setup

Install OCR Windows server

Logs management

Security settings in Control Tower

Prerequisites

Download and extract patch

note

Apply patch

For single-point setup

For legacy setup (multi-point)

Rollback

Check the update