Page History
...
- Install and configure the Tomcat web application server to
${CATALINA_HOME
}- Configure Tomcat to use SSL
- Purchase and install an SSL server certificate (for testing purposes it is possible to use a self-signed certificate; a property to this effect can be set in the file
eagle-i-apps.properties
)- Make sure your certificate is properly installed by using an SSL checker, e.g. http://www.geocerts.com/ssl_checker
- Set up the networking configuration such that Tomcat responds on standard ports 80 and 443
- Move aside the default
ROOT.war
orROOT
directory if it is present in Tomcat's webapps directory - Secure access to an outgoing mail server (SMPTSMTP). This can be co-located and accessed via localhost (e.g. postfix), or can be a remote server accessed over https.
1. Install the eagle-i repository
For detailsThis is a very succinct description that will work in many cases, for many more details and troubleshooting, see Repository Installation, Upgrade and Administration Guide > Install and Configure Repository
For downloads, see: Get Software
- 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 - If Tomcat doesn't already have them, copy the 2 derby jars in
${REPO_HOME}/lib
to${CATALINA_HOME}/lib
- 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 Copy the file
${REPO_HOME}/default.configuration.properties
into a new file${REPO_HOME}/configuration.properties
and edit it to reflect your installation - Start Tomcat
- Run the script
${REPO_HOME}/etc/finish-install.sh
- Run the script
${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.
2. Install SWEET and Online Help
...
- 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
eagle-i-webapp-sweet-[version].war
into Tomcat's webapps directory and rename tosweet.war
- Download
eagle-i-webapp-help-[version].war
into Tomcat's webapps directory 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
...
For details, see: [Guide under construction] and Configuration Property Guide - pre 3.0.x
For sample files, see: examples in our code repository
...
.
...
Install Sparqler
For details, see: Public SPARQL Endpoint Installation Guide and Configuration Property Guide - pre 3.0.x
For software downloads, see: Get Software
For configuration sample files, see: examples in our code repository
- Stop Tomcat
- 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 endpoint
Did 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.
4. (Optional) Configure search engine access and Google analytics
For details, see: [Guide under construction] and Configuration Property Guide - pre 3.0.x
For sample files, see: 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
5. (Optional) Install Institutional Search
...
- 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
eagle-i-webapp-institution-[version].war
into Tomcat's webapps directory and 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.