This section outlines the necessary steps for migrating Qommentary components between environments. It is important to note that there are three primary scenarios to consider.

Database only

  1. Backup Qommentary Database using pgadmin tool

  2. Restore Qommentary Database in the new Database server

  3. Go to the Qommentary Engine folder

  4. Open the appsettings.json

  5. Update the "ConnectionStrings" > “Qommentary” entry with the new connectionstring

  6. Restart Qommentary Engine application pool in IIS

Example of the appsetting.json entry

"ConnectionStrings": {
    "Qommentary": "zKA40nbrJzFIzu1kXecgP45n1d1f9beA6MBvieX99UUmFMQxc2lpem8x6hV+TNDjgOa3+lvLJAie3Qnl+KbBxghI58LF4DgEHbZdqEpLIVoCIbOA9eFwpGUMXOzNbmTfQTD+LpHUEktCoIW6d7mQI4b2YJKcYy448rVGJk7K0fbbg8n"

You will have to use the DB Connection Utility to encrypt your new connectionstring before updating this entry

Admin Console and Engine only

  1. Install Qommentary on the new environment using the Qommentary Setup Wizard. In the database step, connect to existing database and provide the details related to the existing Qommentary Database.

  2. Re-install the Qlik Sense Client certificate in the new environment

  3. Re-bind the SSL certificate to the Qommentary Manager/Engine sites (if applicable)

  4. Check that the Qommentary Manager/Engine hostnames are whitelisted in the virtual proxy list in the Qlik Management Console (QMC)

  5. Update all Qommentary extensions configurations via Qlik dev-hub if the new environment is using different endpoint URLs.

For more information please check Prerequisites and Installing sections

Database, Admin Console and Engine

This scenario is a combination of the previous sections, so please begin with the "Database only" steps and then proceed with the "Admin console and Engine only" steps.

Last updated