Versions Compared

Old Version 5

changes.mady.by.user Jim Blake

Saved on

compared with

New Version 6

changes.mady.by.user Jim Blake

Saved on

Key

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

...

Note
This document applies to VIVO release 1.6. For documents that apply to other releases, please consult the Documentation Archive page.

 

Introduction

This document is a summary of the VIVO installation process. For information about this release, consult the VIVO 1.6 Release Announcement. Links to this and other documentation can be found on the support page at VIVOweb.org.

...

  • Mac:
    • Chrome 30.0.1599.69 and above
    • FireFox 3.6.28, 10.0.12, 24
    • Opera 12.02
    • Safari 5.0.3
  • PC:
    • Chrome 25.1364.2 and above
    • FireFox 10.0.12, 24
    • Internet Explorer 8, 9, 10
    • Opera 12.02

Did it work?

You can test the software installation by typing these commands:

...

Download the VIVO application source as either rel-1.6.zip or rel-1.6.gz file and unpack it on your web server:
http://vivoweb.org/download

Specify build properties

Warning
TBD

At the top level of the VIVO distribution directory, copy the file example.build.properties to a file named simply build.properties. Edit the file to suit your installation, as described in the following table.

...

Compile and deploy

Warning
TBD

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:

Code Block
ant all

to build VIVO and deploy to Tomcat's webapps directory.

The build script may run for as much as five minutes, and creates more than 100 lines of output. The process comprises several steps:

  • collecting the source files from the distribution directory,
  • compiling the Java source code,
  • compiling and running unit tests,
  • preparing the Solr search engine,
  • deploying VIVO and Solr to Tomcat.

Did it work?

The output of the build may include a variety of 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.

BUILD SUCCESSFUL
Total time: 1 minute 49 seconds

If the output ends with a success message, the build was successful. Proceed to the next step.

BUILD FAILED
Total time: 35 seconds

If the output ends with a failure message, the build has failed. Find the cause of the failure, fix the problem, and run the script again.

Running VIVO

Warning
TBD

Configure Tomcat

...

Adding OpenSocial gadgets to VIVO

Warning
TBD
Warning
These values are used when deploying VIVO as an OpenSocial container and integrating with OpenSocial gadgets (see Step 13, below). If you are creating a VIVO installation that does not use OpenSocial gadgets, these values are omitted.
OpenSocial.shindigURL
OpenSocial.tokenService
OpenSocial.tokenKeyFile
OpenSocial.sandbox		 

VIVO in a language other than English

Warning
TBD
Warning
Languages (in addition to American English) that will be built into your VIVO site. The languages must be found in the languages directory of the VIVO distribution. See the VIVO Wiki for more information.
languages.addToBuildes_MX

 

Other installation options

...