9.3

Edit

Preparation steps

Prerequisites

The steps are valid only for Linux Servers: DB, APP, APM, OCR (Linux), AutoML (Cluster).

  • Linux servers are up and running, and all system requirements are met as described in System Requirements.

  • SSH access is allowed to the servers with root privileges. If created manually, a non-privileged user () must have the same name, UID, and GIDDNS names for all servers (Linux and Windows) are configured according to DNS Names Configuration.

  • Application Ports are open between servers.

  • Installation packages are uploaded to servers/opt/workfusion.

  • The default WorkFusion installation directory: change it to your own if necessary.

  • /opt/workfusion/wf_installer is the directory where the installation package is extracted.

Package extraction

Perform the steps below on all Linux servers.

  1. Log into the target server, for instance, using Linux Terminal or Windows PuTTY:

    Example: Linux terminal

    ssh -i /path/to/private-key.pem user@hostname.example.com
sudo su - root

  2. Create a directory for the WorkFusion installation package or installer in the file system. Grant read access for the directory to all users:

    mkdir -p /opt/workfusion/wf_installer
chmod 0755 /opt/workfusion/wf_installer

  3. Extract the installation package:

    tar -xzvf /opt/workfusion/workfusion-full-package-<version>.tar.gz --strip 1 -C /opt/workfusion/wf_installer

Initial configuration

Perform the steps below on the DB server.

  1. Log into the DB Server via SSH.

  2. Edit the configuration files (config.yml and secrets.yml) using a text editor (vi is used in the example below):

    cd /opt/workfusion/wf_installer
vi config.yml
vi secrets.yml

You can refer to the Installation package and config files section for more details on each configuration option.

Prepare TLS certificates

OPTION 1: trusted certificates

  1. Put the following certificates into the <PACKAGE_DIR>/certificates/ directory. Use the file names provided in secrets.yml:

    • Root CA certificate to sign your Trusted Server Certificates.
    • Trusted Server Certificates and their corresponding key files. Certificate files should contain the full bundled chain: End Certificate, Intermediate cert(s) if exist, and Root CA cert.

  2. Generate Vault certificates (for internal application needs):

    cd /opt/workfusion/wf_installer
./generate-certificates.sh cert-vault

OPTION 2: Self-Signed certificates

If you don't have trusted certificates, you can generate Self-Signed certificates. This will populate the <PACKAGE_DIR>/certificates/ directory with all certificates required for installation:

cd /opt/workfusion/wf_installer
./generate-certificates.sh cert-all

To distribute the <PACKAGE_DIR>/certificates folder, config.yml and secrets.yml files across all other Linux servers.

  • Create the wf_configs.tar.gz archive of these files:

    tar czvf wf_configs.tar.gz certificates config.yml secrets.yml

  • Copy wf_configs.tar.gz to all other servers. A Python SimpleHTTPServer can be useful. Start the HTTP server on any port which is accessible on the DB server for other servers:

    Example: SimpleHTTPServer is on port 9999

    python -m SimpleHTTPServer 9999

    This command makes the directory content where the command was executed downloadable via HTTP.

Run the next steps on all other Linux servers.

  1. Log in to the target server as root and download wf_configs.tar.gz from the DB server:

    cd /opt/workfusion/wf_installer

## install wget if not installed
yum -y install wget
wget http://db_hostname:9999/wf_configs.tar.gz -O wf_configs.tar.gz

  2. Unpack configuration files and certificates:

    tar xzvf wf_configs.tar.gz -C /opt/workfusion/wf_installer/

Install WorkFusion license

Perform the step below on the APP server. Copy license.properties file (obtained from WorkFusion) to /opt/workfusion/wf_installer/:

Example: full path of the license file

/opt/workfusion/wf_installer/license.properties
← PreviousNext →