Enter your keyword

Upgrade an existing version

You can upgrade you instance of Ping to the latest version by following the steps below. This will retain all of the data you have entered, all users, all alerts and the data connection to Qlik. You will need to follow these instructions carefully.
NOTE: We will be improving this process in future versions.

The installer for 2019.03.02 (from build version 2019.03.02.14) has a database upgrade facility that allows you to retain all information in the system. The following steps should be followed:

If you plan to move your Ping Alerting install to a different server see this post.

Preparation Steps
  1. Install Redis which is a prerequisite for the 2019.03.02 and later builds.
  2. (Required for Version 2019.02.05.xx) Use the backup process to make a copy of the Ping database with the expected database name of ‘pingalerting’
    • see the backup and restore postĀ for details of the backup process.
    • identify the sourceDb which will be similar to ‘pingFeb2019020501’
      • you can check using the following command line steps (or a GUI tool such as Robo 3T or MongoDB Compass)
        • open a command window
        • change directory to the folder where MongoDB is installed, e.g. C:\Program Files\MongoDB\Server\4.0\bin and press enter
        • enter mongo and press enter
        • enter show dbs and press enter to see a list of databases in your MongoDB server.
    • the newDb value should be set to ‘pingalerting’

 

Upgrade Steps
  1. Make a copy of your Qlik certificates from the C:\Ping <version>\server\ConnectionAPI\qlikSenseEnigma\Certificates folder. Keep these in an easy to identify place as you will upload these into the new Ping install.
  2. Uninstall the existing Ping installation using the add or remove programs window from control panel.
  3. Delete theĀ C:\Ping <version> folder.
  4. Check the services window to ensure the PingSetup service has been removed.
  5. Install the new version of Ping using the new installer.
    NOTE: You will need to manually close a command window at the final stage of this process. Only do this when you see many lines that start with Collection Name=>… with information on records counts as per the example below and message saying it has been completed:
  6. Check that the 3 Ping services (Ping Setup, Ping Qlik Connector, Ping Scheduler) are running.
  7. Login to Ping.
  8. Update the Ping Server DNS or IP, this was previously automated:
    • navigate using the top menu to Admin > Ping Settings.
    • if there are no records in the table, click create new.
    • if a record exists, edit the record by clicking on the pencil icon on the right.
    • enter the DNS or IP of Ping server in the Ping host server name field and click update (this is used for the links in emails).
    • you can leave all the other fields with the default values unless you need to change the Ping ports.
    • save the changes you have made.
  9. Validate the Qlik data connection:
    • navigate using the top menu to Admin > Data Sources.
    • edit the record by clicking on the pencil icon on the right.
    • upload the certificates that you saved in step 1.
    • check the Qlik Sense port settings as these could have the incorrect values, change these to the default Qlik settings (or those required for your Qlik Sense site):
      • Qlik Sense Service Listen Port (HTTPS) is the HTTPS connection port for Qlik Sense. This will normally be the default value of 443 but if this has been customized you can change the value here. You can see if this and the following Qlik Ports have been customized in the QMC in the settings for the proxy you will be connection to.
      • Qlik REST API Listen Port will default to 4243 as per the standard install of Qlik Sense.
      • Qlik Repository Service API Listen Port will default to 4242 as per the standard install of Qlik Sense.
    • Click on Test Connection to validate the connection.
    • Click on Update when you have a successful response.

That’s it, you’ve completed the upgrade process.

 

Troubleshooting

Issue: You have completed the upgrade but some of your alerts setup with a time-based schedule are not triggering.
Resolution: Request that the owner of the alert open the alert record from the my alerts view, click the edit button at the bottom of the page, and then click update. The alert should now start triggering.