Page History

...

You can install and run VIVO on most modern PC, laptop, or server hardware. Whilst the application layer needs a reasonable amount of memory, the majority of the workload is placed on the storage layers, which as a semantic web application means the triple store. As VIVO aims to be agnostic to the triple store, the precise requirements will depend on your choice of triple store. However, starting from the VIVO 1.12, the default configuration is to use Jena TDB, while VIVO can be optionally configured to use Jena SDB backed by MySQL - in this setup, it MySQL as a backing store for Jena SDB. TDB is another triple store from the Jena project, but TDB keeps its data in directory of flat files, while SDB uses a relational database. It is recommended that you have very high IO bandwidth for the file system used by Jena TDB or MySQL, and significant memory for caching layers of the database engine.

Minimum Specification

2 core x64 processor, 2GB RAM, 100GB HDD

...

4 core x64 processor, 16GB RAM, 500GB SSD

Note: If you plan on using the optional Jena SDB database option, I/O performance for MySQL is critical to the responsiveness of the application. The Regardless of chosen database, the fastest SSD you can specify will help, as will having direct (e.g. not virtualised) access to it.

...

Anchor
Java Java

Java 8 or 11

The minimum requirement is Java 8. Both OpenJDK and Oracle JVMs are compatible. Other JVMs that meet the JDK 8 specification may work, but have not been tested.

...

<settings>
  .
  .
  <proxies>
   <proxy>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.somewhere.com</host>
      <port>8080</port>
      <username>proxyuser</username>
      <password>somepassword</password>
      <nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts>
    </proxy>
  </proxies>
  .
  .
</settings>

Anchor

...

Once installed, you only need to create a user and schema - see Installing VIVO. VIVO will create the necessary tables and load the default data on startup.

Alternative databases: Jena SDB supports other databases - including PostgreSQL and Oracle. If you wish to use a different database, you will need to add the appropriate Java libraries to the application, and configure the VitroConnection.DataSource.* settings in runtime.properties so that Jena knows what database it is operating with.

...

Tomcat Tomcat

Tomcat

...

8 or

...

9

VIVO is a web application, which requires a servlet engine to host. It has been tested with Tomcat 7 and Tomcat 88.5, and 9. The applications make use of Tomcat context.xml configuration files - if you wish to use an alternative servlet engine, you will need to make the appropriate adjustments.

You may use Tomcat as supplied by your operating system / package manager providing is meets the minimum requirements, or you can download it from: http://tomcat.apache.org/download-8085.cgi. Note, VIVO does not currently support Tomcat 10+.

Tomcat User: When running, Tomcat is usually launched under an unprivileged user account. As VIVO needs to be able to read and write to the home directory, you must ensure that permissions are set on the home directory correctly. This is most easily achieved by assigning ownership to the user that Tomcat is running as.

Anchor
SQL SQL

Optional - MySQL / MariaDB 5.5 or later (or any other supported by Jena SDB)

VIVO can optionally be configured to use a legacy database called Jena SDB, which requires an SQL database to operate. This may be an attractive option for system administrators familiar with SQL databases, however note that Jena SDB was 'retired' by the Apache Jena project in 2020. 

Once MySQL is installed, you only need to create a user and schema - see Jena SDB and MySQL setup. VIVO will create the necessary tables and load the default data on startup.

Alternative databases: Jena SDB supports other databases - including PostgreSQL and Oracle. If you wish to use a different database, you will need to add the appropriate Java libraries to the application, and configure the VitroConnection.DataSource.* settings in runtime.properties so that Jena knows what database it is operating with.