Personal tools
You are here: Home Documentation Tutorials Website Administration

Website Administration

Document Actions

Note: This is the print view with all the tutorial pages on one page. The paginated version is available here, if you prefer that.

Introduction

Administrator's Profile

to be added
The administrator has the full rights for managing the system included the creation/management of different groups and users (Fig. 1).

 
 

Figure 1: Administration Tool

 

The Administrator Profile has special privileges that allow for different management activities:
                                               
·       Full rights on creating new groups and new users
·       Rights to change users/groups’ profiles
·       Full rights on creating/editing/deleting new/old data
 

This profile should be assigned only to one/two persons administrating the site.


The user with administrator privileges can manage the creation of various groups corresponding to the various contributors/users (fig. 2) of the database



Figure 2: Groups Management

 

Each group has a number of users with different profiles (user administrator/editor/guest) as follows (fig. 3).

User Administrator Profile:

·       Full rights on creating new users within the own group
·       Rights to change users profiles within the own group
·       Full rights on creating/editing/ deleting new/old data


Editor Profile:

·       Full rights on creating/editing/ deleting new/old data

 

It should be assigned only to all users uploading and editing data.

 

Guest Profile:            

·       Data /Download.

 

It should be assigned to authorized users that need to download password-protected data.




Figure 3: User Management

 

 

Each group will have different data accessibility privileges (fig.4) for each record inserted in the system, depending from the setting of the Data Owner concerning: View, Download, Edit, Delete and Dynamic.

Website Installation: Minimum Requirements

This section will inform you on the minimum requirements needed for the GeoNetwork 2.0 installation, in terms of hardware, software, operating system etc.
Hardware

IBM PC compatible, Intel Xeon, 3 GHz or more

At least 2MB RAM

At least 73 GB SCSI HD, RAID Level 5

Additional SCSI controller for the tape backup unit

Rack to mount the server

Tape backup unit, if not already available in the local structure

 

 

Operating System

Windows 2000 Server SP4

 

 

Software

Sun J2SE 1.4.2

Apache Tomcat 1.4.30

GeoNetwork and InterMap (Open Source software)

MySQL Database

ESRI ArcIMS (Internet mapping software)

GIS Software

 

 

Firewall Settings

 
Incoming Requests

Port 80 (http server)

Port 443 (https server)

Port 2100 (z39.50 server)

Remote Control (Windows Remote Desktop, PC Anywhere, Timbuktu, or VNC over SSH)

 

Outgoing Requests

Port 80 (http client, used for the dynamic mapping)

Ports 210 and 2100 (connection to z39.50 servers)

 

 
Additional requirements

 
Firewall settings

Even though ports 210 or 2100 are used by most of the z39.50 servers, the z39.50 protocol doesn’t specify which port has to be used for the TCP/IP connections, so in order to access a wider range of servers ports 210 and >= 1024 should be opened for the outgoing requests.

 
An external SMTP server should be accessible, or it should be installed on each VAM SIE server, to allow email notification.

 
Bandwidth

The bandwidth specified above is the minimum required for the system to work properly. In the future a wider bandwidth could be needed.

Installation on a Desktop

content to be added
content to be added

Installation on a Server

This manual contains notes on the installation of the GeoNetwork 2.0 on a server and is based on the first beta version.
1. Install first Java 2 SDK (Software Development Kit), SE (Standard Edition) 1.4.2 or newer version.
This package can be downloaded from http://java.sun.com

2. Install Tomcat version 4.1 or newer version if you decide not to use the in the GeoNetwork installation package inbuilt jetty server.
This package can be downloaded from http://jakarta.apache.org/tomcat
After the installation test Tomcat in a browser http://localhost:8080/ (or whichever port you set it up on) and test the example applications in the Tomcat Web Application Manager (especially the servlets).

3. Set up of firewall

