Upgrading

Upgrade is a complex procedure. Make sure to backup all data according to the below instructions to minimize system downtime if it fails.

Tibbo is doing its best to ensure backwards compatibility between all AggreGate releases, including major ones. However, in some rare cases we have to modify platform's components, unified data model entities, and programmatic interfaces so that minor tweaks of platform-based products and services may be required after upgrading to a new major version.

To upgrade AggreGate Server to the new version, please follow these instructions carefully in order to protect the server database from being corrupted:

  • Stop all AggreGate Clients

Database backup is an important operation. Failing to backup the database before upgrade may result in data loss!

Server installation folder backup is an important operation that should not be skipped in the production environment.

  • Upgrade the server by running the installer of the new version

  • Upgrade all installations of AggreGate Client. Make sure to backup AggreGate Client installation folders before backup.

  • Upgrade the firmware of all Devices if necessary

  • Start AggreGate Server

  • Check the server log to make sure that the server has been started successfully and the database has been upgraded

If the upgrade fails or the system does not work as expected, roll back to the previous version of AggreGate Server and AggreGate Client by restoring their installation folders and AggreGate Server database from backup. Contact Tibbo technical support for solving the problem.

Creating New Resources

The upgraded version of AggreGate may include lots of new built-in resources (alerts, reports, widgets, etc.). These resources are not created automatically during the upgrade. If you'd like to make use of them, run Create Resources () action from the root context and select resources to create. See Managing Built-In Resources for details.

Was this page helpful?