Installing the software

Where do I get the installer?

The software is distributed through the Website at

Use the platform independent installer (.jar) for all platforms except Windows. Windows has a .exe file installer.

System requirements

GeoNetwork can run either on MS Windows , Linux or Mac OS X .

Some general system requirements for the software to run without problems are listed below:

Processor : 1 GHz or higher

Memory (RAM) : 1 GB or higher

Disk Space : Minimum of 512MB of free disk space. Additional space is required depending on the amount of spatial data that you expect to upload.

Other Software requirements : A Java Runtime Environment (JRE 1.6.0). For server installations, Apache Tomcat and a dedicated JDBC compliant DBMS (MySQL, Postgresql, Oracle) can be used instead of Jetty and H2.

Additional Software

The software listed here is not required to run GeoNetwork, but can be used for custom installations.

  1. MySQL DBMS v5.5+ (All) [1]
  2. Postgresql DBMS v7+ (All) [1]
  3. Apache Tomcat v5.5+ (All) [1]

Supported browsers

GeoNetwork should work normally with the following browsers:

  1. Firefox v1.5+ (All) [1]
  2. Internet Explorer v8+ (Windows)
  3. Safari v3+ (Mac OS X Leopard)

How do I install GeoNetwork opensource?

Before running the GeoNetwork installer, make sure that all system requirements are satisfied, and in particular that the Java Runtime Environment version 1.6.0 is set up on your machine.

On Windows

If you use Windows, the following steps will guide you to complete the installation (other FOSS will follow):