3.1. Incoming ports
Make sure that the ports Tomcat is set on are open. The port to install Tomcat can be configured during the installation or in the Tomcat configuration file in the Tomcat Directory /conf/server.xml
The Z39.50 port is used for incoming queries; it is by default 2100 and should be left open to enable the Z39.50 remote search function.

3.2.Outgoing ports:
Since Geonetwork connects to some http ports of other sites for remote alignment and InterMap and some Z39.50 ports it is advisable to allow the server to go outside.

4. The most recent released Geonetwork installer can be downloaded at
https://sourceforge.net/projects/geonetwork/

4.1. Start the installer by double-clicking on the .jar file or type in the command prompt
java -jar

Accessing the McKoi Database with Druid

This document explains how to set up Druid, an open source database management programme, to connect to the McKoi database.


GeoNetwork sets up by default a McKoi database in which the Administration information on Groups, Categories etc. are stored. Moreover the metadata records are stored here. In order to explore the database it is useful to have a database management system of which Druid is an option.

You can use the same procedures to connect to another DBMS you may have selected to use for your GeoNetwork Open Source installation. Connection parameters will be slightly different though.


Druid is a database management program available at http://sourceforge.net/projects/druid.

To install it on you computer please follow the steps below:

1) Stop the webserver on which GeoNetwork is running (Tomcat or Jetty)

2) Start the database by executing in the command prompt:
     C:\Program Files\geonetwork\web\WEB-INF\db>java -jar ../lib/mckoidb.jar

3) Start Druid:
    - From the "config" menu select "jdbc drivers" and press the "new" button located in the dialog that pops up.
    - Select the "mkjdbc.jar" file inside the web/WEB-INF/lib directory to add it to the system.
    - Do a right click on the left panel (the project view) and select "add database".
    - In the dialog that pops up just press "finish".

At this point, on the right panel you should see a set of tabs.

    - Select "jdbc" and then "connection".


If you want to use mckoi insert: url --> jdbc:mckoi://localhost:9157/

Enter the username and password you selected during the installation of geonetwork for the McKoi database. Now press the "connect" button.

Under the tab "structure" you can explore the database.

Exercise 1: Install and Start the System

This exercise will take you through the installation steps of GeoNetwork opensource and ends with starting the system as stand alone application using Jetty.

Pre-requisites

Before running the GeoNetwork opensource installer you will have to ensure a Java SDK version 1.4.2 or later is installed on your system. You can download that installer from http://java.sun.com. Look for the latest J2SDK1.4 for your operating system.


Starting the GeoNetwork installer

Now start the installer. Normally you can simply double-click on the installer file.
Depending on your computer settings this may not work. In that case, open a terminal window to start the installer from the command-line.

On Windows do: Start -> Run -> type 'cmd' and hit Return. This will open a terminal (MS-DOS) window. Now type 'java -jar C:\temp\geonetwork-2.0.0-beta3-install.jar' followed by a Return.
On UNIX operating systems (Linux, Max OS X, Solaris), open a terminal window and type 'java -jar ~/temp/geonetwork-2.0.0-beta3-install.jar' followed by a Return


Note: replace the directory and installer name with the proper names for your situation

The installer will now display an introduction screen. Click next to select the packages.

You can choose what items to install. At present there are five packages available:

  • GeoNetwork opensource - This is the GeoNetwork web application and is mandatory
  • Sample metadata - These are some sample metadata records that can be used while trying and testing the application. Select it.
  • Integrated Jetty server - The Jetty server allows you to run GeoNetwork opensource as stand alone application without the need to install a separate servlet engine webserver. Select it.
  • Sources - These are the Java source code files. Unless you want to develop or examine the Java source code, there is no need to install them now.
  • JavaDoc - These are the Java source code documentation pages. Again these are not required at this point.
installer_1


Index - Next page



General settings (I)

In the next steps we will go through the general settings. A number of these are not relevant for stand alone installations and will probably be removed from future stand alone installers. However, they are of relevance for server installations, so they will be reviewed while installing.


