Page History
Contents
| Table of 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
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:
| Code Block |
|---|
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:
| Code Block |
|---|
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
- 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
- rename the war to sweet.war and drop in the tomcat webapps directory
- restart Tomcat
- SWEET will be available at:
| Code Block |
|---|
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 ** {color:#ff0000}\[do we need to include an example with the war?\]{color} * Rename the application war file as desired and drop in the app server webapps directory ** example * All the apps assume https {color:#ff0000}\[shall we include installation for plain http?\]{color} h1. Instructions specific to SWEET * create the file datatools.properties and copy to {noformat} ${tomcat_home}/conf/eaglei {noformat}* this file contains the URL of the repository where data will be entered* rename the war to sweet.war and drop in {noformat} ${tomcat_home}/webapps {noformat} * restart Tomcat * SWEET will be available at: ** [https://your.server/sweet] h1. |
Instructions
...
specific
...
to
...
Institutional
...
Search
...
- 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
Wiki Markup \[instructions to set up solr home directory?\]
...
- rename the war to institution.war
...
- and
...
- drop in the tomcat webapps directory
- restart Tomcat
- Institutional search will be available at:
| Code Block |
|---|
in ${tomcat_home}/webapps * restart Tomcat * Institutional search will be available at: ** [https://your.server/institution] h1. |
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:
| Code Block |
|---|
drop in ${tomcat_home}/webapps * restart Tomcat * The ontology browser will be available at: ** [https://your.server/model] h3. |
Instructions
...
specific
...
to
...
the
...
monitor
...
Instructions
...
specific
...
to
...
the
...
identity
...
service
...
Overview
Content Tools