Upgrade

Higson Applications Upgrade

This is wise to upgrade Higson applications (the Studio and Runtime) for a newer version as we are repairing bugs and adding new features, so let’s check how to do it in a few short steps. This article refers to patch installation.

IMPORTANT:

  • As far higson-studio and higson-runtime are separate applications we truly recommend running them the same version.
  • Higson Studio MUST BE STARTED FIRST! Higson Studio is managing the Database Schema!

Bump the Studio Application First#

Download Studio#

Firstly, download application from here. After filling the form, you will get mail with a link to your download page. Depending on your needs, download the file/files (probably you use a war file with your tomcat).

Shut Down Old Studio#

Turn off the Studio App. You probably want to stop all running applications which are using higson-runtime, because we need to modify its database schema.

Remember to Create a Database Backup#

Due to the fact, there might occur database updates, it would be very helpful if you prepare a Higson’s database backup. Use a database client to create the backup. Do not use a snapshot (Higson Studio functionality), as snapshots do not store history.

Check out properties

Make sure that application properties are up to date.

Take a look at your property source (by default: {your_tomcat_dir}/conf/application.properties) and change them regarding the table followed the link Pay special attention to database connection properties.

Adjust ports

If necessary, modify the server.xml file (adjust ports as in previous version).

Start the Studio Application#

You should be able to see a standard login page (by default: https://{serverUrl}/higson/app)

Bump the Runtime in Your Applications#

Since Runtime is available at Maven Central repositories, you should only bump its version at your building script, ie: build.gradle, pom.xml etc.

Migrate Between Versions

Developer License Requirement (version 4.3)#

Starting from version 4.3, a developer license is required on all non-production environments. Before completing the upgrade to version 4.3, ensure that a developer license has been obtained for each non-production environment.

To obtain a developer license, contact:

Bump the Studio Application#

Understanding dependencies between applications:

  • Higson Studio and Higson Runtime are separate applications but should run on the same version.
  • Higson Studio must be started first, as it manages the database schema.

Download new Studio

The first step you should do is to head for new applications here. Search for version of 4.2

Shut down the Studio

Turn off the Studio App. You probably want to stop all running applications which are using higson-runtime, because we need to modify its database schema.

Remember to create a database backup!

Due to the fact, there might occur database updates, it would be very helpful if you prepare a Higson’s database backup. Use a database client to create the backup. Do not use a snapshot (Higson Studio functionality), as snapshots do not store history.

Check out new properties

Make sure that applicatio properties are set up correctly.

Take a look at your property source (by default: {your_tomcat_dir}/conf/application.properties) and change them regarding the table followed the link Pay special attention to database connection properties and security properties.

Adjust ports

If necessary, modify the server.xml file (adjust ports as in version 4.0 or 4.1).

Start the Studio App

You should be able to see a standard login page (by default: https://{serverUrl}/higson/app)

Bump the Runtime in Your Applications#

Since Runtime is available at Maven Central repositories, you should only bump its version at your building script, ie: build.gradle, pom.xml etc. Check out the new properties for Runtime App since there were a lot of changes.