This page last changed on Oct 28, 2010 by jdeolive.

The dbconfig module was recently added to GeoServer trunk community space and as such is still in a working state. This page contains some notes about trying out and working with the module.

Database

By default the database used to store configuration is an H2 database and stored in the root of the GeoServer data directory. The database is called geoserver.db.

The first time GeoServer is started with the dbconfig module it will create a file in the data directory called geoserver.db.properties. This is a properties file containing the connection parameters to the database used to store the configuration. This file can be used to say store the data in a postgresql database.

Configuration Migration

The first time GeoServer is started with the dbconfig module enabled it will import the existing configuration into the underlying database. Upon subsequent startups this will not occur.

When the migration occurs a file called hibernate.marker is created in the root of the data dir. Removing this file will cause the data to be reimported next time GeoServer starts up.

Hibernate Configuration

On startup dbconfig will create a file named hibernate.properties in the root of the data dir if it does not already exist. This file contains the hibernate configuration properties used for dbconfig. You an use this file to say turn on verbose logging about the sql that dbconfig generates.

Document generated by Confluence on May 14, 2014 23:00