(13.3) Deployment Guide
Solution Prerequisites
The following are the solution setup prerequisites.
Hardware requirements
For HA deployment, each machine in the cluster should have the following hardware specifications.
Minimum requirement | |
|---|---|
CPU | 2 cores vCPU (4 cores for non-HA deployment) |
RAM | 4 GB (8 GB for non-HA deployment) |
Disk | 100 GB mounted on / |
NICs | 1 NIC |
Software Requirements
Installation Steps
Internet should be available on the machine where the application is being installed and connections on port 9242 should be allowed in the network firewall to carry out the installation steps. Trailing # is not a part of the command.
Configure Log Rotation
Add the following lines in /etc/docker/daemon.json file (create the file if not there already) and restart the docker daemon using systemctl restart docker. Perform this step on all the machines in the cluster in case of HA deployment.
{
"log-driver": "json-file",
"log-opts": {
"max-size": "50m",
"max-file": "3"
}
}Creating Databases
Create two databases i:e (For UMM & ECM) in the MSSQL/MYSQL server with a suitable name and follow the application installation steps.
Installing Application
Download the deployment script ECM-deployment.sh and place it in any directory. This script will:
delete the ECM-deployment directory in the present working directory if it exists.
clone the ECM-deployment repository from GitLab in the present working directory.
To execute the script, give it the execute permissions and execute it. (on RHEL, run commands with sudo)
# chmod +x ecm-deployment.sh # ./ecm-deployment.shUpdate ECM Environment Variables in the
environment-variables.envfile.Update the UMM Environment Variables.
Get domain/CA signed SSL certificates for ecm FQDN/CN and place the files in
ecm-deployment/docker/certificatesfolder. The file names should beserver.crtandserver.key.Copy the ecm-deployment directory to the second machine for HA. Execute below command
# scp -r ecm-deployment root@machine-ip:~/Go to the second machine and update the environment variables where necessary like INSTANCE_NAME and SERVER_URL
Execute the following commands inside the ecm-deployment directory on both machines.
# chmod 755 install.sh # ./install.shRun 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.
# docker ps
Virtual IP configuration
Repeat the following steps for all the machines in the HA cluster.
Download keepalived.sh script and place it in any directory.
Give execute permission and execute the script. This will create a keep-alived directory.
Configure keep.env file inside
keep-aliveddirectoryGive the execute permission and execute the script:
Adding License and Application Settings
Browse to http://<MACHINE_IP or FQDN:UMM_Port>/umm in your browser (FQDN will be the domain name assigned to the IP/VIP).
Click on the red warning icon on right, paste the license in the field and click save.
Once license is added, go to http://<MACHINE_IP or FQDN>/#/applicationSetting and define application settings.
Restart the services after application settings are defined using below commands inside ecm-deployment directory
docker-compose -f docker/docker-compose.yml down docker-compose -f docker/docker-compose.yml up -d