VIVO Documentation
Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
...
| Code Block | ||
|---|---|---|
| ||
$ cd VIVO VIVO$ mvn install -s default-settings.xml [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Vitro [INFO] Vitro Dependencies [INFO] Vitro API [INFO] VIVO [INFO] VIVO API [INFO] Vitro Web App [INFO] VIVO Web App [INFO] Vitro Home [INFO] VIVO Home [INFO] Vitro Solr App [INFO] VIVO Installer [INFO] VIVO Prepare Home [INFO] VIVO Prepare Solr App [INFO] VIVO Prepare Web App [INFO] .... |
At this point, the
Completing The Installation
The VIVO home directory will now be created, the VIVO application installed to Tomcat.
In order to run VIVO, please read the section below "Completing the Installation".
| Anchor | ||||
|---|---|---|---|---|
|
...
The VIVO home directory will now be created, the VIVO application installed to Tomcat.
In order to run VIVO, please read the section below "Completing the Installation".
| Panel | |||||
|---|---|---|---|---|---|
Custom InstallerIf you want to use the source code / GitHub clone with your own customisations, you can exclude the supplied installer project, and use your own customized installer project instead. To do so, you need to supply the location of your custom installer project as the "vivo-installer-dir" property. This can be done on the command line, or in the settings.xml. If you are supplying a relative path, it should be relative to the location of the VIVO/pom.xml.
The VIVO home directory will now be created, the VIVO application installed to Tomcat, including any customizations that are defined in your local installer project. |
| Anchor | ||||
|---|---|---|---|---|
|
Configure the Database Schema
The default configuration of VIVO is to use MySQL as a backing store for Jena SDB. Whilst VIVO / Jena will create the necessary tables for the triple store, a database (schema) and authentication details need to have been created first. To do so, log in to MySQL as a superuser (e.g. root)
| Code Block | ||
|---|---|---|
| ||
$ mysql -u root -p
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.7.9 MySQL Community Server (GPL)
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> CREATE DATABASE vivodb CHARACTER SET utf8;
mysql> GRANT ALL ON vivodb.* TO 'vitrodbUsername'@'localhost' IDENTIFIED BY 'vitrodbPassword'; |
Configure the Home Directory
There are two configuration that are required to be in the home directory. By default, the installer does not create them, so that they are not overwritten when you redeploy the application. Instead, example files are created in the home directory, which can be copied and used as the basis for your installation.
| Code Block | ||
|---|---|---|
| ||
$ cd /usr/local/vivo/home
/usr/local/vivo/home$ cp example.runtime.properties runtime.properties
/usr/local/vivo/home$ cd config
/usr/local/vivo/home/config$ cp example.applicationSetup.n3 applicationSetup.n3 |
| Note | |||||
|---|---|---|---|---|---|
| |||||
In order for your installation to work, you will need to edit the runtime.properties, and ensure that the VitroConnection properties are correct for your database engine. They should look something like this.
|
Configure and Start Tomcat
Overview
Content Tools