...
For details, see Repository Installation, Upgrade and Administration Guide > Install and Configure Repository
For downloads, see: Get Software
Download the eagle-i repository distribution package, {{Wiki Markup 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
- Create and edit the repository configuration file in
${REPO_HOME}/configuration.properties
- Start Tomcat
- Run the script
${REPO_HOME}/etc/finish-install.sh
- Run the script
${REPO_HOME}/etc/upgrade.sh
...
For details, see: SWEET and Institutional Search Installation and Upgrade Guide and Configuration Property Guide - pre 2.0MS3.x
For software downloads, see: Get Software
For configuration sample files, see: examples in our code repository
- In the repository admin console, create an "anonymous-ext" repository user with no roles (to be used by the sweet backend services), and a few test users with different roles.
- 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,.....
- 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 Download {{Wiki Markup eagle-i-webapp-sweet-
\[version
\].war
}} into Tomcat's webapps directory and rename to {{rename tosweet.war
}}Wiki Markup - Download {{
eagle-i-webapp-help-
\[version
\].war
}} into into Tomcat's webapps directory and rename {{and renamehelp.war
}} - Start Tomcat
Did it work?
The SWEET should be available at https://your.host.edu/sweet. Create a "Level 4" test user via the repository admin console and log in to the SWEET. Verify that the footer information reflects your installation. Verify that the header links work.
...
3. (Optional) Configure search engine access and Google analytics
_For details, see: \ [Guide under construction\]__ and __[eaglei:Configuration Property Guide - pre ] and Configuration Property Guide - pre 2.0MS3.x]_
_ Wiki Markup
For sample files, see:_ _[examples|https://open.med.harvard.edu/svn/eagle-i-dev/apps/trunk/examples/config-files]_ _in our code repository_ examples 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://foo.bar.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
...
For details, see: Public SPARQL Endpoint Installation Guide and Configuration Property Guide - pre 2.0MS3.x
For software downloads, see: Get Software
For configuration sample files, see: examples in our code repository
...
For details, see: SWEET and Institutional Search Installation and Upgrade Guide and Configuration Property Guide - pre 2.0MS3.x
For software downloads, see: Get Software
For configuration sample files, see: examples in our code repository
- Stop Tomcat
- Modify files
eagle-i-apps.properties
,eagle-i-apps-credentials.properties
andwhoami.xml
to reflect your installation - (optional) install a MySQL database for search usage logging and configure its name and credentials in the two property files above (the tables will be created upon first access by the application)
Download {{DownloadWiki Markup eagle-i-webapp-institution-
\[version
\].war
}} into into Tomcat's webapps directory and rename to {{rename toinstitution.war
}}- Start Tomcat
Did it work?
Institutional Search should be available at https://your.host.edu/institution. Verify that the footer information reflects your installation. Verify that the header links work.