Page History
...
Wiki Markup Download the eagle-i repository distribution package, {{eagle-i-repository-dist-\[version\].zip}}
- Establish a repository home directory, such as
/opt/eaglei/repo
and set an environment variable${REPO_HOME
}. Unzip the distribution package to this location - Copy
${REPO_HOME}/webapps/ROOT.war
to Tomcat's webapps directory - Configure Tomcat's JAVA_OPTS (in tomcat6.conf or similar):
JAVA_OPTS="-XX:PermSize=64M -XX:MaxPermSize=256M -Xmx1024m"
- Add two system properties to
catalina.properties
:
org.eaglei.repository.home=/opt/eaglei/repo
derby.system.home=/opt/eaglei/repo
- Run the script
${REPO_HOME}/etc/prepare-install.sh
- Edit Create and edit the repository configuration file in
${REPO_HOME}/configuration.properties
- Start up Tomcat
- Run the script
${REPO_HOME}/etc/finish-install.sh
- Run the script
${REPO_HOME}/etc/upgrade.sh
...
- Stop Tomcat
- Establish an eagle-i application home directory and a subdirectory for common application configuration files, e.g.
/opt/eaglei
and/opt/eaglei/conf
. Editcatalina.properties
to reflect these:
org.eaglei.home=/opt/eaglei
common.loader=/opt/eaglei/conf,.....
- Create an "anonymous" repository user with no roles (to be used by the sweet backend services), and a few test users with different roles.
- Download example configuration files
eagle-i-apps.properties
,eagle-i-apps-credentials.properties
,whoami.xml
, place them in the common configuration directory and modify them to reflect your installation Wiki Markup Download {{eagle-i-webapp-sweet-\[version\].war}} into Tomcat's webapps directory and rename to {{sweet.war}}
Wiki Markup Download {{eagle-i-webapp-help-\[version\].war}} into Tomcat's webapps directory and rename {{help.war}}
- Start Tomcat
3.
...
(Optional) Configure search engine access and Google analytics
Wiki Markup |
---|
_For details, see: \[Guide under construction\]__ and __[eaglei:Configuration Property Guide]_ _For configuration sample files, see:_ _[examples|https://open.med.harvard.edu/svn/eagle-i-dev/apps/trunk/examples/config-files]_ _in our code repository_ |
- Create the file
robots.txt
in${CATALINA_HOME}/webapps/ROOT
and edit it to allow search engine crawler access (see examples directory) - Create the file sitemap.xml in
${CATALINA_HOME}/webapps/ROOT
by using the sitemap web service provided by SWEET:
wget -O ${CATALINA_HOME}/webapps/ROOT/sitemap.xml
http://your.host.edu/sweet/sitemap
(It is a good idea to set up a cron job to update the site map periodically.) - Submit this sitemap to the search engines of your choice (for Google, you will need to set up a Google Webmaster account)
- Google analytics: obtain an analytics account and configure your tracker ID in the file
eagle-i-apps.properties
4. (Optional) Install Sparqler
For details, see: Public SPARQL Endpoint Installation Guide and Configuration Property Guide
For software downloads, see: Get Software
For configuration sample files, see: examples in our code repository
- Stop Tomcat
- Copy Copy
${REPO_HOME}/webapps/sparqler.war
to Tomcat's webapps directory - Establish a Sparqler home directory
- , such as
/opt/eaglei/sparqler
and set an environment variable${SPARQLER_HOME
}. - Add the following system property to
catalina.properties
:
org.eaglei.sparqler.home=/opt/eaglei/sparqler
- Run the script
${REPO_HOME}/etc/prepare-install.sh
with an additional argument:sparqler-users.derby
- Edit the repository configuration file in
${SPARQLER_HOME}/configuration.properties
. It should be identical to the repository's except for two lines:
eaglei.repository.sesame.dir=${sys:org.eaglei.sparqler.home}/sesame
eaglei.repository.log.dir=${sys:org.eaglei.sparqler.home}/logs
- Start Tomcat
- Run the script
${REPO_HOME}/etc/finish-install.sh
targeting the newly created /sparqler endpointStart Tomcat
5. (Optional) Install Institutional Search
...
Overview
Content Tools