Page History

...

mv /tmp/repository-1.1-MS1.00-SNAPSHOT/\* ${REPO_HOME}/.

List the contents of the home directory:

...

cp ${REPO_HOME}/lib/derby-\* ${CATALINA_HOME}/lib/

Step 7. (OPTIONAL) Choose alternate Apache Derby implementation

...

1. Navigate to Tomcat's webapps directory. If there exist a directory named ROOT, move it aside. The eagle-i repository must be the ROOT application

   Code Block
   cd ${CATALINA_HOME}/webapps mv ROOT ROOT.original

2. Copy the repository webapp to the Tomcat webapps directory:

   Code Block
   cp ${REPO_HOME}/webapps/ROOT.war ${CATALINA_HOME}/webapps/.

3. Create your initial administrative user login. Think of a USERNAME and PASSWORD and substitute them for the upper case words in this command:

   Code Block
   bash ${REPO_HOME}/etc/prepare-install.sh USERNAME PASSWORD ${REPO_HOME}

4. Start up Tomcat.
5. Run the finish-install script, which loads the data model ontology among other things. Note that you can also give it additional options to specify a personal name and email box for the initial admin user.

   Code Block
   bash ${REPO_HOME}/etc/finish-install.sh USERNAME PASSWORD https://localhost:8443

   ...or, with username metadata included:

   Code Block
   bash ${REPO_HOME}/etc/finish-install.sh \ \-f firstname \ \-l lastname \ \-m admin@ei.edu \ USERNAME PASSWORD https://localhost:8443

6. Run the upgrade.sh script, which preforms additional configurations.

   Code Block
   bash ${REPO_HOME}/etc/upgrade.sh USERNAME PASSWORD https://localhost:8443

7. Edit the file configuration.properties located in {${REPO_HOME} to reflect your installation. See the Configuration Reference #Configuration section below for details on the property definitions and expected values.
8. Restart Tomcat to pick up these configuration changes. Confirm that the eagle-i repository is running by visiting the admin page (login with USERNAME and PASSWORD):

   Code Block
   https://localhost:8443/repository/admin

...

1. Unpack the distribution Zip archive in a directory e.g. under /tmp:

   Code Block
   cd /tmp unzip repository-dist.zip

2. Shut down your Tomcat java servlet container.
3. Delete the old repo webapp subdirectory and WAR file, since there should not be any local modifcations there. For example:

   Code Block
   rm \-rf ${CATALINA_HOME}/webapps/ROOT\*

4. Save the current release files in case you have to roll back:

   Code Block
   cd ${REPO_HOME} mv etc etc.old mv lib lib.old mv webapps webapps.old

5. Copy the distribution into place (in this example the distribution is version 1.7-MS1.01) -- note there are 2 steps:

   Code Block
   cp \-f \-rp /tmp/repository-1.7-MS1.01/\* ${REPO_HOME} cp ${REPO_HOME}/webapps/ROOT.war ${CATALINA_HOME}/webapps/.

6. Start up your tomcat java servlet container.
7. Run the upgrade script, substituting your admin's username and password:

   Code Block
   bash ${REPO_HOME}/etc/upgrade.sh USERNAME PASSWORD https://localhost:8443

   Watch the output of upgrade.sh very carefully! Pay particular attention to the final status and any messages beginning "WARN", they will indicate problems you MUST resolve.
8. Confirm that it worked: visit the repo admin page, check for new version, and then follow the link to Show Data Model Ontology versions to confirm that "loaded" and "available" versions of the ontology are the same.When running the upgrade script, there may be messages about out-of-date NG_Internal and NG_Query graphs. Most likely, these are nothing to worry about -- check the release notes. These graphs are only initialized from static files when the repository was created, and afterward they accumulate statements, so reloading a new copy of the original data is not practical. Some releases may include instructions for making changes in these graphs when upgrading from previous versions.
9. Download the data migration toolkit that corresponds to your repository version (in this example, version 1.7-MS1.02) and run the data migration script, substituting your admin's username and password:

   Code Block
   wget wget -O ${REPO_HOME}/etc/eagle-i-datatools-datamanagement.jar http://infra.search.eagle-i.net:8081/nexus/content/repositories/releases/org/eagle-i/eagle-i-datatools-datamanagement/1.7-MS1.02/eagle-i-datatools-datamanagement-1.7-MS1.02.jar bash ${REPO_HOME}/etc/data-migration.sh USERNAME PASSWORD https://localhost:8443

   Watch the output of data-migration.sh very carefully! Pay particular attention to the final status and any messages beginning "WARN", they will indicate problems you MUST resolve. In addition to the output on screen, the data-migration script will place a data migration report in the logs directory directly under /etc.

...