9.2

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 9.2.x System Requirements
  • SSH access is allowed to the servers with root privileges
  • If created manually, a non-privileged user (WF_USER) must have the same name, UID, and GID.
  • DNS names for all servers (Linux and Windows) are configured according to 9.2.x DNS Names Configuration
  • Application Ports are open between servers
  • Installation packages are uploaded to servers
  • /opt/workfusion—INSTALL_DIR—default Workfusion installation directory. Change it to your own if necessary
  • /opt/workfusion/wf_installer-<PACKAGE_DIR>-directory where installation package was extracted

Package extraction

Perform the steps below on all Linux servers.

  1. Log into the target server, for example, 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 Workfusion installation package/installer on the file-system. Grant read access for this directory to all users:

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

  3. Extract 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 DB server.

  1. Log into 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 9.2.x 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 file names provided in secrets.yml):

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

  2. Then 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 may generate Self-Signed certificates. This will populate <PACKAGE_DIR>/certificates/ directory with all certificates required for installation:

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

Distribute files

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

  • Create 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 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. Login into target server as root and download wf_configs.tar.gz from 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 APP server. Copythe license.properties file obtained from WorkFusion to /opt/workfusion/wf_installer/:

Example: full path of the license file

/opt/workfusion/wf_installer/license.properties

Selinux settings

By default, 9.2.0 SPA installer will set SELinux to permissive mode during product deployment. (NOTE starting from SPA 9.2.1 Selinux mode is not modified by SPA installer. So, skip this section if you are installing 9.2.1+).

Perform the following steps on ALL servers if you don't want SPA installer to modify current SELinux configuration on the server.

  1. Before installation go to directory where workfusion installer is extracted and modify the file roles/init-common/tasks/flat-preinstall.yml:

    cd /opt/workfusion/wf_installer
vi roles/init-common/tasks/flat-preinstall.yml

  2. Remove the following lines (2-5):

    - name: Ensure SELinux is set to permissive
    selinux:
    state: permissive
    policy: targeted

  3. Save and exit the file.

← PreviousNext →