9.1. Preparation of an update
General information
When you update Goobi workflow, all plug-ins should also be updated. You should also check the page Installed plug-ins
in Goobi workflow. If this page does not yet exist, the relevant files must be identified in the file system. It is important not to forget the REST API.
Commands from this manual are best copied by clicking on the corresponding icon. Otherwise there is the danger of copying unwanted whitespaces.
Sensible preparatory work before carrying out the update
Checking the condition
To ensure the machine is in good condition, the following items should be checked before and/or after the update:
Creation of a backup
It makes sense to issue the Tomcat before the backup. However, it is necessary to check beforehand that no other user is logged into Goobi workflow. In addition to displaying the users who are logged in in the interface, the last entries in the process log or the last logins can be helpful in assessing the situation:
The Tomcat process for Goobi workflow can then be terminated:
Use the following commands to create a backup directory and copy the files to it:
Commit the current state in the Goobi folder:
Save the current status of the archives:
If an update is performed from a version lower than 24.07 to the current version, all EAD files must be exported from BaseX. To do this, log in at https://URL/basex/dba/login
. Then select each database under Databases
, select the .xml file and download it.
Copy the new files to this machine
It is recommended to copy the files to /tmp/g3 on the machine to be updated. Move the files to the correct paths:
Especially configuration files of plugins can have a different file name due to a change in the naming scheme.
When the work is complete, the timestamp comparison can be used to determine whether all necessary files have been updated:
Plugins that are built as tar
package:
Testing the installed update
The following things should be checked after an update:
Rescue in case of problems
Sometimes errors may occur after the update. The following points help to identify and solve typical problems:
Goobi does not start - ActiveMQ
If the Tomcat hangs after starting, the contents of the folder /opt/digiverso/goobi/activemq/
may be to blame. Emptying and restarting helps in this case:
LayoutWizzard
The LayoutWizzard.jar
in /opt/digiverso/{goobi,itm}/lib/
must be the same Symbolic links do not work.
Implementation of the actual update
After all preliminary work has been carried out, the actual update can take place. This is explained in detail in individual steps here:
Last updated