This quick start guide is intended as a reference for the steps necessary to install an eagle-i node (institutional server). For detailed instructions, please refer to the linked guides.
For details, see Repository Installation, Upgrade and Administration Guide > Platform Requirements
See also System Requirements.
${CATALINA_HOME
}
eagle-i-apps.properties
)
ROOT.war
or ROOT
directory if it is present in Tomcat's webapps directoryFor details, see Repository Installation, Upgrade and Administration Guide > Install and Configure Repository
For downloads, see: Get Software
eagle-i-repository-dist-[version].zip
/opt/eaglei/repo
and set an environment variable ${REPO_HOME
}. Unzip the distribution package to this location${REPO_HOME}/webapps/ROOT.war
to Tomcat's webapps directoryJAVA_OPTS="-XX:PermSize=64M -XX:MaxPermSize=256M -Xmx1024m"
catalina.properties
:org.eaglei.repository.home=/opt/eaglei/repo
derby.system.home=/opt/eaglei/repo
${REPO_HOME}/etc/prepare-install.sh
${REPO_HOME}/configuration.properties
${REPO_HOME}/etc/finish-install.sh
${REPO_HOME}/etc/upgrade.sh
Did it work?
The repository admin console should be available at https://your.host.edu/repository/admin. Log in with your newly created admin user. Verify that the version information reflects your installation.
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
/opt/eaglei
and /opt/eaglei/conf
. Edit catalina.properties
to reflect these:org.eaglei.home=/opt/eaglei
common.loader=/opt/eaglei/conf,.....
eagle-i-apps.properties
, eagle-i-apps-credentials.properties
, whoami.xml
, place them in the common configuration directory and modify them to reflect your installationeagle-i-webapp-sweet-[version].war
into Tomcat's webapps directory and rename to sweet.war
eagle-i-webapp-help-[version].war
into Tomcat's webapps directory and rename help.war
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.
For details, see: [Guide under construction] and Configuration Property Guide - pre 2.0MS3.x
For sample files, see: examples in our code repository
robots.txt
in ${CATALINA_HOME}/webapps/ROOT
and edit it to allow search engine crawler access (see examples directory)${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
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
${REPO_HOME}/webapps/sparqler.war
to Tomcat's webapps directory/opt/eaglei/sparqler
and set an environment variable ${SPARQLER_HOME
}.catalina.properties
:org.eaglei.sparqler.home=/opt/eaglei/sparqler
${REPO_HOME}/etc/prepare-install.sh
with an additional argument: sparqler-users.derby
${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
${REPO_HOME}/etc/finish-install.sh
targeting the newly created /sparqler endpointDid it work?
The Sparqler query workbench should be available at http://your.host.edu/sparqler and should have no access restrictions. Execute the following SPARQL query: select * where {?s ?p ?o
} with Default Graph = NG_Published. You should see the public triples of your main 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
eagle-i-apps.properties
, eagle-i-apps-credentials.properties
and whoami.xml
to reflect your installationeagle-i-webapp-institution-[version].war
into Tomcat's webapps directory and rename to institution.war
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.