Page Comparison

Installation Files Location

Build Files

• docker-compose.yml
• ecm_variables.env
• ecm-frontend.tar
• ecm-services.tar
• ecm.tar
• umm_12.0.7.tar

Place all build files provided with the release in /root on all machines where the application’s being deployed.

...

Load the images in docker engine on all the machines running following commands (execute each command separately, the command starts after $ sign) : 

$ docker load < ecm.tar

...

$ docker load < umm.tar   

...

$ docker load < ecm-services.tar

...

$ docker load < ecm-frontend.tar

Configuration

Application Configurations 

• Create new databases in the MSSQL server with any names corresponding to umm and ecm and edit the corresponding settings in “docker-compose.yml” file for configuration. Details have been written in the comments.
• Update the DB name required urls URLs and cisco related (IP, Username, and Password) configuration in the “ecm_variables.env” file. DB configurations for umm can be updated directly in “docker-compose.yml”.

...

{ 
	"log-driver": "json-file", 

	"log-opts": 
		{
			"max-size": "20m", # Max size of the log files. 

			"max-file": "3" # The maximum number of log files.
		} 
}

{
	"log-driver":
"json-file", 
	"log-opts": 
			{
				"max-size": "20m", # Max size of the log files. 

				"max-file": "3" # The maximum number of log files.
			} 
}

Troubleshooting

Logs for each container are available in files as well as within docker daemon. To see the logs for any container, execute docker ps and get the id of the container. Use that id to see the logs using docker logs <container_id>. At any given time, the active machine would be the one with highest keepalived priority, so the logs would be stored there.