Updating ECCM involves the following steps:

  1. 0. Create a backup of the data;
  2. 1. Download and extract the archive containing the new version of the ECCM startup files;
  3. 2. Shut down the old version of ECCM;
  4. 3. Run the new version of ECCM.

Obtaining a license

Starting with version 2.1, licensing for the ECCM management system is handled via the ELM license server.

To run ECCM in a restricted access network, the Offline ELM server must be installed.

ECCM services are compatible with PostgreSQL version 14.10.

If you are updating to version 2.4 from version 1.6 (or earlier), before proceeding with instructions in this section do the following:

  1. Update to version 1.7 (since the PostgreSQL database must be updated from version 12.5 to version 14.2).
  2. Update to version 1.8.
  3. Update to version 1.9.
  4. Update to version 1.10.
  5. Update to version 1.11.
  6. Update to version 1.12.
  7. Update to version 1.13.
  8. Update to version 2.0.
  9. Update to version 2.1. Detailed instructions are provided in the Update 2.0 → 2.1 section.
  10. Update to version 2.2. Detailed instructions are provided in the Update 2.1 → 2.2 section.
  11. Update to version 2.3. Detailed instructions are provided in the Update 2.2 → 2.3 section.

Version 2.4 is not backward compatible with license files from versions prior to 2.1.

To obtain updated licenses, please contact the Eltex sales department by phone at +7 383 274-10-01, by email at eltex@eltex.ru, or request a call via the website: http://eltex-co.com/

Creating a backup

To ensure the ability to revert to a previous version, create a data backup before starting the update. If ECCM is installed on a virtualized server, take a system snapshot. Otherwise, create a backup of the ECCM database using PostgreSQL.

Downloading and extracting the archive

Before installing the new version of ECCM, it is necessary to download the archive containing the system files. The files required to run the project are distributed as a .tar.gz archive and can be obtained from a public cloud storage service. Upload the archive to the server and extract it. It is recommended to extract the archive into a separate directory created in advance:

wget "https://cloud.eltex-co.ru/index.php/s/P8xDfmyo3XyEs0g/download?path=%2F&files=eccm-2.4.tar.gz" -O eccm-2.4.tar.gz
mkdir eccm
sudo tar -zxvf eccm-2.4.tar.gz -C eccm/

For your convenience, it is recommended to place the files needed to run the new version in a directory adjacent to the old one, here's the example:

$ tree -L 2 --dirsfirst
.
├── 2.3
│   ├── eccm
│   ├── postgres
│   ├── README.md
│   ├── args-compose-tools.log
│   ├── compose-tools.sh
│   ├── generate-cert.sh
│   └── technical_support.sh
└── 2.4
    ├── eccm
    ├── postgres
    ├── README.md
    ├── args-compose-tools.log
    ├── compose-tools.sh
    ├── generate-cert.sh
    └── technical_support.sh



For a multi-host installation, download and extract the archive to both the ECCM server and the database server.


Shutting down the old version of ECCM

Shutting down ECCM services in a single-host installation

In ECCM version 2.4, the structure of event generation rules and issue generation rules has been modified. If these rules have been modified during operation, they must be renamed to prevent the system rules from being reset to their default values.

When ECCM is running on a single host (ECCM and the database are on the same server), to shut down the old version of ECCM and remove the containers, run the following command from the directory containing the old version of ECCM’s startup files:

cd <path to the directory containing ECCM 2.3 startup files>
sudo ./compose-tools.sh --stop --delete-containers


Shutting down ECCM services in a multi-host installation

In ECCM version 2.4, the structure of event generation rules and issue generation rules has been modified. If these rules have been modified during operation, they must be renamed to prevent the system rules from being reset to their default values.

When ECCM is running on multiple hosts (ECCM on one server, the database on another), to shut down the old version of ECCM, run the commands described below.

On the ECCM server:

cd <path to the directory containing the ECCM 2.3 startup files>
sudo ./compose-tools.sh --stop --delete-containers

On the database server:

cd <path to the directory containing the ECCM 2.3 startup files>/postgres
sudo docker compose down


Launching the new version of ECCM

Launching the new version of ECCM in a single-host installation

For a single-host system, after successfully shutting down the old version of ECCM, go to the directory where the archive containing the new version of ECCM was extracted and run the following command:

cd <path to the directory containing the ECCM 2.4 startup files>
sudo ./compose-tools.sh --pull --start <IP ADDRESS>

Launching the new version of ECCM in a multi-host installation

If the system was installed on multiple hosts, to launch the new version of ECCM run the following commands.

On the database server:

cd <path to the directory containing the ECCM 2.4 startup files>/postgres
sudo docker compose up -d

On the ECCM server:

cd <path to the directory containing the ECCM 2.4 startup files>
sudo ./compose-tools.sh --pull --start <IP ADDRESS> --database-host <IP ADDRESS DATABASE> --database-port <PORT DATABASE>