Contents

...

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

1. SWEET - Semantic Web Editing and Entry Tool
2. Online help
3. Institutional Search (optional, but useful if your institution will not be indexed by eagle-i's central search)

The eagle-i applications run in a web application containerTomcat server. We assume a container Tomcat is installed and configured to support HTTPS. Container , Tomcat configuration is out of scope for this installation guide. Our reference implementation (used by uses Tomcat 7.

Prerequisites

• Tomcat with the eagle-i

...

• repository installed
  Locate Tomcat's home directory (usually dictated by your OS) and set an environment variable  CATALINA_HOME, for example:

  No Format
  CATALINA_HOME=/opt/tomcat

• An outgoing e-mail server (SMTP) or a Jira server_ _for processing user feedback. 
• Optional: MySQL for search usage logging

Installation Procedure

Initial steps for all applications

1. Create a few repository users
   Log in as an administrator to your eagle-i repository, e.g. if your server is foo.bar.edu, the URL of the repository admin is: https://foo.bar.edu/repository/admin . Navigate to the Manage User Accounts page and create the following users:
   1. an anonymous user with no roles, to be used by the SWEET backend
   2. a sample user with Resource Navigator role (to collect data)
   3. a sample user with Curator role (to curate and publish data)

2. Create eagle-i application home and configuration directory, ${EAGLE_I_HOME}
   Create

General procedure

1. Create common configuration directory

...

1. a directory to place eagle-i application data and configuration files. You may want to reuse part of the path used when installing the eagle-i repository. For example,

...

1. if you installed the repository in /opt/eaglei/repo, 

   No Format
   mkdir /opt/eaglei/conf

2. edit catalina.properties 

...

1. edit catalina.properties
   Open the file ${CATALINA_HOME}/conf/catalina.properties in your favorite text editor.
   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:

...

1. No Format

...

1. common.loader=

...

1. /opt/eaglei/conf,${catalina.base}/lib,...

...

1. Add the definition of the eagle-i home property, where the conf directory was created. This needs to be the full path, without using variables, for example:

...

1. No Format

...

1. org.eaglei.home=/

...

1. opt/

...

1. 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

Property and configuration files

The following three files are necessary to configure the eagle-i applications:

• eagle-i-apps.properties - contains basic properties for all applications 
• eagle-i-apps-credentials.properties - contains various back-end credentials (e.g. optional logging database and Jira feedback). As a good practice, this file should be placed in an access-restricted directory of your server
• local-node.xml - contains Institution-specific configuration

Download the samples for the type of node you're setting up from the examples directory and edit to reflect your environment, see Configuration Property Guide - pre 3.0.x. Place the three files in the configuration directory (defined in step 1 of the the Initial Procedure for all Applications section)

Instructions specific to SWEET

1. Download the SWEET war file from our Software download page (choosing the version you need, usually you will want the latest release) and place in a temporary location, e.g. /tmp. Rename the war to sweet.war and place it in your Tomcat webapps directory:

   No Format
   mv /tmp/eagle-i-webapp-sweet-[version].war ${CATALINA_HOME}/webapps/sweet.war

2. Make sure the property eaglei.datatools.repository.url is set in eagle-i-apps.properties, to reflect the base address of your repository installation. Note that the URL must be an https URL, for example:

   No Format
   eaglei.datatools.repository.url=https://foo.bar.edu

3. Restart
4. 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
5. rename the war to sweet.war and drop in the tomcat webapps directory
6. restart Tomcat

7. SWEET will be available at:

...

1. No Format

...

1. https://

...

1. foo.bar.

...

1. edu/sweet

2. Log in as one of the test users created as part of the Initial Steps for all Applications and explore the SWEET. You can invoke the user help from the link on the top right hand corner.

Instructions specific to Institutional Search

...

(optional)

1. Download the Institutional search war file from our Software download page (choosing the version you need, usually you will want the latest release) and place in a temporary location, e.g. /tmp. Rename the war to institution.war and place it in your Tomcat webapps directory:

   No Format
   mv /tmp/eagle-i-webapp-institution-[version].war ${CATALINA_HOME}/webapps/institution.war

2. Make sure the files eagle-i-apps.properties and  whoami.xml reflect your institution's configuration
3. Optional: set up a database for logging search activity
   1. Create a database named searchlogdb (refer to the MySQL manual)
   2. Uncomment the asynchronous logging properties in  eagle-i-apps.properties and eagle-i-apps-credentials.properties and edit the latter to reflect your database credentials
4. Restart
5. create the following properties files and copy to the common configuration directory:
   • institution-registry.properties - contains the repository credentials for using the harvest service 
   • asynchronousLogger.properties - contains the credentials for database

6. Wiki Markup
   \[instructions to set up solr home directory?\]

7. rename the war to institution.war and drop in the tomcat webapps directory
8. restart Tomcat

9. Institutional search will be available at:

...

1. No Format

...

1. https://

...

1. foo.bar.

...

1. edu/

...

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

1. insitution

2. Log in as one of the test users created in the Initial Steps for all Applications and explore the search application.

Upgrade procedure

To upgrade the SWEET, online help, and institutional search applications, follow these simple steps:

1. Stop Tomcat.

2. Delete the wars from ${CATALINA_HOME}/webapps:

   No Format
   cd ${CATALINA_HOME}/webapps rm -rf sweet* help* institution*

3. Download the desired release of the application wars and copy into ${CATALINA_HOME}/webapps, as described in the installation sections above.
4. Refer to the release notes for possible property files changes (this is uncommon)
5. Start Tomcat.
6. Navigate to the application URLs and verify the updated release number in the footer.

...