9.4

Edit

Post-installation

Backup procedure

Set up the cold-backup procedure that should be aligned with your company backup policy using the Cold backup and restore guide.

Post-installation health checks

Once the installation is completed, you should run healthchecks of WorkFusion Platform with Business Process (BP) and Manual Task.

  • To check WorkFusion S3, OCR and RPA, run the environment healthcheck.
  • To check ML (VDS) follow the Cognitive process runbook. Use a Classification model to perform a quick check.

ML, RPA and OCR check without manual steps can be launched from console on APP server:

cd <PACKAGE_DIR>
./install.sh check app -e test_rpa="true" -e test_ocr="true" -e test_ml="true"

Post-installation steps

OCR license activation

Activate the OCR license on OCR Server as described in the OCR license topic.

RPA Server (optional)

Configure RPA Manager on APP Server as described in Update from non-SSL to SSL.

VDS Server (optional)

Update Models

On this page and others, you may find references to "VDS" acronym (Virtual Data Scientist). VDS is the former name for the AutoML component (Automatic Machine Learning). "VDS" is equivalent to "AutoML" in all cases. Use these steps in case you need to update current models or upload new ones. These commands need to be executed on AutoML Master server.

cd <INSTALL_DIR>

## Will update the models, merging the already uploaded with the new ones
./vds_models_uploader.sh <PATH_TO_MODELS_PACKAGE>

## Use -o flag to overwrite everything with the new models instead of merging
./vds_models_uploader.sh -o <PATH_TO_MODELS_PACKAGE>

Install ML SDK

The ML-SDK package is a part of the AutoML server installation process. These steps can be used in case vds-ml-sdk should be uploaded to the standalone nexus-server.

Predefined variables:

  • nexus_host: IP adress of standalone nexus-server
  • local_artifact_path: /workfusion-nexus-artifacts, directories inside workfusion-nexus-artifacts must be named the same as repositories in nexus
  • username: username to access a standalone Nexus server
  • password: password to access a standalone Nexus server

This command should be executed on DB server:

/usr/bin/env python <INSTALL_DIR>/tools/nexus_tool/nexus_tool.py update --nexus_host=http://127.0.0.1:{{ nexus_port }} --local_artifact_path={{ workfusion_nexus_artifact_dir }} --username={{ workfusion_nexus_admin }} --password={{ workfusion_nexus_admin_pass }}

End-user machines

Import SSL Certificates to the end-user's server, java truststore and browser. The browser cannot work properly with web pages over HTTPS without importing certificates to the system.

Secure Vault password

After the installation has been completed, it is highly recommended to delete sensitive data from the host, e.g. the unencrypted secrets.yml file from the installation directory.

After the installation, you can find encrypted configuration files at the <INSTALL_DIR>/distr/latest directory:

  • Logs
  • Config difference files
  • Encrypted secrets_overrides.yml file
  • Encrypted config_overrides.yml file

The encryption is performed using Ansible Vault, and the decryption password is stored in the <PACKAGE_DIR>/VAULT_PASSWORD.DELETE_ME file.

This password has to be stored in trusted secure location.

After that, you can remove the VAULT_PASSWORD.DELETE_ME file from the host.

Keep the distr directory as it is required for future on-demand passwords update and general upgrade procedures.

← PreviousNext →