-

VIVO Release V1.4 Installation Guide

+

VIVO Release V1.5 Installation Guide

- December 10, 2011 + June 30, 2012

This document is a summary of the VIVO installation process. For information about this release, consult - the VIVO v1.4 Release + the VIVO v1.5 Release Announcement. This and other documentation can be found on the support page at VIVOweb.org. @@ -47,14 +47,16 @@

The VIVO distribution directory

- This is created when you unpack the VIVO distribution file (see Step III, below). This is where you will + This is created when you unpack the VIVO distribution file + (see Step III, below). This is where you will create your deploy.properties file (see Step - IV, below), and where you will make any modifications to the VIVO + IV, below), and where you will make any modifications to the VIVO theme or code. You can create this wherever you choose.

VIVO inside Tomcat

- When you run the build script to compile and deploy VIVO (see Step VI, below), the files will be deployed to a + When you run the build script to compile and deploy VIVO + (see Step VI, below), the files will be deployed to a directory inside Tomcat. This is the actual executing code for VIVO, but you won’t need to look at it or change it. If you need to change VIVO, make the changes in the distribution directory, and run the build @@ -120,7 +122,7 @@ System with VIVO

  • - Using VIVO as an OpenSocial platform + Using VIVO as an OpenSocial platform
  • Was the installation successful? @@ -137,8 +139,11 @@

    @@ -158,36 +163,29 @@ support websites.

    - * Note that vivo does not yet work with Java 1.7 + The following browsers are supported for this release

    -

    - ** Note that from version V1.2 onward VIVO will does - not support older versions of MySQL that - may have worked with 1.1.1. Be sure to use MySQL 5.1 or - higher. Using unsupported versions may result in strange error messages - related to table formatting or other unexpected problems. -

    -

    - *** Note that for this release, the following browsers are supported. -

    -

    - Mac: -

    - -

    - PC: -

    - + +

    II. Create an empty MySQL database

    Decide on a database name, username, and password. Log into your @@ -214,8 +212,8 @@

    - Download the VIVO application source as either rel-1.4.zip - or rel-1.4.gz + Download the VIVO application source as either rel-1.5.zip + or rel-1.5.gz file and unpack it on your web server:
    http://vivoweb.org/download @@ -607,7 +605,7 @@ The number of grants and publications is large.

    • - VIVO V1.4 mitigates this problem by the way of a caching + VIVO V1.4 (and later) mitigates this problem by the way of a caching mechanism and hence we can safely set this to be enabled by default. @@ -675,6 +673,42 @@ + + + Show only the most appropriate data values based on the Accept-Language + header supplied by the browser. Default is true if not set. + + + + + RDFService.languageFilter + + + true + + + + + + These values are used when deploying VIVO as an OpenSocial container + and integrating with OpenSocial gadgets + (see Step XII, 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 + + +   + + +

    V. Compile and deploy

    diff --git a/example.deploy.properties b/example.deploy.properties index a26ce917..ab1ba095 100644 --- a/example.deploy.properties +++ b/example.deploy.properties @@ -198,6 +198,12 @@ Vitro.reconcile.defaultTypeList = http://vivoweb.org/ontology/core#Role, core:Ro # proxy.eligibleTypeList = http://xmlns.com/foaf/0.1/Person, http://xmlns.com/foaf/0.1/Organization +# +# Show only the most appropriate data values based on the Accept-Language +# header supplied by the browser. Default is true if not set. +# +RDFService.languageFilter = true + # # For OpenSocial integration # The base URL of the ORNG Shindig server. Usually, this is the same host and port @@ -225,9 +231,3 @@ proxy.eligibleTypeList = http://xmlns.com/foaf/0.1/Person, http://xmlns.com/foaf # Only set sandbox to True for dev/test environments. Comment out or set to False in production # #OpenSocial.sandbox = True - -# -# Show only the most appropriate data values based on the Accept-Language -# header supplied by the browser. Default is true if not set. -# -RDFService.languageFilter = true