Date: Thu, 28 Mar 2024 20:48:29 -0400 (EDT) Message-ID: <1117474176.856.1711673309694@prodopencatalystconfluence.catalyst> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_855_477499167.1711673309691" ------=_Part_855_477499167.1711673309691 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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 a=
nd Administration Guide > Platform Requirements
See also=
System Requi=
rements.
${CATA=
LINA_HOME
}=20
eagle-i-apps.properties
)=20
ROOT.war
or ROOT
direc=
tory if it is present in Tomcat's webapps directory
This is a very succinct description that will work in many cases, fo=
r many more details and troubleshooting, see Repo=
sitory Installation, Upgrade and Administration Guide > Install and Conf=
igure Repository
For downloads, see: Get Software
eagle-i-rep=
ository-dist-[version].zip
/opt/eaglei/repo=
code> and set an environment variable ${REPO_HOME
}. Unzip the =
distribution package to this location
${REPO_HOME}/webapps/ROOT.war
to Tomcat's webapps dir=
ectory${R=
EPO_HOME}/lib
to ${CATALINA_HOME}/lib
JAVA_OPTS=3D"-XX:PermSize=3D64M -XX:MaxPermSize=3D256M -Xmx1024m"=
code>
catalina.properties
.org.eaglei.repository.home=3D/opt/eaglei/repo
derby.system=
.home=3D/opt/eaglei/repo
${REPO_HOME}/etc/prepare-install.sh
Special characters are currently not supported in either the username or= password. Using a special character will cause an error. Special character= s include punctuation and symbols.
${REPO_HOME}/default.configuration.properties
=
into a new file ${REPO_HOME}/configuration.properties
an=
d edit it to reflect your installation${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 Instit=
utional Search Installation and Upgrade Guide and =
em>Configurat=
ion Property Guide - pre 3.0.x
For software downloads, see:=
Get Soft=
ware
For configuration sample files, see: exampl=
es in our code repository
/opt/eaglei
and <=
code>/opt/eaglei/conf. Edit catalina.properties
to=
reflect these. Note that catalina.properties
s=
hould already have a common.loader
definition, you o=
nly need to add the eagle-i configuration directory.org.eaglei.ho=
me=3D/opt/eaglei
common.loader=3D/opt/eaglei/conf, ${catali=
na.base}/lib
eagle-i-apps.properties=
, eagle-i-apps-credentials.properties
, whoam=
i.xml
, place them in the common configuration directory and mo=
dify 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 Tomca=
t's webapps directory and rename help.war
Did it work?
The SWEET should be available at https://your.host.edu/sweet=
a>. Create a "Level 4" test user via the repository admin console and log i=
n to the SWEET. Verify that the footer information reflects your installati=
on. Verify that the header links work.
For details, see: Public SPARQL Endpoint Installation Guide&=
nbsp;and Configuration Property Guide - pre 3.0.x
For=
software downloads, see: Get Software
For configuration sample file=
s, see: examples in our code repository=
em>
${REPO_HOME}/webapps/sparqler.war
to Tomcat's we=
bapps directory/opt/eaglei/sparqler=
and set an environment variable ${SPARQLER_HOME}.
catalina.properties
:<=
br>org.eaglei.sparqler.home=3D/opt/eaglei/sparqler
${REPO_HOME}/etc/prepare-install.sh
w=
ith an additional argument: sparqler-users.derby
${SPARQLER_HOME}/c=
onfiguration.properties
. It should be identical to the repository's =
except for two lines:eaglei.repository.sesame.dir=3D${sys:org.eag=
lei.sparqler.home}/sesame
eaglei.repository.log.dir=3D${sys=
:org.eaglei.sparqler.home}/logs
${REPO_HOME}/etc/finish-install.sh
tar=
geting the newly created /sparqler endpoint
Did it work?
The Sparqler query workbench should be available at http://y=
our.host.edu/sparqler and should have no access restrictions. Execute t=
he following SPARQL query: select * where {?s ?p ?o
} with=
Default Graph =3D NG_Published. You should see the public triples of =
your main repository.
For details, see: [Guide under construction] and&=
nbsp;Con=
figuration Property Guide - pre 3.0.x
For sample files, see=
: examples in our code repository
robots.txt
in ${CATAL=
INA_HOME}/webapps/ROOT
and edit it to allow search engine craw=
ler access (see examples directory)${CATALINA_HOME}/webapps/ROOT=
by using the sitemap web service provided by SWEET:w=
get -O ${CATALINA_HOME}/webapps/ROOT/sitemap.xml
http://foo.bar.edu/sweet/sitemap
eagle-i-apps.properties
For details, see: SWEET and Instit=
utional Search Installation and Upgrade Guide an=
d C=
onfiguration Property Guide - pre 3.0.x
For software downlo=
ads, see: Get Software
For configuration sample files, see:&nbs=
p;examples in our code repository
eagle-i-apps.properties
, eagl=
e-i-apps-credentials.properties
and whoami.xml
to reflect your installationeagle-i-webapp-institution-[version].war
&nbs=
p;into Tomcat's webapps directory and rename to institution.war<=
/code>
Did it work?
Institutional Search should be available at h=
ttps://your.host.edu/institution. Verify that the footer informat=
ion reflects your installation. Verify that the header links work.