Upgrade
In this section you will find information about how to upgrade a previous installation of GeoNetwork Enterprise.
Before you start
Minor updates may be performed in place:
GeoCat Recommends backing up your database and data directory.
For major updates or migrating from an earlier version of GeoNetwork:
GeoCat recommends backing up your database and data directory.
We do not recommend upgrading on a production server. Instead perform a new installation and transfer your data and settings to the new machine.
References:
configuring-database
customizing-data-directory
Minor Update
Release |
GeoNetwork |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoNetwork Enterprise 2022.0 |
3.12.3 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.1 |
3.12.4 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.2 |
3.12.5 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.3 |
3.12.6 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.4 |
3.12.8 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.5 |
3.12.10 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2022.6 |
3.12.11 |
2022 |
2025 |
2027 |
Major Upgrade
See the sections Downloading the Geonetwork Enterprise archive file and Deploying GeoNetwork Enterprise to download GeoNetwork Enterprise 2022.0 and deploy it.
Release |
GeoNetwork |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoNetwork Enterprise 2022 |
3.12 |
2022 |
2025 |
2027 |
GeoNetwork Enterprise 2020.5 |
3.10 |
2020 |
2023 |
2025 |
GeoNetwork Enterprise 2019.5 |
3.6 |
2019 |
2022 |
2024 |
GeoNetwork Enterprise 3.4 |
3.4 |
2018 |
2021 |
2023 |
GeoNetwork Enterprise 3.2 |
3.2 |
2017 |
2020 |
2022 |
GeoNetwork Enterprise 2022.0 includes a feature that encrypts the passwords that are stored in the database for the mail server, harvesters, etc.
The first time the application is started, a file named encryptor.properties is created in the application data directory, which the application uses to decrypt passwords.
It’s recommended to make a backup copy of this file, because if it’s lost, the application will not be able to decrypt the passwords. You can find the exact file path in the log file:
2022-03-02 13:36:32,299 INFO [geonetwork.encryptor] - Generating a new random password for the database password encryptor
2022-03-02 13:36:32,299 INFO [geonetwork.encryptor] - Password database encryptor initialized - Keep the file /opt/tomcat/webapps/geonetwork/data/config/encryptor.properties safe and make a backup. When upgrading to a newer version of GeoNetwork the file must be restored, otherwise GeoNetwork will not be able to decrypt passwords already stored in the database.
If you have already backed up the application data directory, as recommended, this file is already included in the backup.
Troubleshooting
During the first startup after an update, GeoNetwork performs a database migration adjusting any tables to reflect all changes required.
Scripts used:
initial setup:
WEB-INF/classes/setup/sql/create/initial data:
classes/setup/sql/data/migration:
classes/setup/sql/migrate/
Table structure is also adjusted to reflect any changes to the GeoNetwork data model. To monitor these changes add the following to log4j.xml:
<!-- Set hdm2ddl to information to see database setup -->
<logger name="org.hibernate.tool.hbm2ddl" additivity="false">
<level value="INFO"/>
<appender-ref ref="consoleAppender"/>
<appender-ref ref="fileAppender"/>
</logger>