No Results
How to Upgrade edgeCore
Article Contents

We recommend upgrading your edgeCore version to stay up to date with new features, enhancements, and fixed issues.

Upgrading without Using an External Authentication Database

If you are not using an external authentication database, take the following steps to upgrade your edgeCore version:

  1. Create a full backup of the server.
  2. Stop the old version/shut down the instance.
  3. Download the version you want to use and unzip it.
  4. Install the downloaded version (Linux/UNIX or Windows).
  5. Start edgeCore and log in (Linux/UNIX or Windows).
  6. Upload the license.
  7. Restore the previously created full backup.

 

Upgrading with an External Authentication Database

If you are using an external authentication database, take the following steps to upgrade your edgeCore version:

  1. Create a full backup of the server.
  2. Stop the old version/shut down the instance.
  3. Download the version you want to use and uzip it.
  4. Copy the backup archive to the target version server exports folder.
  5. Set up a new database and connect to it.
    Alternatively, you may also use edgeCore’s table partitioning by configuring the following IDs in conf/local.properties:
    db.default.id=EDGE
    db.auth.id=EDGE
    db.config.id=EDGE
    db.cache.id=EDGE01
    This will use a single database, but each edgeCore instance will have its own unique set of tables.
    Additionally, when using a cluster, the cluster will share the same IDs, with the exception of the db.cache.id which should be unique per instance.
  6. Install the downloaded version (Linux/UNIX or Windows).
  7. Start edgeCore and log in (Linux/UNIX or Windows).
  8. Upload the license.
  9. Restore the previously created full backup.

 

Validation after the Upgrade

  • Java version updates may require SSL certs to be re-imported to your CA certs.
  • SQL Transforms may need to be reviewed in case new keywords defined by H2Database are handled appropriately.
  • JavaScript Feeds / Transforms should be reviewed for any issues.
  • General spot checks of Pages and Actions should be validated; If there are errors, you will need to go to the page pipeline to view/resolve any errors.
  • HTML Templates should be reviewed for any issues.
Terms | Privacy
×