Overview

Upgrading If you are already running VIVO 1.11.x, you can upgrade to VIVO 1.10 requires upgrading your triple stores (content and configuration).  A procedure is provided below.  You should consider:

...

12.x without making any configuration or data changes.  Follow the procedure in Installing VIVO while using your existing installation settings (installation.xml).  If you have customized your VIVO 1.11 installation, you will need to take action to preserve those customizations. 

...

...

...

Changes to runtime.properties

Location

Enabling additional languages

After upgrading to For VIVO 1.10, the preferred location of runtime.properties has changed from the <vivo_home> directory to <vivo_home>/config. VIVO will raise a warning on startup if runtime.properties is found in <vivo_home> or both <vivo_home> and <vivo_home>/config. Continue startup by refreshing or clicking continue. Move runtime.properties into the config directory to avoid the warning. Note, jenatools expects to find runtime.properties in <vivo_home>.

Password hashing settings

VIVO 1.10 includes security enhancements to the way passwords are stored in VIVO. Three new settings are now required in runtime.properties. Add the following to an older version of runtime.settings (default settings shown):

argon2.parallelism = 1
argon2.memory = 1024
argon2.time = 1000

For a full explanation of the new settings, see example.runtime.properties.

Upgrading The Triple Stores

Upgrading the triple stores (there are two - content and configuration) involves dumping the contents of your stores, and then reloading them, using tools provided with VIVO.

In order to upgrade your triple stores, use the following steps (replace <your-settings.xml> and <vivo_home> with the appropriate values for your system.

...

To export your triple stores, use the jena2tools utility provided with VIVO 1.10.0, in <vivo home dir>/bin, specifying the export command, as shown below.

java -jar jena2tools.jar -e -d <vivo_home>

Arguments:

-d - the location of the Vitro/VIVO home directory

-e - run in export mode

On execution, the program will read your configuration files, find your VIVO configuration within the vivo home directory, and get the necessary information to connect to your configuration triple store, and your content triple store. If your triple store(s) are not SDB or TDB backed, they will be skipped.

jena2tools will then extract the contents of the triple stores, and write them to <vivo_home>/dumps

...

Drop your database and recreate it as empty, just as you would for creating a new VIVO install.  jena3tools must find an empty database (no tables) as named in your runtime.properties and will recreate your content triple store using the triples produced by jena2tools

mysql> DROP DATABASE vitrodb;
mysql> CREATE DATABASE vitrodb CHARACTER SET utf8;
mysql> GRANT ALL ON vitrodb.* TO 'vitrodbUsername'@'localhost' IDENTIFIED BY 'vitrodbPassword';

Delete all files in <vivo_home>/tdbModels.  Jena3tools will rebuild your configuration tdbModels based on the content created by jena2tools

rm -rf <vivo_home>/tdbModels

...

Having exported your triple stores, you can reload them using jena3tools, also available with VIVO 1.10, specifying the import command.

java -jar jena3tools.jar -i -d <vivo_home>

Arguments:

-d - the location of the Vitro/VIVO home directory

-i - run in import mode

On execution, the program will find your VIVO configuration within the home directory, as well as the dumps that you have created with jena2tools. It will import them into the SDB and TDB triple stores, based on the configuration of your VIVO instance.

jena3tools will be present in <vivo home dir>/bin when you install the 1.10.

...

12, additional interface languages may be added at any time by editing runtime.properties and restarting Tomcat.  See How to Enable Languages in VIVO as an Administrator for more information.