3.1 Symbols

4.1 Hardware requirements

Server load is difficult to predict, therefore live testing remains the best way to determine what hardware the ISO Registry instance will require in production. The values given below refer to the minimum available hardware to run the ISO Registry instance with five concurrent users.

• 2 GHz+ CPU

• 2048 MB RAM

• 10 GB database space

4.2 System requirements

Table 1

4.3 Skill requirements

This document assumes that you:

• are familiar with administrating Linux systems

• have root access to the server used for installation

5.1 Prerequisites

The steps in this section depend on the following assumptions.

• The following components have been installed on the server:

  • OpenJDK 7 or Oracle JDK/JRE 7

  • Apache Tomcat 7.0.x

• The server can connect to a PostgreSQL instance and:

  • the database <dbname> for the ISO Registry was created

  • the database user <dbuser> with password <dbpassword> exists and has full rights on the <dbname> database

• The server can connect to an SMTP server that will deliver mails sent by the registry software.

The commands shown work on servers running Ubuntu LTS 14.04 (and possibly later Ubuntu versions). In case your server runs a different distribution you must modify the commands to fit that platform.

5.2 Steps

1. Load the database dump iso-gcp-minimal.backup into the isoreg database (for example, through PgAdmin).
   

   The dump contains a minimal version of the ISO Registry of Geodetic Codes and Parameters, including example users. For further details, see configuration.

2. Copy the web archive iso-registry-client.war to <Tomcat7>/webapps, the directory that contains Tomcat’s webapps (e.g. /var/lib/tomcat7/webapps).

3. Apache Tomcat should unpack the web archive to the sub-directory iso-registry-client.

4. Stop Apache Tomcat
   

   service tomcat7 stop

5. Change to the directory iso-registry-client/WEB-INF/classes and edit the following configuration files:
   

   • registry.configuration.xml

   • client.configuration.xml

   • hibernate.connection.xml and

   • hibernate.properties.xml.

   For a list of all configuration settings, see section 1.6.

6. Start Apache Tomcat +

   service tomcat7 start

7. To access the ISO Registry of Geodetic Codes and Parameters, open a browser and navigate to http:// server URL>/iso-registry-client. For example, with Tomcat running on port 8080 on localhost, the URL would be http://localhost:8080/iso-registry-client. == Configuration

5.3 Database connection (hibernate.connection.xml)

hibernate.connection.username

<dbuser>

hibernate.connection.password

<dbpassword>

hibernate.connection.url

jdbc:postgresql://<dbhost>:<dbport>/isoreg

5.4 Database parameters (hibernate.properties.xml)

hibernate.hbm2ddl.auto

• validate – for standard production use

• update – when performing a software update

• create – when installing for the time

5.5 Registry configuration (registry.configuration.xml)

mail.enabled

• true – mail sending is enabled

• false – mail sending is disabled

mail.from.name

Mail name used in From header

mail.from.address

E-mail address used in From header

mail.smtp.auth

Switch to activate SMTP authentication (true, false)

mail.smtp.starttls.enable

Switch to activate STARTTLS SMTP authentication (true, false)

mail.smtp.host

Host name or IP address of SMTP server

mail.smtp.port

Port number of SMTP server (TLS: 587, plain: 25)

mail.smtp.user

User name used for SMTP authentication

mail.smtp.password

Password used for SMTP authentication (plain text)

5.6 Registry client configuration (client.configuration.xml)

basePath

If you run Apache Tomcat behind a reverse proxy this parameters must be set to the context path used by external clients, preceded by a tilde.

If e.g. the registry is accessed from the outside via the URL http://registry.isotc211.org/gcp the parameter must be set to ~/gcp.

In environments without a reverse proxy this parameters must be left empty.