Solution Prerequisites

...

Browser Compatibility

...

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. If the customer is not willing to put database password in environment variables file then follow these steps to configure Vault that will hold the database password

4. 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.

5. 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.

6. 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:~/

7. Go to the second machine and update the environment variables where necessary.

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

   Code Block
   chmod 755 install.sh ./install.sh

9. 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

   

...