NIHVIVO-3844 Update install.html to reflect changes in 1.5

This commit is contained in:
j2blake 2012-06-29 17:56:49 +00:00
parent 056b17d77a
commit e5d67b4bde
2 changed files with 83 additions and 49 deletions

View file

@ -3,7 +3,7 @@
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="utf-8">
<title>VIVO Release V1.4 Installation Guide</title>
<title>VIVO Release V1.5 Installation Guide</title>
<link rel="stylesheet" href="./css/doc.css" media="screen">
</head>
<body>
@ -12,15 +12,15 @@
</div>
<!-- Start of content -->
<div id="wrapper-content" role="main">
<h1>VIVO Release V1.4 Installation Guide</h1>
<h1>VIVO Release V1.5 Installation Guide</h1>
<div>
December 10, 2011
June 30, 2012
</div>
<p>
This document is a summary of the VIVO installation
process. For information about this release, consult
the <a href="release.html">VIVO v1.4 Release
the <a href="release.html">VIVO v1.5 Release
Announcement</a>. This and other documentation can be found on
the <a href="http://vivoweb.org/support">support
page</a> at <a href="http://vivoweb.org">VIVOweb.org</a>.
@ -47,14 +47,16 @@
</p>
<h4>The VIVO distribution directory</h4>
<p>
This is created when you unpack the VIVO distribution file (see <a href="#download_code">Step III</a>, below). This is where you will
This is created when you unpack the VIVO distribution file
(see <a href="#download_code">Step III</a>, below). This is where you will
create your deploy.properties file (see <a href="#deploy_properties">Step
IV</a>, below), and where you will make any modifications to the VIVO
IV</a>, below), and where you will make any modifications to the VIVO
theme or code. You can create this wherever you choose.
</p>
<h4>VIVO inside Tomcat</h4>
<p>
When you run the build script to compile and deploy VIVO (see <a href="#deploy">Step VI</a>, below), the files will be deployed to a
When you run the build script to compile and deploy VIVO
(see <a href="#deploy">Step VI</a>, below), the files will be deployed to a
directory inside Tomcat. This is the actual executing code for VIVO,
but you wont 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</a>
</li>
<li>
<a href="opensocial">Using VIVO as an OpenSocial platform</a>
<a href="#opensocial">Using VIVO as an OpenSocial platform</a>
</li>
<li>
<a href="#installation_check">Was the installation successful?</a>
@ -137,8 +139,11 @@
</p>
<ul>
<li>
Java (SE) 1.6.x* <a href="http://java.sun.com">http://java.sun.com</a>
(Not OpenJDK)
Java (SE) 1.6.x <a href="http://java.sun.com">http://java.sun.com</a>
<ul>
<li>VIVO does not work with OpenJDK</li>
<li>VIVO does not work with Java 1.7</li>
</ul>
</li>
<li>
Apache Tomcat 6.x or 7.x <a href="http://tomcat.apache.org">http://tomcat.apache.org</a>
@ -147,7 +152,7 @@
Apache Ant 1.7 or higher, <a href="http://ant.apache.org">http://ant.apache.org</a>
</li>
<li>
MySQL 5.1 or higher**, <a href="http://www.mysql.com">http://www.mysql.com</a>
MySQL 5.1 or higher, <a href="http://www.mysql.com">http://www.mysql.com</a>
</li>
</ul>
<p>
@ -158,36 +163,29 @@
support websites.
</p>
<p>
* Note that vivo does not yet work with Java 1.7
The following browsers are supported for this release
</p>
<p>
** 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.
</p>
<p>
*** Note that for this release, the following browsers are supported.
</p>
<p>
Mac:
</p>
<ul>
<li>Chrome 8.0.552.237</li>
<li>FireFox 3.6.13</li>
<li>Opera 10.6.2</li>
<li>Safari 5.0.3</li>
</ul>
<p>
PC:
</p>
<ul>
<li>Chrome 8.0.552.273</li>
<li>FireFox 10.0.2</li>
<li>Internet Explorer 7, 8, 9</li>
<li>Opera 10.6.2</li>
</ul>
<ul>
<li>
Mac:
<ul>
<li>Chrome 8.0.552.237</li>
<li>FireFox 3.6.13</li>
<li>Opera 10.6.2</li>
<li>Safari 5.0.3</li>
</ul>
</li>
<li>
PC:
<ul>
<li>Chrome 8.0.552.273</li>
<li>FireFox 10.0.2</li>
<li>Internet Explorer 7, 8, 9</li>
<li>Opera 10.6.2</li>
</ul>
</li>
</ul>
<h3 id="create_database">II. Create an empty MySQL database </h3>
<p>
Decide on a database name, username, and password. Log into your
@ -214,8 +212,8 @@
<br>
</h3>
<p>
Download the VIVO application source as either <code>rel-1.4.zip</code>
or <code>rel-1.4.gz</code>
Download the VIVO application source as either <code>rel-1.5.zip</code>
or <code>rel-1.5.gz</code>
file and unpack it on your web server:
<br>
<a href="http://vivoweb.org/download">http://vivoweb.org/download</a>
@ -607,7 +605,7 @@
The number of grants and publications is large.
</li>
</ul>
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.
</td>
</tr>
@ -675,6 +673,42 @@
</td>
</tr>
<tr>
<td colspan="2">
Show only the most appropriate data values based on the Accept-Language
header supplied by the browser. Default is true if not set.
</td>
</tr>
<tr class="odd_row">
<td>
RDFService.languageFilter
</td>
<td>
true
</td>
</tr>
<tr>
<td colspan="2">
These values are used when deploying VIVO as an OpenSocial container
and integrating with OpenSocial gadgets
(see <a href="#opensocial">Step XII</a>, below). If you are creating
a VIVO installation that does not use OpenSocial gadgets, these values are omitted.
</td>
</tr>
<tr class="odd_row">
<td>
OpenSocial.shindigURL<br>
OpenSocial.tokenService<br>
OpenSocial.tokenKeyFile<br>
OpenSocial.sandbox
</td>
<td>
&nbsp;
</td>
</tr>
</tbody>
</table>
<h3 id="deploy">V. Compile and deploy</h3>

View file

@ -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