Migration to 3.0.0 from earlier releases

1. Database Migration

Due to changes in construction of payloads stored in database, migration of data from AAM 2.x to 3.x and then from 3.x to 4.x/5.x is required. Necessary scripts can be found in here both for Core AAM and Platform AAM. Depending on your release, you might need to run both scripts. More specifically:

• if you have 1.x release of symbIoTe (i.e. 2.x release of AAM) you need to run both 2.0_to_3.0.js and 3.0_to_4.0.js
• if you have 2.x release of symbIoTe (i.e. 3.x release of AAM) you need to run only 3.0_to_4.0.js

First, please shut down your current deployment to avoid any data corruption. Then, you can run the migration scripts by simply executing the following command:
mongo {mongo_host}:{mongo_port} {script.js}

e.g. mongo 127.0.0.1:27017 3.0_to_4.0.js

DISCLAIMER: Regarding the platform migration scripts, all the accounts will be automatically set to ACTIVE with the serviceConsent set to true. This is not GDPR-compliant, but we recommend this approach for testing environments. For production, we recommend to run the core scripts on the platform side as well, and to require email verification and service consent request from the users registered in your PAAM.

2. Upgrading to the newest version 3.0.0

Starting from 3.0.0 release, the preferred method of deploying the symbIoTe cloud framework is by using Docker. If you want to migrate from a manual deployment to a docker deployment, you can follow this guide.

The previous approaches of deploying from sources and deploying from jars will not be actively supported. However, if you insist on using these approaches, you have to do the following:

• Deploying from sources: You have to
  • pull the latest master branches
  • re-compile and deploy
• Deploying from jars: You have to update the correct version of the each component in the symbioteCloud.sh. The latest version can be found either in the Releases tab of the corresponding repository e.g. for Registration Handler it is 3.0.0 or in jitpack.

3. Reconfigure the platform

• Download again the configuration.zip from the administration
• Reload the nginx configuration using the latest configuration which you downloaded on the previous step