Upgrade CMS

Upgrading CMS (Condition Monitoring System) involves updating the alert database schema and metadata to the latest version. The CMS system also stores some metadata in the directory database, which may need to be updated as well.

To upgrade to a new CMS database schema version, you should first create a backup of the existing alert database. Then, you can run the provided SQL scripts to create a new database or update an existing one.

Run all upgrade scripts in the order they have been numbered, starting from the current schema version to the latest version. If you are upgrading from a previous version, ensure that you have run all necessary migration scripts to bring your database up to date.

Example:

psql --file alert-db-upgrade.2.pgsql  postgres://{username}:{password}@{host}:{port}/{databasename}
psql --file alert-db-upgrade.3.pgsql  postgres://{username}:{password}@{host}:{port}/{databasename}

Remarks

The file variables.pgsql may be updated to customize the database setup. It allow changing database and schema name as well as the user to be created for the database.

Updating Directory Metadata

The directory service database contains metadata, display components, displays, and dashboards that are part of the distribution. This data may be updated in new releases. Run the following command to update metadata.

Complete Syntax:

psql --file seed_mops_eav_entities.pgsql postgres://{username}:{password}@{host}:{port}/{databasename}

Example:

psql --file seed_mops_eav_entities.pgsql postgres://postgres@localhost/dirdb

See deployment package folder <package>/dbdef/alertdb/directory for the script seed_mops_eav_entities.pgsql and other related files.