CCM Configuration Introduction
CCM uses Supervisor (a client/server system that allows its users to control a number of processes on UNIX-like operating systems) to manage the execution of continuous processes.
Note:
A number of these parameters are also specified in CCM Admin, but are not automatically migrated to the structures described here.
The environments and command lines that control the execution of processes user control of Supervisor are contained in several configuration files:
The file, supervisord.conf, contains configuration parameters for supervisord, the controlling service. Subordinate configurations for applications are contained in *.conf files, typically in a conf.d directory under the main supervisorConfig/ .
supervisorConfig/
├── supervisord.conf
└── conf.d
├── eleadv2.conf
├── demo.conf
├── pccw.gem.conf
├── pccw.gemx.conf
├── pccw.router.conf
├── pccw.stream.conf
├── pccwtcpa.gem.conf
├── pccwtcpa.gemx.conf
├── pccwtcpa.router.conf
├── pccwtcpa.stream.conf
├── pccwtcpa.web.conf
└── read.me
Within supervisord.conf, the [include] section specifies the location of sub-configs.
[include]
files = /etc/supervisor/conf.d/*.conf
The following is an example of the contents of a *.conf file. This example is for the CCM web application.
[program:demoweb]
directory=/git/ccm/ccmDemo/ccmex/ccm/bin
environment=PORT="1335",REDISDB="6",
CCMTENANT='demo',SMRTAPI='api.smrttouch.com:80/api/v1/',
TOKEN="a1d9c44c084596e1d30e0413122d4d41aed853c81cca9b44c0a2387623"
command=node www
autostart=false
autorestart=true
startretries=5
stdout=/git/ccm/logs/demo.ccmweb.out.log
stderr=/git/ccm/logs/demo.ccmweb.out.err
user=root
Execution parameters for CCM processes are specified via environment variables for the web application and through command line parameters for other processes. The directory= and command= parameters are also process-specific. These parameters are described in the following sections.
Other supervisord parameters are described in the supervisord documentation.