Skip to content
This repository has been archived by the owner on Oct 18, 2018. It is now read-only.

Installation Prerequisites

vidiecan edited this page Nov 24, 2014 · 1 revision

There are a few important prerequisites which should be prepared or answered before deployment:

Architecture of server/backups

LINDAT/CLARIN server is virtual which can be migrated between two independent servers. It backed up on VM (virtual machine) level, OS level and DSpace level (backups of important directories in DSpace, backups of databases, and replication of AIPs).

OS

We are using Ubuntu LTS version.

Basic Software

  • ant (>= 1.8.0 required)
  • postgresql (required)
  • jdk (>=1.6 required)
  • tomcat (>=6 required)
  • maven (>=3.0)
  • make
  • apache

DSpace dependencies

Handles

  • Additional information: Handle Server, PIDs
  • Required: own prefix, running handle server

DSpace assigns identification strings to objects which resemble the form of specific PIDs (persistent identifiers) namely handles. In order for these ids to become real PIDs, you need to have a correct prefix and a handle server listening for this prefix which will resolve the ids to urls. There are several options how to do it and LINDAT/CLARIN supports obtaining handles from EPIC (API v1/v2) or using DSpace handle server integration (the server will delegate work to DSpace).

In order to obtain your own prefix you should buy (register) a prefix (http://www.handle.net/), follow the instructions specific for DSpace sent by the handle.net, set the prefix in dspace.cfg and start the handle server bundled with DSpace. You can verify the setup by going to http://hdl.handle.net/YOUR-PREFIX/something and checking the log file handle-plugin.log which should contain the request. Your own prefix can be also hosted by EPIC using the APIv2.

Note: Using a shared prefix is very simple but a bad idea in the long run. You cannot migrate your PIDs from one handle server to another if you use a shared prefix (you cannot just take a bunch of PIDs from a prefix).*

Mail server

  • Additional information: SUNScholar
  • Required: running mail server

DSpace relies on a working mail server for sending reports, alerts, verification and exception logs. LINDAT/CLARIN uses mailing-lists for this purpose.

Google Analytics and PIWIK

DSpace has own internal statistics but we extended DSpace with private Google Analytics and PIWIK integration. In order to use it, obtain your own UA string and a developer access (api key file) for GA and auth token with idSite for PIWIK.

We are explicitly tracking OAI-PMH and bitstream downloads for PIWIK.

AAI

  • Additional information: Shibboleth
  • Required: running shibboleth process, part of (at least) national federation and set up the configuration

Authentication is based on Shibboleth, which requires joining federation(s). LINDAT/CLARIN is part of eduID.cz (national federation), eduGAIN (through eduID.cz and following the DP-CoC), SPF. This can take some time and depends on the national federation requirements.

Tomcat / Apache integration

There are several ways how to connect these two, see document above or google :).

HTTPS

  • Additional information: google

If you would like to use https, acquire a certificate and integrate it with apache.

Postgres

  • Additional information: SUNScholar
  • Required: postgreSQL database up and running