Start and shutdown

Start

Automated setup of database tables

PQM checks on startup if the database contains all required tables. If not existing, PQM automatically creates or updates the tables on startup. As long as the table setup or update is running, the health state of the 'trinity/trinity-core-service' is not in state "ready".

Automated setup of messaging queues

PQM checks on startup if the requried message queues are available. If not existing, PQM automatically creates or updates the necessaryqueues. As long as the setup or update is running, the health state of the 'trinity/trinity-core-service' is not in state "ready".

Verify correct startup via health endpoints

In order to verify that PQM application has started or correctly, the health check endpoint can be used. If the response status code is 200 and health_response.health == 'healthy' then services sucessfully started.

Shutdown

Decommissioning

Set the variable 'enabled' in HELM’s 'custom-values.yaml' file to 'false' in case you want to decomission PQM from your IAS installation. Here is an example file for further illustration:

pqm:
      databases:
        pqm:
          serverInstance: externalmssql
          name: DB_PQM_MSSQL
          userName: PQM_user
          password: XXX
        influxpqm:
          userName: pqm_db_user
          name: ias_pqm_influx
          password: XXX
          serverInstance: externalinflux
      enabled: true