Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Solution Prerequisites

The following are the solution setup prerequisites.

...


Minimum requirement

CPU

2 cores vCPU 

RAM

4 GB

Disk

100 GB mounted on /

NICs

1 NIC

Software Requirements

OS Compatibility

We require the customer/partner to install the following software on the server.

...

Browser Compatibility

Item

Version

Notes

Chrome

92.0.x

Firefox

Not tested

IE

Not tested

An on-demand testing cycle can be planned

...

  1. Download the deployment script supervisor-tools-deployment.sh. This script will:

    1. delete the supervisor-tools-deployment directory in the present working directory if it exists.

    2. clone the supervisor-tools-deployment repository from GitLab in the present working directory.

  2. To execute the script, give it the execute permissions and execute it. 

    Code Block
    chmod +x supervisor-tools-deployment.sh
    ./supervisor-tools-deployment.sh
  3. For UCCE customers only, execute the following command

    Code Block
     rm /root/supervisor-tools-deployment/docker/config/umm/permissions/tam.json
  4. For UCCX customers only, uncomment the lines 67 - 77 from file /root/supervisor-tools-deployment/docker/docker-compose.yml

    It should looks like

    Code Block
    languagejson
    tam:
    image: gitlab.expertflow.com:9242/supervisor-tools/team-administration:13.2.1
    ports:
    - "8082:8080"
    env_file:
    - ${PWD}/docker/environment-variables/environment-variables.env
    restart: always
    volumes:
    - ${PWD}/docker/trustStore:/usr/local/trustStore
    networks:
    - st
    If the customer is not willing to put database password in environment variables file then follow these steps to configure Vault that will hold database password
  5. Update environment variables  in the following files inside /supervisor-tools-deployment/docker/environment_variables folder.

    1. Update UMM environment variables in the umm-environment-variables.env file.

    2. Update Supervisor Tools Environment variables in the environment-variables.env. See also, Caller Lists Environment Variables to specify variables of the Caller Lists microservice.

  6. Get domain/CA signed SSL certificates for SupervisorTools FQDN/CN and place the files in /root/supervisor-tools-deployment/docker/certificates folder. The file names should be server.crt and server.key.

  7. Copy the supervisor-tools-deployment directory to the second machine for HA. Execute below command 

    Code Block
    scp -r supervisor-tools-deployment root@machine-ip:~/
  8. Go to the second machine and update the environment variables where necessary.

  9. Execute the following commands inside /root/supervisor-tools-deployment directory on both machines.

    Code Block
    chmod 755 install.sh
    ./install.sh
  10. Run the following command to ensure that all the components are up and running. The screenshot below shows a sample response for a standalone non-HA deployment. 

    Code Block
    docker ps

...