Updating the application
Before you start
Jasypt encryption settings
Since GeoNetwork 4.0.4, passwords stored in the database for the mail server, harvesters, etc. are encrypted with Jasypt.
By default, a random encryption password is generated when GeoNetwork is started, if it is not already defined, and it is stored in the data directory data/config/encryptor/encryptor.properties
.
If you are using the application data direcotry, the encryption password is stored in the file /geonetwork/WEB-INF/data/config/encryptor/encryptor.properties
.
Warning
This encryptor.propertie
file must be copied to the new installation when upgrading the application; otherwise, it will not be possible to decrypt the existing passwords stored in the database.
If you have set the location of the data directory outside of the application, the file will be stored in this external location at data/config/encryptor/encryptor.properties
Read more at Customizing the data directory.
Updating from GeoNetwork 4.2 to GeoNetwork 4.4
Updating from GeoNetwork 4.2 to GeoNetwork 4.4 is a minor upgrade and may be performed in place.
Before you start:
-
Stop the services:
- Application server running GeoNetwork
-
When using application data directory be sure to backup
/geonetwork/WEB-INF/data/config/encryptor/encryptor.properties
Before you start:
-
Stop the services:
- Application server running GeoNetwork
Update:
-
GeoNetwork 4.4 requires a Java 11 environment (JRE) to be installed on your system.
Later versions of Java will not work at present. This must be done prior to installation.
-
This release of GeoNetwork 4.4 is developed and tested with Elasticsearch
7.17.15
.If required update Elasticsearch, see Installing search platform.
-
Minor update may be performed in place, update
geonetwork
according to installation approach used.Note
Configurations changes made to application
/WEB-INF/
files should be backed up, and the same configuration changes reapplied to the new application.With the service stopped you may find it easier to manually deploy (by unzipping the
geonetwork.war
into the correctwebapps/geonetwork/
location) in order to apply configuration changes to **/WEB-INF/**
.Read more at Configuration.
-
Restore the backup of
encryptor.properties
to the application data directory. -
Restart services:
- Application server for GeoNetwork
-
GeoNetwork 4.4 requires a Java 11 environment (JRE) to be installed on your system.
Later versions of Java will not work at present. This must be done prior to installation.
-
This release of GeoNetwork 4.4 is developed and tested with Elasticsearch
7.17.15
.If required update Elasticsearch, see Installing search platform.
-
Minor update may be performed in place, update
geonetwork
according to installation approach used.Note
Configurations changes made to application
/WEB-INF/
files should be backed up, and the same configuration changes reapplied to the new application.With the service stopped you may find it easier to manually deploy (by unzipping the
geonetwork.war
into the correctwebapps/geonetwork/
location) in order to apply configuration changes to **/WEB-INF/**
.Read more at Configuration.
-
Restart services:
- Application server for GeoNetwork
Guidance:
- Changelog 4.4
- No additional guidance provided at this time.
Upgrade from GeoNetwork 3.0 to GeoNetwork 4.4
Upgrading from GeoNetwork 3.0 to GeoNetwork 4.4 is a major upgrade.
We do not recommend updating a production system. Instead treat this as a migration, setting up a new GeoNetwork 4.0 installation and transfer data and settings.
Before you start:
-
Backup your database
-
Backup your data directory
GeoNetwork for Migration:
-
GeoNetwork 4.4 requires a Java 11 environment (JRE) to be installed on your system.
Later versions of Java will not work at present. This must be done prior to installation.
-
GeoNetwork 4 changes the search engine to Elasticsearch.
For installation instructions see Installing search platform.
-
Perform a new install of GeoNetwork 4.0, according to installation approach used.
-
Configure GeoNetwork use to your database and data directory.
-
Start services:
- Database
- Elasticsearch
- Application server for GeoNetwork
-
GeoNetwork 4 encrypts stored passwords using Jasypt as described at the top of this page.
During startup a random encryption password will be generated and stored in data directory
data/config/encryptor/encryptor.properties
. -
During startup the database schema will be updated to match the table structure required for GeoNetwork 4.
-
GeoNetwork will create indices automatically when connecting to Elasticsearch.
Guidance:
-
Be advised of the following changes in application functionality:
-
Permalink to search page from GeoNetwork 3.x will need to be updated to work with 4.x.
-
Please be advised of the following changes to application services:
- Search / q service is replaced by Elasticsearch
- Virtual CSW end-points are replaced by sub-portals
- RDF DCAT API no longer available
- Z39-50 API is no longer available
- OpenSearch no longer available
- Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is not migrated
- GeoNetwork API support for Report Uploads not migrated
The above links provided recommendations and mitigation measures where appropriate.
-
For information on new features and functionality:
- Changelog 4.2
- Changelog 4.0