The items to be filled out are:

  • Organization name
  • Servlet name - This field defines what URL you and your users will use when accessing GeoNetwork through a web browser. Standard this is set to geonetwork. This will result in a URL with the following pattern: http://<your organizations www address>/geonetwork or, on your local computer, running Jetty on the default port 8080, http://<localhost:8080/geonetwork
  • Site ID - The site ID is a unique identifier of your node in the world. It is used by other nodes to reckognize your node while harvesting metadata. For desktop installations this ID is not very relevant as other nodes will not harvest your metadata, but for one of the following exercises we will simulate server installations, so make sure your use something unique.
  • Network address and Network mask - This defines the range of IP numbers used within the organization. It is used by GeoNetwork opensource to distinct Intranet from Internet users. For this exercise the network address and mask are not relevant, so just leave the default values.

Previous page - Index - Next page

General settings (II)

In this section you will now set up the Administrator account of the application.


Define a username and password for the administrator. The password should have a minimum of 6 characters.
The email address will by default be displayed on the homepage and is used for feedback from users. For the stand alone installation the email address is not relevant, just put your own email address

Proceed to the Next page of the installer.

You will now enter details used by GeoNetwork for a database connection. You have the option to install the system with an embedded Database Management System (DBMS) or to use an existing database within the organization.
Currently support for MySQL and Oracle has been provided, but other DBMS's have also been used. The main requirement is for the DBMS to have JDBC driver support. Databases can maunally be configured when needed.
When selecting MySQL or Oracle using the installer, you will need to have that DBMS up and running, have a valid account at hand and have the JDBC driver for the DBMS at hand.

We will now use the embedded DBMS (McKoiDB). Provide a username and password for the database connection and leave the connection URL as is.

Previous page - Index - Next page

General settings (III)

In this section you will now fill out the details of your email server, used to send feedback to the administrator and to data providers. For the stand alone installation this can be set to e.g. localhost on port 25.

The next field defines the port to be used for remote servers to search your node through the Z39.50 protocol search. This is an older, but still much used type of distributed search. On a server installation, allowing other nodes to access your metadata requires you to open the port in the firewall. The ports commonly used for Z39.50 ar 210 or 2100, but other ports could also be used.

We will leave the port to the default value 2100

Click Next to start the installation of the software

You will be prompted to now copy the JDBC driver for your DBMS in its newly created location inside the GeoNetwork opensource directory.

For now, just click OK

This is not required when installing GeoNetwork opensource with the embedded McKoiDB. When using a DBMS like MySQL or Oracle, you will have to copy the respective JDBC driver into the <your installation directory>\web\WEB-INF\lib directory (see figure below).

When the installer completes, you will see a Post installation page. The page explains how to start and stop GeoNetwork opensource and how to configure Tomcat as a servlet engine.
Read the start and stop instructions before proceeding.

As we use the Jetty embedded servlet engine, we do not have to configure Tomcat.

When ready, click Next. We are now at the end of the installation process. Click Finish to end the installation process.

On the next page you will start GeoNetwork opensource.

Previous page - Index - Next page

Finishing the installation process

Last step: Running GeoNetwork through Jetty

To start GeoNetwork opensource, browse to the start up scripts using a file manager.

On Windows, double click on the start-geonetwork.bat file. A terminal window should open, providing log information from Jetty.

On UNIX machines, open a terminal window and cd to the scripts directory.
You can start GeoNetwork by typing ./start-geonetwork.sh followed by a return.


The jetty output will look like this

When the output on the terminal window stops scrolling and you see ... Started org.mortbay.jetty.Server@ ... your system is up and running!

Now open a web browser like Internet Explorer or Firefox and browse to http://localhost:8080/geonetwork , assuming you used default values for the servlet and port and installed on your local computer.
GeoNetwork opensource shoud start and be ready for use. Congratulations!

Previous page - Index


Creative Commons License
This work is licensed under a Creative Commons Attribution-No Derivative Works 3.0 Unported License.

Powered by Plone CMS, the Open Source Content Management System