Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Copy the upgradeExport.sh file from the v2.1.0 install directory to the base directory where v2.0.0 was installed
  2. Run the upgradeExport.sh script to create the upgrade file containing the data from the old installation
  3. Copy the exported file from v2.0.0 install directory to the base directory where v2.1.0 is installed
  4. Run the upgradeExportupgradeImport.sh script to import the file into the new installation
  5. Start the new v2.1.0 Chariot MQTT Server.

...

Note: Remember to first deactivate the Chariot License on the old server before installing and activating on the new server.


Upgrading on Windows

The following instructions can be used with upgrading the Chariot MQTT Server on Linux.

  1. Stop old v2.0.0 Chariot MQTT Server.
  2. Copy the upgradeExport.vbs file from the v2.1.0 install directory to the base directory where v2.0.0 was installed.
  3. Run the upgradeExport.vbs script to create the upgrade file containing the data from the old installation.

Image AddedTODO

4. Change to the v2.1.0 install directory and run the upgradeImport.vbs script.

5. If the upgradeImport.vbs script is invoked without specifying a full path to the ZIP upgrade archive, the 'Chose File to Upload' window will appear as shown below:

Image Added

6. Navigate to the Chariot 2.0.0 directory and select the 'chariot_upgrade' ZIP archive created earlier.

7. Click the 'Open' button to import from selected ZIP archive.

8. Make sure Chariot files are imported as shown below:

Image Added

8. Start the new v2.1.0 Chariot MQTT Server.

The new Chariot MQTT Server should be loaded with the Users, Roles, MQTT Credentials, and System & Server configurations from the old installation.  However, the new Chariot MQTT Server will still need to be licensed and any SSL certificates/keys will need to be uploaded again.

Note: Remember to first deactivate the Chariot License on the old server before installing and activating on the new server.