Locked History Actions

deegree3/CatalogueService

NOTE: This page is outdated. If you are looking for up-to-date information, please refer to the official documentation on the deegree homepage.

deegree 3 catalogueService

1. Features of the implementation

  • Implementation of the CSW 2.0.2 specification

  • Fully transactional
  • High performance and excellent scalability due to document-oriented storage and streaming architecture
  • Currently supported Application Profiles / Backends
    • ISO Metadata Application Profile 1.0.0 / PostGIS
    • ISO19115 metadata standard
  • Pluggable and modular dataacess layer allows to add support for new APs and backends
  • Status of the catalogueService configurable to read-only-CSW or read-write-CSW

  • Modular inspector architecture allows to validate records to be inserted against various criteria (e.g. schema validity, identifier integrity, INSPIRE requirements, ...)
  • Supports KVP, XML and SOAP (1.1 and 1.2) requests
  • Handles all queryable properties (for Dublin Core as well as ISO profile)

2. See a demo installation

A running version can be accessed on the deegree CSW demo server.

3. Run your own installation

Additionally to the steps listed here, you also need a PostgreSQL installation with PostGIS extension (tested with the combination 8.3/1.3).

Make sure you created a PostGIS-enabled database.

Login to the services console (password is "deegree").

Now you need to set up

  • the jdbc connection

  • the metadataStore.

3.0.1. JDBC connection

  1. For easy setup it is recommended to create an empty database inside your Postgres installation named "deegree-csw". This name is of course configurable to suit your needs, but it is the default name in the following steps. So to keep it simple in your very first setup, please use pgadmin (or the command line, if you are familliar with psql), to create a database with the following parameters:
    db name: deegree-csw
    user: postgres
    password: postgres
    encoding: UTF-8
    template: template_postgis
  2. In the Adminstration Console click the link jdbc.
    jdbc.png

  3. In the list of JDBC connections you will find the preconfigured JDBC connection named conn1, which is prefconfigured to connect to PostGIS database deegree-csw on localhost with login "postgres/postgres". If any of these needed to be adapted for your setup, please click Edit and apply the needed changes. When done click Save and then Reload (at the top of the screen).

  4. Click Test to see if your database connection works.

3.0.2. Metadata Store

  1. Next, click on metadata stores. We're going to create the needed tables in your database now.

  2. In the list of Metadata stores, there is a preconfigured metadata store named iso19115. Click Setup tables and Execute (at the bottom). You should see a response saying ... statements executed successfully. metadataStore.png

3.1. Testing the installation

  1. There are two easy possibilities to use the catalogueService:
    • using the Generic OGC client to fire xml statements against the service OR

    • using deegree catalogueManager to search on the service and edit metadata (perform transaction operations). TBD: More text needed. How to access the catalogue manager?

4. Configuration basics

To modify the configuration of the catalogueService please visit the page MetadataStoreConfiguration. If you want to get deeper into the configuration basics you're welcome to consult the deegree3/WorkspaceConfiguration which describes the common configuration concept in deegree3.

5. Configuration of catalogueManager

Since the deegree 3 cswDemo (zip/tar.gz version) is bundled with the catalogueManager (which is based on deegree 2 technology) there is some additional explanation needed. For further reading please visit the dedicated page for deegree catalogueManager.

The configuration of the deegree catalogueManager is completely different to the configuration concepts for deegree 3. While one can configure a lot of things regarding the CSW, there is one little bolt regarding the catalogueManager. Unfortunately this one is a little complicated to find. In deegree-csw webapplication go to

webapps/ROOT/WEB-INF/conf/cataloguemanager/

and open the xml-file cataloguemanager.xml:

  • catmanConf.png

These are the very first rows of that document. Find the element md:onlineResource and change the default location of the CSW (which in this case is http://localhost:8080/deegree-csw-demo/services) to your individual needs.

6. Troubleshooting

6.1. Exceptions

In general, if there is any exception regarding the database-connection, you have to check the configuration in /WEB-INF/conf/jdbc/conn1.xml
Some of the exceptions regarding the database-connection are like:

  • org.postgresql.util.PSQLException: FATAL: database >>deegree-csw<< doesn't exist

  • org.postgresql.util.PSQLException: FATAL: Password-Authentification for user >>postgrs<< failed


CategoryDeegree3