We recommend institutional servers be kept up to date with respect to the official software releases, not only to benefit from bug fixes and new features, but also to access additions to the eagle-i ontology such as fulfilled term requests and newly modeled resource types.
Upgrading the software in an eagle-i institutional server requires system administrators to perform a few simple tasks. This checklist is provided as a guide for upgrading the various software components. For details, refer to the linked guides.
For details, see: Repository Installation, Upgrade and Administration Guide > Administrator Tools > make-snapshot.sh script
For details, see: Repository Installation, Upgrade and Administration Guide > Upgrade
For downloads, see: Get Software
${REPO_HOME
} directory and move aside existing etc
, lib
and webapps
directories${REPO_HOME
} directoryROOT
and ROOT.war
from ${CATALINA_HOME}/webapps
${REPO_HOME}/webapps/ROOT.war
into ${CATALINA_HOME}/webapps
${REPO_HOME}/etc/upgrade.sh
Use the guide to determine if a data migration is required.
For details, see: Repository Installation, Upgrade and Administration Guide > Upgrade > Step by Step Upgrade Procedure - step 9
For downloads, see: Get Software
eagle-i-datatools-datamanagement-[version].jar
, rename to eagle-i-datatools-datamanagement.jar
and place in ${REPO_HOME}/etc/
${REPO_HOME}/etc/data-migration.sh
commandFor details, see: SWEET and Institutional Search Installation and Upgrade Guide > Upgrade Procedure
For downloads, see: Get Software
For configuration sample files, see: examples in our code repository
eagle-i-webapp-sweet-[version].jar
, eagle-i-webapp-institution-[version].war
and eagle-i-webapp-help-[version].war
into a temporary locationinstitution.war
, sweet.war
and help.war
and their corresponding directories in ${CATALINA_HOME}/webapps/sweet.war
, institution.war
and help.war
and place in ${CATALINA_HOME}/webapps