Requirements
- Postgres database with Postgis extension
- Tomcat 6
- Java 1.7 (Tested with Java version "1.7.0_45")
Configuring the Geonetwork 3 sources
To make Geonetwork 3 use the Postgres configuration (Tested with 9.3) the following has to be changed in the "web/src/main/webapp/" directory:
- WEB-INF\config-node\srv.xml --> Change to: <import resource="../config-db/jndi-postgres-postgis.xml"/>
- WEB-INF\config-db\jdbc.properties --> Fill in the database host, username and password
Geonetwork uses stopwords to create indexes and to filter them from queries. This leads to unexpected results if a user uses the english user interface and types a dutch query. For example the query "het water" wil be interpreted as an english query. The stopword "het" won't be removed from the query. During indexing dutch documents the stop words will be removed, so only "water" is stored in the index. So searching for "het water" will not find any results.
To work around this issue, the english and dutch stop words have been merged:
webapp/resources/stopwords
- eng.txt
- dut.txt
Tomcat 6 Configuration
To store indexes and other Geonetwork specific data, pass a java environment data directory to tomcat.
"-Dgeonetwork.dir=/var/lib/geonetwork_data"
To make sure tomcat has enough memory available, use the following java parameters:
"-Dfile.encoding=UTF-8 -Xms128m -Xmx712m -XX:PermSize=128m -XX:MaxPermSize=128m"
On CentOS these settings can be set in the /usr/share/tomcat6/conf/tomcat6.conf file.
- JAVA_OPTS="-Dgeonetwork.dir=/var/lib/geonetwork_data -Dfile.encoding=UTF-8 -Xms128m -Xmx712m -XX:PermSize=128m -XX:MaxPermSize=128m"
On windows the JAVA_OPTS can be added to the sentenv.bat file in the tomcat bin directory.
