Old Release

This documentation relates to an old version of VIVO, version 1.8.x. Looking for another version? See all documentation.

Skip to end of metadata
Go to start of metadata

 These options can make VIVO more scalable, add features, or run VIVO in a different environment.

Linking user accounts to VIVO profile pages

Configure VIVO so each user can edit their own profile page.

Running VIVO behind an Apache server

Add a reverse proxy, to add a layer of security, allow fine control over your site's URL, and provide a layer for additional network modules.

Using an external authentication system

VIVO can be configured to work with an external authentication system like Shibboleth or CUWebAuth.

Tuning the database connection pool

The number of database connections can affect VIVO's speed.

Using a different data store

VIVO can work with databases like Oracle or SQL Server, or with other types of triple stores.

Developers' installation: obtaining VIVO source code from Git

Some people prefer to work with the very latest source code.

Building VIVO in 3 tiers

Add a third layer to the VIVO distribution, to keep all of your modifications in one place.

Building a VIVO distribution for other servlet containers

Some sites prefer to use a container like GlassFish or JBoss, instead of Tomcat

Activating the ORCID integration

If your site is a member of ORCID, you can activate the ORCID Integration code in VIVO.

Adding OpenSocial gadgets to VIVO

Instructions for connecting VIVO and Open Research Networking Gadgets

VIVO in a language other than English

VIVO can display pages and data in different languages.

Other installation options

An assortment of installation options that aren't necessary for your first installation, but might be helpful later.


  • No labels