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.
General procedure
- Tweak Tomcat configuration.
- create a directory to place application property files
- tell Tomcat to include this directory in the classpath
- tell Tomcat where the eagle-i home is
- example with catalina.properties
- Create configuration file for each application and place in the configured directory
- Examples for all configuration files are located in the examples directory of the code trunk
- [do we need to include an example with the war?]
- Rename the application war file as desired and drop in the app server webapps directory
- example
- All the apps assume https [shall we include installation for plain http?]
Instructions specific to SWEET
- create the file datatools.properties and copy to
* this file contains the URL of the repository where data will be entered* rename the war to sweet.war and drop in
${tomcat_home}/conf/eaglei
${tomcat_home}/webapps
- restart Tomcat
- SWEET will be available at:
Instructions specific to Institutional Search
- create the following properties files and copy to $
Unknown macro: {tomcat_home}/webapps
/conf/eaglei
-
- institution-registry.properties - contains the repository credentials for using the harvest service
- asynchronousLogger.properties - contains the credentials for database
- [instructions to set up solr home directory]
- rename the war to institution.war and drop in $
-
- restart Tomcat
- Institutional search will be available at:
Instructions specific to the ontology browser
- rename the war to model.war and drop in $
Unknown macro: {tomcat_home}/webapps
- restart Tomcat
- The ontology browser will be available at:
Instructions specific to the monitor
Instructions specific to the identity service
Overview
Content Tools