Jeevlet sandbox

Date	2011/05/30
Contact(s)	Francois
Last edited
Status	on-going
Assigned to release	-
Resources	Available
Ticket

Overview

This proposal aims to create a sandbox for the Jeevlet engine which is a Jeeves flavor based on ​RESTLET. The idea is to add the capability to start many catalogues with only one GeoNetwork installation.

Having a public sandbox will improve the visibility of the project.

Proposal Type

• App: !Jeevlet

Links

• Documents:
• Email discussions:
• Other wiki discussions:

Voting History

• Vote proposed by Francois on 31th May 2011, result was

---

Proposal

In that environment, you could run many catalogues with only one GeoNetwork installation. Each catalogue are defined using a WEB-INF-NodeId directory and started as a GeoNetworkRestletApplication according to that configuration.

All catalogues are sharing the Managers (eg. ThesaurusManager, SchemaManager) but not the configuration (eg. DB, DataDir, LuceneDir).

Pros:

• deploy multiples nodes with one application
  • Tested with more than 100 nodes
• Sharing common resources
  • save disk space
  • save memory usage
• Update all nodes in one step.

Cons:

• Each nodes could not have advanced custom designed (to be improved see ​http://trac.osgeo.org/geonetwork/ticket/214)

Made by Jean-Pascal Boignard and Mathieu Coudert.

The sandbox is composed of:

• svn:externals to trunk
• one new module: jeevlet
• a custom pom to link jeevlet to GeoNetwork main maven module.

Backwards Compatibility Issues

None.

New libraries added

• New module.

Participants

• Francois (Maven module, Proposal)
• Jean-Pascal Boignard and Mathieu Coudert (Core development)