Versions Compared

Old Version 12

changes.mady.by.user Jim Blake

Saved on

compared with

New Version Current

changes.mady.by.user Alvin Hutchinson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Install required software

Before installing VIVO, make sure that the following software should be is installed on your computer:

...

In the previous step, you defined the location of the VIVO home directory, by specifying vitro.home in the build.properties file. If that directory does not exist, create it now.

 

At the command line, from the top level of the VIVO distribution directory, type:

...

The output of the build may include warning messages. The Java compiler may warn of code that is outdated. Unit tests may produce warning messages, and some tests may be ignored if they do not produce consistent results. If the output ends with a success message, these warnings may be ignored.

Running VIVO

Configure Tomcat

Set JVM parameters

Note

What user account owns the VIVO directories?

In many operating systems, the issue of file permissions is important. Who owns the files? Who is authorized to read them, or to write new files?

When running the VIVO build script, it must have permission to read and write to:

  • the VIVO distribution directory
  • the Tomcat webapps directory
  • the VIVO home directory

When VIVO is started under Tomcat, Tomcat must have permission to read and write to:

  • the Tomcat webapps directory
  • the VIVO home directory

There are several ways to make this work. People who are experimenting with VIVO often use their own account to create the VIVO distribution directory, to run the build script, and to run Tomcat.

In more formal environments, it may be necessary to run Tomcat as a service, under its own account. In that case, some people choose to run the build script with root privilege, and then assign the resulting files to Tomcat:

Code Block
sudo ant all
sudo chown -R tomcat /usr/local/vivo/home
sudo chown -R tomcat /usr/local/tomcat/webapps/vivo*

When installing on Microsoft Windows, this is not usually a problem.

Running VIVO

Configure Tomcat

Set JVM parameters

VIVO copies small sections of your RDF database into memory in order to serve VIVO copies small sections of your RDF database into memory in order to serve Web requests quickly (the in-memory copy and the underlying database are kept in synch as edits are performed).

...

Property name

VitroConnection.DataSource.url

Description Specify the JDBC URL of your database. Change the end of the URL to reflect your database name (if it is not "vivovitrodb").
Default valueNONE
Example valuejdbc:mysql://localhost/vivo

...