Avoid installing in a directory containing spaces. Best is to install in c:\programs and not in c:\program files

  1. Double click on geonetwork-install-2.10.x.exe to start the GeoNetwork opensource desktop installer
  2. Follow the instructions on screen. You can choose to install the embedded map server (based on GeoServer and the European Union Inspire Directive configuration pack. Developers may be interested in installing the source code and installer building tools. Full source code can be found in the GeoNetwork github code repository at
  3. After completion of the installation process, a ‘GeoNetwork desktop’ menu will be added to your Windows Start menu under ‘Programs’
  4. Click Start>Programs>GeoNetwork desktop>Start server to start the Geonetwork opensource Web server. The first time you do this, the system will require about 1 minute to complete startup.
  5. Click Start>Programs>Geonetwork desktop>Open GeoNetwork opensource to start using GeoNetwork opensource, or connect your Web browser to http://localhost:8080/geonetwork/



Packages to be installed

The installer allows to install these additional packages:

  1. GeoNetwork User Interface: Experimental UI for GeoNetwork using javascript components based on ExtJs library.
  2. GeoServer: Web Map Server that provides default base layers for the GeoNetwork map viewer.
  3. European Union INSPIRE Directive configuration pack: Enables INSPIRE support in GeoNetwork.
  • INSPIRE validation rules.
  • Thesaurus files (GEMET, Inspire themes).
  • INSPIRE search panel.
  • INSPIRE metadata view.
  1. GAST: Installs GeoNetwork’s Administrator Survival Tool. See GeoNetwork’s Administrator Survival Tool - GAST.

Installation using the platform independent installer

If you downloaded the platform independent installer (a .jar file), you can in most cases start the installer by simply double clicking on it.

Follow the instructions on screen (see also the section called On Windows).

At the end of the installation process you can choose to save the installation script.


Save the installation script for commandline installations

Commandline installation

If you downloaded the platform independent installer (a .jar file), you can perform commandline installations on computers without a graphical interface. You first need to generate an install script (see Figure Save the installation script for commandline installations). This install script can be edited in a text editor to change some installation parameters.

To run the installation from the commandline, issue the following command in a terminal window and hit enter to start:

java -jar geonetwork-install-2.10.0.jar install.xml
[ Starting automated installation ]
Read pack list from xml definition.
Try to add to selection [Name: Core and Index: 0]
Try to add to selection [Name: GeoServer and Index: 1]
Try to add to selection [Name: European Union INSPIRE Directive configuration pack and Index: 2]
Try to add to selection [Name: GAST and Index: 3]
Modify pack selection.
Pack [Name: European Union INSPIRE Directive configuration pack and Index: 2] added to selection.
Pack [Name: GAST and Index: 3] added to selection.
[ Starting to unpack ]
[ Processing package: Core (1/4) ]
[ Processing package: GeoServer (2/4) ]
[ Processing package: European Union INSPIRE Directive configuration pack (3/4) ]
[ Processing package: GAST (4/4) ]
[ Unpacking finished ]
[ Creating shortcuts ....... done. ]
[ Add shortcuts to uninstaller  done. ]
[ Writing the uninstaller data ... ]
[ Automated installation done ]

You can also run the installation with lots of debug output. To do so run the installer with the flag -DTRACE=true:

java -DTRACE=true -jar geonetwork-install-2.10.0.jar
[1](1, 2, 3, 4) All = Windows, Linux and Mac OS X

User interface configuration

As mentioned above, GeoNetwork now provides two user interfaces:

  • Default user interface is the old user interface from 2.6.x and earlier
  • Javascript Widgets user interface is the new user interface for searching, editing and viewing metadata records in 2.8.x

The catalog administrator can configure which interface to use in WEB-INF/config-gui.xml as follows.

Configuring the Default user interface

WEB-INF/config-gui.xml is used to define which home page to use. To configure the Default user interface use:

<client type="redirect"

Configuring the Javascript Widgets user interface

Widgets can be used to build custom interfaces. GeoNetwork provides a Javascript Widgets interface for searching, viewing and editing metadata records.

This interface can be configured using the following attributes:

  • parameter is used to define custom application properties like default map extent for example or change the default language to be loaded
  • createParameter is appended to URL when the application is called from the administration > New metadata menu (usually “#create”).
  • stateId is the identifier of the search form (usually “s”) in the application. It is used to build quick links section in the administration and permalinks.

Sample configuration:

<!-- Widget client application with a tab based layout -->
<client type="redirect"

Configuring the user interface with configuration overrides

Instead of changing config-gui.xml file, the catalog administrator could use the configuration overrides mechanism to create a custom configuration (See Configuration override). By default, no overrides are set and the Default user interface is loaded.

To configure which user interface to load, add the following line in WEB-INF/config-overrides.xml in order to load the Widgets based user interface:


XSLT processor configuration

The file INSTALL_DIR/web/geonetwork/WEB-INF/classes/META-INF/javax.xml.transform.TransformerFactory defines the XSLT processor to use in GeoNetwork. The allowed values are:

  1. de.fzi.dbs.xml.transform.CachingTransformerFactory: This is the Saxon XSLT processor with caching (recommended value for production use). However, when caching is on, any updates you make to stylesheets may be ignored in favour of the cached stylesheets.
  2. net.sf.saxon.TransformerFactoryImpl: This is the Saxon XSLT processor without caching. If you plan to make changes to any XSLT stylesheets you should use this setting until you are ready to move to production.

GeoNetwork sets the XSLT processor configuration using Java system properties for an instant in order to obtain its TransformerFactory implementation, then resets it to the original value, to minimize affect the XSL processor configuration for other applications that may be running in the same container.

Database configuration

Geonetwork uses the H2 database engine as default. The following additional database backends are supported (listed in alphabetical order):

  • DB2
  • H2
  • Mckoi
  • MS SqlServer 2008
  • MySQL
  • Oracle
  • PostgreSQL (or PostGIS)

To configure one of these databases for use by GeoNetwork, three steps are required.

Choose a Database Connection Pool

To manage connections with the database efficiently, a database connection pool is used. GeoNetwork uses the Apache Database Connection Pool (DBCP). This connection pool can be configured directly in the config.xml file described below or in Jetty/tomcat through the Java Naming and Directory Interface (JNDI).

  • ApacheDBCPool: This pool is recommended for smaller catalogs (less than 10,000 records).
  • JNDIPool: This pool is configured in Jetty or Tomcat. It is recommended for larger catalogs (especially those with more than approx 30,000 records).

More details about the DBCP configuration parameters that can be used here are in the advanced configuration section of this manual (See Database configuration).

Download and install JDBC Drivers

For the Apache DBCP pool, JDBC database driver jar files should be in INSTALL_DIR/WEB-INF/lib. For Open Source databases, like MySQL and PostgreSQL, the jar files are already installed. For commercial databases like Oracle, the jar files must be downloaded and installed manually. This is due to licensing issues.

Specify configuration in GeoNetwork

GAST provides a graphical user interface to make database configuration easy. You can find out how to do this in the GAST section of the manual: GeoNetwork’s Administrator Survival Tool - GAST.

Alternatively you can manually configure the database by editing INSTALL_DIR/WEB-INF/config.xml. In the resources element of this file, you will find a resource element for each database that GeoNetwork supports. Only one of these resource elements can be enabled. The following is an example for the default H2 database used by GeoNetwork:

<resource enabled="true">
    <validationQuery>SELECT 1</validationQuery>

If you want to use a different database, then you need to set the enabled attribute on your choice to “true” and set the enabled attribute on the H2 database to “false”. NOTE: If two resources are enabled, GeoNetwork will not start.

As a minimum, the <user> , <password> and <url> for your database need to be changed. Here is an example for the DB2 database:

<resource enabled="true">
    <validationQuery>SELECT 1 FROM SYSIBM.SYSDUMMY1</validationQuery>

Starting up GeoNetwork with a new database

At startup, GeoNetwork checks if the database tables it needs are present in the currently configured database. If not, the tables are created and filled with initial data.

If the database tables are present but were created with an earlier version of GeoNetwork, then a migration script is run.

An alternative to running these scripts automatically is to execute them manually. This is preferable for those that would like to examine and monitor the changes being made to their database tables.

  • The scripts for initial setup are located in INSTALL_DIR/WEB-INF/classes/setup/sql/create/
  • The scripts for inserting initial data are located in INSTALL_DIR/WEB-INF/classes/setup/sql/data/
  • The scripts for migrating are located in INSTALL_DIR/WEB-INF/classes/setup/sql/migrate/

Issues or exceptions with databases

If you run into problems when you start GeoNetwork with a particular database, you may find a solution in the Specific Database Issues section of this manual.

Upgrading to a new Version

The upgrade process from one version to another is typically a fairly simple process. Following the normal setup instructions, should result in Geonetwork successfully upgrading the internal datastructures from the old version to the new version. The exceptions to this rule are:

  • Migration to Geonetwork 2.8 will reset all harvesters to run every 2 hours. This is because the underlying harvester scheduler has been changed and the old schedules are not longer supported. In this case one must review all the harvesters and define new schedules for them.
Previous: New Features