Versions Compared

Key

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

...

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.

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.

 

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

...