There are three different kinds of upgrades:
- Major upgrades adding significant new functionality or changes to the architecture of the system. For example this could be the upgrade from 9.0.0 to 10.0.0, which added a new instant message feature. These upgrades will usually require changes to the existing data.
- Minor upgrades making small changes to existing functionality. For example this could be the upgrade from 10.0.0 to 10.1.0. These upgrades may require small changes to the existing data.
- Hotfix upgrades correcting issues with the system. For example this could be the upgrade from 10.1.0 to 10.1.1. These upgrades will require no changes to the existing data.
Copy the RPM files to a directory on the server and then use:
rpm -U jiglu-version.rpm jiglu-webapp-version.rpm
Changing version for the version number of the RPMs.
For major and minor upgrades a data upgrade is almost always required. A backup should always be taken prior to these upgrades. For hotfix upgrades even if there is no data upgrade the version number of system stored in the database will always be changed to match the current version.
After the package has been updated it is essential to run the data upgrade. First stop the Jiglu server:
Anyone attempting to use the Jiglu web application will be given a message that the system is currently offline. Next carry out the data upgrade:
Finally, start the Jiglu server once more:
Then restart Tomcat. On OpenSuse use:
systemctl restart tomcat
On Fedora, Redhat or Amazon Linux instead use:
service tomcat restart
Background data upgrades
For some major upgrades it will be necessary to rebuild the text search indexes or to retag all the content when changes have been made to this process. The release notes will inform you when this is necessary.