To be safe in case of any problems during the update, back up your database and the stages folder before the upgrade.
If the backup is running automated - please check whether the backup was created successfully.
Linux: execute sudo stages stop
Windows: stop the Stages and Stages Search Windows services
Stages V7.12 requires new license files. Please contact Stages support to get an updated version of your license files.
Linux: execute sudo rpm -Uvh stages-…rpm or sudo yum localinstall stages-…rpm, depending on your Linux flavor (if you have installed the rpm to different path then default - /opt/stages - previously: “–prefix=/path/to/stages” also have to be added to the update command)
Windows: execute Stages V7.12 Windows installer in an administrative command prompt and follow the assistant steps
The following actions only apply when upgrading from a release minor to Stages 7.11.5.0.
Admin Jobs now adhere to a script timeout which will abort jobs that exceed the timeout. In case you have intentionally long running admin jobs, set the new configuration property “adminjob.script.timeoutInSeconds” accordingly. The default value is 1800 which is 30 minutes.
The following actions only apply when upgrading from a release minor to Stages 7.11.4.0.
In versions older than 7.11.4.0 moving an element to another process led to database inconsistencies.
It is necessary to cleanup potential database inconsistencies regarding associations.
The preparation step can be done while Stages is running to get an rough estimate of the needed downtime. Preparation: Execute bin/ensureAssociationIntegrity.sh|bat and check the logs/cleanup.log for the runtime of this script. This script searches for inconsistencies, but does not fix them. In case inconsistencies are found (check cleanup.log) the script execution time plus five percent can be assumed as needed downtime for fixing the inconsistencies.
Fix: After Stages is stopped execute bin/ensureAssociationIntegrity.sh|bat -fixit and wait for the completion of the script.