Difference between revisions of "GeoNetwork Configuration"
m |
|||
| Line 1: | Line 1: | ||
| − | |||
[http://geonetwork-opensource.org/ GeoNetwork] is a catalog application to manage spatially referenced resources, thus is a strategic technology for all geospatial application. | [http://geonetwork-opensource.org/ GeoNetwork] is a catalog application to manage spatially referenced resources, thus is a strategic technology for all geospatial application. | ||
Purpose of this page is to explain how to configure a GeoNetwork service instance in order to fulfill the needs of gCube environment. | Purpose of this page is to explain how to configure a GeoNetwork service instance in order to fulfill the needs of gCube environment. | ||
Please refer to its official website for further configuration details and more comprehensive documentation. | Please refer to its official website for further configuration details and more comprehensive documentation. | ||
| − | = | + | =Installation= |
| + | GeoNetwork version adopted by the gCube infrastructure is 2.8.0 , available [http://sourceforge.net/projects/geonetwork/files/GeoNetwork_opensource/v2.8.0/ here]. | ||
| + | |||
| + | Prerequisites are : | ||
| + | *java7 jre sun | ||
| + | *apache tomcat 7 | ||
| + | *postgres 9 | ||
| + | *postgis2 | ||
| + | |||
| + | In order to configure GeoNetwork to use postgis jdbc connection to the local database, please refer to [http://geonetwork-opensource.org/manuals/2.8.0/eng/users/index.html official documentation]. | ||
| + | |||
| + | Please, note that the jdbc url to the database must have the form ''jdbc:postgis://<HOST>:<PORT>/<DATABASE_NAME>'', other wise the spatial metadata catalog is created as a shapefile, which may cause a loss of performance. | ||
| + | |||
=Security= | =Security= | ||
| + | |||
| + | To reproduce visibility and security means of the gCube infrastructure, the security module of GeoNetwork need to be configured accordingly to the scope(s) in which it is registered in. | ||
| + | Please note that the following conventions needs to be maintained according to the infrastructure state. | ||
| + | |||
| + | |||
==Groups== | ==Groups== | ||
| + | For each scope in which the GeoNetwork instance is registered in, the administrator must create a group with the same name of the scope. | ||
| + | |||
| + | I.e. Let's assume our instance to be registered both in ''d4science.research-infrastructures.eu'' and in ''d4science.research-infrastructures.eu/gCubeApps''. The GeoNetwork must be configured with at least the 2 groups ''d4science.research-infrastructures.eu'' and ''gCubeApps''. | ||
| + | |||
==Users== | ==Users== | ||
| + | |||
| + | Other then at least one administrator user, 2 users must be set for each and every scope in which the GeoNetwork is registered. | ||
| + | |||
| + | |||
=GeoNetwork categories= | =GeoNetwork categories= | ||
| + | =External resources= | ||
=GUI Customization= | =GUI Customization= | ||
| + | =Replica management= | ||
Revision as of 17:33, 24 May 2013
GeoNetwork is a catalog application to manage spatially referenced resources, thus is a strategic technology for all geospatial application. Purpose of this page is to explain how to configure a GeoNetwork service instance in order to fulfill the needs of gCube environment. Please refer to its official website for further configuration details and more comprehensive documentation.
Contents
Installation
GeoNetwork version adopted by the gCube infrastructure is 2.8.0 , available here.
Prerequisites are :
- java7 jre sun
- apache tomcat 7
- postgres 9
- postgis2
In order to configure GeoNetwork to use postgis jdbc connection to the local database, please refer to official documentation.
Please, note that the jdbc url to the database must have the form jdbc:postgis://<HOST>:<PORT>/<DATABASE_NAME>, other wise the spatial metadata catalog is created as a shapefile, which may cause a loss of performance.
Security
To reproduce visibility and security means of the gCube infrastructure, the security module of GeoNetwork need to be configured accordingly to the scope(s) in which it is registered in. Please note that the following conventions needs to be maintained according to the infrastructure state.
Groups
For each scope in which the GeoNetwork instance is registered in, the administrator must create a group with the same name of the scope.
I.e. Let's assume our instance to be registered both in d4science.research-infrastructures.eu and in d4science.research-infrastructures.eu/gCubeApps. The GeoNetwork must be configured with at least the 2 groups d4science.research-infrastructures.eu and gCubeApps.
Users
Other then at least one administrator user, 2 users must be set for each and every scope in which the GeoNetwork is registered.
