Skip to content

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.properties.

If you are using the application data directory, the encryption password is stored in the file /geonetwork/WEB-INF/data/config/encryptor.properties.

Warning

This encryptor.properties 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.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:

  1. Stop the services:

    • Application server running GeoNetwork

  2. When using the application data directory, be sure to back up /geonetwork/WEB-INF/data/config/encryptor/encryptor.properties

Before you start:

  1. Stop the services:

    • Application server running GeoNetwork

Update:

  1. 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.

  2. This release of GeoNetwork 4.4 is developed and tested with Elasticsearch 7.17.15.

    If required update Elasticsearch, see Installing search platform.

  3. 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 correct webapps/geonetwork/ location) in order to apply configuration changes to **/WEB-INF/**.

    Read more at Configuration.

  4. Restore the backup of encryptor.properties to the application data directory.

  5. Restart services:

    • Application server for GeoNetwork

  1. 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.

  2. This release of GeoNetwork 4.4 is developed and tested with Elasticsearch 7.17.15.

    If required update Elasticsearch, see Installing search platform.

  3. 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 correct webapps/geonetwork/ location) in order to apply configuration changes to **/WEB-INF/**.

    Read more at Configuration.

  4. Restart services:

    • Application server for GeoNetwork

Guidance:

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 upgrading a production system in place. Instead, treat this as a migration: set up a new GeoNetwork 4.0 installation and transfer data and settings.

Before you start:

  • Back up your database

  • Back up your data directory

Migration steps:

  1. 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.

  2. GeoNetwork 4 changes the search engine to Elasticsearch.

    For installation instructions see Installing search platform.

  3. Perform a new install of GeoNetwork 4.0, according to the installation approach used.

  4. Configure GeoNetwork to use your database and data directory.

  5. Start services:

    • Database
    • Elasticsearch
    • Application server for GeoNetwork

  6. 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.

  7. During startup the database schema will be updated to match the table structure required for GeoNetwork 4.

  8. GeoNetwork will create indices automatically when connecting to Elasticsearch.

Guidance:

The above links provide recommendations and mitigation measures where appropriate.