Contents

Once you have an eagle-i repository to talk to (see repository installation and administration guide), installing the rest of the eagle-i suite applications is relatively straightforward.

The eagle-i applications run in a web application container. We assume a container is installed and configured to support HTTPS. Container configuration is out of scope for this installation guide.

Our reference implementation (used by the eagle-i Consortium) uses Tomcat 6.This installation guide references Tomcat file names and property files in its examples; equivalent details for other application containers are out of scope.

Prerequisites

Tomcat with eagle-i repository

Optional: MySQL for search usage logging

General procedure

1. Create common configuration directory

create a directory to place eagle-i application configuration files. For example,

/usr/share/tomcat6/eaglei/conf

2. edit catalina.properties 

add the eagle-i configuration directory to the common class loader. Note that catalina.properties should already have a common.loader definition, you only need to add the eagle-i configuration directory, for example:

common.loader=${catalina.base}/eaglei/conf,${catalina.base}/lib,...

add the definition of the eagle-i home property. This needs to be the full path, without using variables, for example:

org.eaglei.home=/usr/share/tomcat6/eaglei/

3. Create application configuration files and place in the configuration directory. 

Examples for all configuration files are located in the examples directory of the code trunk

4. Rename the application war file as indicated in specific instructions and drop in the webapps directory

Instructions specific to SWEET

1. create the file datatools.properties (see examples directory) and copy to the common configuration directory.  This file contains the URL of the repository where data will be entered
2. rename the war to sweet.war and drop in the tomcat webapps directory
3. restart Tomcat
4. SWEET will be available at:

https://your.server/sweet

Instructions specific to Institutional Search

1. create the following properties files and copy to the common configuration directory:
   • institution-registry.properties - contains the repository credentials for using the harvest service 
   • asynclogger.properties - contains the credentials for search usage database

2. \[instructions to set up logging database\]

3. \[instructions to set up solr home directory\]

4. rename the war to institution.war and drop in the tomcat webapps directory
5. restart Tomcat
6. Institutional search will be available at:

https://your.server/institution

Instructions specific to the ontology browser

• rename the war to model.war and drop in the tomcat webapps directory
• restart Tomcat
• The ontology browser will be available at:

https://your.server/model

Instructions specific to the monitor

Instructions specific to the identity service