Post Deployment Procedures
After you've deployed CX Contact, you'll want to monitor the status of containers, access logs, upgrade CX Contact components, and so on. This topic describes the post deployment procedures you'll use if you deployed CX Contact using Docker Compose.
Upgrading CX Contact Components
This topic outlines the steps required to upgrade CX Contact components.
- Ensure the CX Contact Docker images included in the upgrade are tagged with the proper version number and are available in the Docker registry.
- Edit the Container Versions section of the .env file to specify one or more versions of the CX Contact components that you're upgrading to. For example, if you're upgrading the List Builder component of CX Contact to version 9.0.000.07.1616, specify the following: CCSListBuilderTag=9.0.000.07.1616
- Execute the following command:
./cxc-app-deploy.sh
TipWhen upgrading, ensure that old containers are stopped and new containers are started. This means that the CX Contact solution is not available during the upgrade.
Using Portainer
Genesys recommends you use Portainer to view the status of all containers and to access logs.
- To start Portainer on the same VM where all containers are started, execute the following command:
docker volume create portainer_data docker run --restart=always -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer --no-auth
- Go to http://<your-vm-ip>:9000. The user interface displays the state of all containers. Open each container and click logs to see the stdout / stderr logs.
Ports
Warning
CX Contact components must use the Docker host network mode. The components must not use Docker bridge networks or swarms, which severely impact performance of the production systems.CX Contact components use the following ports:
Service | Ports used |
---|---|
User Interface (UI) | 8101 - Nignx listener port (static content served) |
API Aggregator |
|
List Builder |
|
Compliance Manager |
|
List Manager |
|
This page was last edited on April 23, 2021, at 18:42.
Comments or questions about this documentation? Contact us for support!