checking in the very latest from the 14 branch
This commit is contained in:
stellamit
parent
d8245f3261
commit
64fb63d304
1 changed files with 418 additions and 375 deletions
241
doc/install.html
241
doc/install.html
|
|
@ -3,44 +3,43 @@
|
||||||
<head>
|
<head>
|
||||||
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
||||||
<meta charset="utf-8">
|
<meta charset="utf-8">
|
||||||
<title>VIVO Release 1 V1.4 Installation Guide</title>
|
<title>VIVO Release V1.4 Installation Guide</title>
|
||||||
<link rel="stylesheet" href="./css/doc.css" media="screen">
|
<link rel="stylesheet" href="./css/doc.css" media="screen">
|
||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
<div id="branding" role="banner">
|
<div id="branding" role="banner">
|
||||||
<h1 class="vivo-logo"><a href="/"><span class="displace">VIVO</span></a></h1>
|
<h1 class="vivo-logo"><a href="http://vivoweb.org"><span class="displace">VIVO</span></a></h1>
|
||||||
</div>
|
</div>
|
||||||
<!-- Start of content -->
|
<!-- Start of content -->
|
||||||
<div id="wrapper-content" role="main">
|
<div id="wrapper-content" role="main">
|
||||||
<h1>VIVO Release 1 V4 Installation Guide</h1>
|
<h1>VIVO Release V1.4 Installation Guide</h1>
|
||||||
<small>
|
<div>
|
||||||
December 9, 2011
|
December 10, 2011
|
||||||
</small>
|
</div>
|
||||||
<br>
|
|
||||||
<hr><!-- Page break --><!-- Installation process for V1.4 --><h2 id="installation">Installation process for V1.4</h2>
|
|
||||||
<p>
|
<p>
|
||||||
This document is a summary of the VIVO installation process. This
|
This document is a summary of the VIVO installation
|
||||||
and other documentation can be found on the <a href="http://vivoweb.org/support">support page</a>
|
process. For information about this release, consult
|
||||||
at <a href="http://vivoweb.org">VIVOweb.org</a>
|
the <a href="release.html">VIVO v1.4 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>.
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<p>
|
||||||
<li>
|
|
||||||
These instructions assume that you are performing a clean
|
These instructions assume that you are performing a clean
|
||||||
install, including emptying an existing database, emptying the VIVO
|
install, including emptying an existing database, emptying the VIVO
|
||||||
home directory, and removing a previous installation from the Tomcat
|
home directory, and removing a previous installation from the Tomcat
|
||||||
webapps directory. Product functionality may not be as expected if you
|
webapps directory. Product functionality may not be as expected if you
|
||||||
install over an existing installation of an earlier version.
|
install over an existing installation of an earlier version.
|
||||||
</li>
|
</p><p>
|
||||||
<li>
|
If you are going to upgrade an existing deployment, please consult
|
||||||
If you are going to upgrade an existing service, please consult
|
the <a href="upgrade-1.4.html">Release 1 V1.4 Upgrade Guide</a> in this directory.
|
||||||
the "upgrade" files in this directory.
|
</p><p>
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
<p>
|
|
||||||
VIVO Developers: If you are working on the VIVO source code from
|
VIVO Developers: If you are working on the VIVO source code from
|
||||||
Subversion, the instructions are slightly different. Please consult
|
Subversion, the instructions are slightly different. Please consult
|
||||||
developers.txt in this directory.
|
<a href="developers.txt">developers.txt</a> in this directory.
|
||||||
</p>
|
<p>
|
||||||
|
|
||||||
<h3>Where does VIVO live on your computer?</h3>
|
<h3>Where does VIVO live on your computer?</h3>
|
||||||
<p>
|
<p>
|
||||||
Before beginning the installation, let's look at the four locations
|
Before beginning the installation, let's look at the four locations
|
||||||
|
|
@ -48,10 +47,10 @@
|
||||||
</p>
|
</p>
|
||||||
<h4>The VIVO distribution directory</h4>
|
<h4>The VIVO distribution directory</h4>
|
||||||
<p>
|
<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 directory is created when you unpack the VIVO distribution file (see <a href="#download_code">Step III</a>, below). This directory is where you will
|
||||||
create your deploy.properties file (see <a href="#deploy_properties">Step
|
create your deploy.properties file (see <a href="#deploy_properties">Step
|
||||||
V</a>, below), and where you will make any modifications to the VIVO
|
V</a>, below), and where you will make any modifications to the VIVO
|
||||||
theme or code. You can create this wherever you choose.
|
theme or code. You can create this directory wherever you choose.
|
||||||
</p>
|
</p>
|
||||||
<h4>VIVO inside Tomcat</h4>
|
<h4>VIVO inside Tomcat</h4>
|
||||||
<p>
|
<p>
|
||||||
|
|
@ -66,25 +65,24 @@
|
||||||
<h4>The VIVO home directory</h4>
|
<h4>The VIVO home directory</h4>
|
||||||
<p>
|
<p>
|
||||||
VIVO will use this area to store some of the data it uses. Uploaded
|
VIVO will use this area to store some of the data it uses. Uploaded
|
||||||
image files are stored here, and the search index is stored here also.
|
image files are stored here, and the Solr home directory is stored here also.
|
||||||
You can create this wherever you choose. Tell VIVO where to find the
|
You can create this wherever you choose. Tell VIVO where to find the
|
||||||
home directory by setting <code>vitro.home.directory</code>
|
home directory by setting <code>vitro.home.directory</code>
|
||||||
in the
|
in the deploy.properties file (see <a href="#deploy_properties">Step V</a>,
|
||||||
deploy.properties file (see <a href="#deploy_properties">Step V</a>,
|
|
||||||
below). You must create this directory before starting VIVO, and you
|
below). You must create this directory before starting VIVO, and you
|
||||||
must ensure that Tomcat has permission to read and write to this
|
must ensure that Tomcat has permission to read and write to this
|
||||||
directory when it runs.
|
directory when it runs.
|
||||||
</p>
|
</p>
|
||||||
<h4>The MySQL database</h4>
|
<h4>The MySQL database</h4>
|
||||||
<p>
|
<p>
|
||||||
Essentially all of the data that you store in VIVO will be given to
|
The data that you add into VIVO will be stored in a MySQL database. The
|
||||||
MySQL for storage. The actual location of this data depends on what
|
actual location of this data depends on what
|
||||||
system you have, and on how you install MySQL (see <a href="#required_software">Step I</a>, below). but you won’t need to
|
system you have, and on how you install MySQL (see <a href="#required_software">Step I</a>, below).
|
||||||
know the location. You will access the data through VIVO, or
|
You will typically access the data through VIVO, or
|
||||||
occasionally through the MySQL client application.
|
occasionally through the MySQL client application.
|
||||||
</p>
|
</p>
|
||||||
<toc>
|
<toc>
|
||||||
<h3>Steps to Installation</h3>
|
<h3>Installation Instructions</h3>
|
||||||
<ol class="roman1">
|
<ol class="roman1">
|
||||||
<li>
|
<li>
|
||||||
<a href="#required_software">Install required software</a>
|
<a href="#required_software">Install required software</a>
|
||||||
|
|
@ -115,7 +113,7 @@
|
||||||
using "Contact Us" form)</a>
|
using "Contact Us" form)</a>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
<a href="#tomcat_connector">Setup Apache Tomcat Connector</a>
|
<a href="#tomcat_connector">Set up Apache Tomcat Connector</a>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
<a href="#external_auth">Using an External Authentication
|
<a href="#external_auth">Using an External Authentication
|
||||||
|
|
@ -136,17 +134,17 @@
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
Java (SE) 1.6 or higher, <a href="http://java.sun.com">http://java.sun.com</a>
|
Java (SE) 1.6.x* <a href="http://java.sun.com">http://java.sun.com</a>
|
||||||
(Not OpenJDK)
|
(Not OpenJDK)
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
Apache Tomcat 6.x, <a href="http://tomcat.apache.org">http://tomcat.apache.org</a>
|
Apache Tomcat 6.x or 7.x <a href="http://tomcat.apache.org">http://tomcat.apache.org</a>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
Apache Ant 1.7 or higher, <a href="http://ant.apache.org">http://ant.apache.org</a>
|
Apache Ant 1.7 or higher, <a href="http://ant.apache.org">http://ant.apache.org</a>
|
||||||
</li>
|
</li>
|
||||||
<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>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
<p>
|
<p>
|
||||||
|
|
@ -157,14 +155,12 @@
|
||||||
support websites.
|
support websites.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
* Note that VIVO V1.4 will not run on older versions of MySQL that
|
** Note that from version V1.2 onward VIVO does
|
||||||
may have worked with 1.1.1. Be sure to run VIVO 1.4 with MySQL 5.1 or
|
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
|
higher. Using unsupported versions may result in strange error messages
|
||||||
related to table formatting or other unexpected problems.
|
related to table formatting or other unexpected problems.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
|
||||||
* Note that VIVO is not yet compatible with Tomcat 7.
|
|
||||||
</p>
|
|
||||||
<h3 id="create_database">II. Create an empty MySQL database </h3>
|
<h3 id="create_database">II. Create an empty MySQL database </h3>
|
||||||
<p>
|
<p>
|
||||||
Decide on a database name, username, and password. Log into your
|
Decide on a database name, username, and password. Log into your
|
||||||
|
|
@ -191,7 +187,7 @@
|
||||||
<br>
|
<br>
|
||||||
</h3>
|
</h3>
|
||||||
<p>
|
<p>
|
||||||
Download the VIVO application source as either <code>rel-4.zip</code>
|
Download the VIVO application source as either <code>rel-1.4.zip</code>
|
||||||
or <code>rel-1.4.gz</code>
|
or <code>rel-1.4.gz</code>
|
||||||
file and unpack it on your web server:
|
file and unpack it on your web server:
|
||||||
<br>
|
<br>
|
||||||
|
|
@ -213,7 +209,7 @@
|
||||||
<em>External authentication:</em>
|
<em>External authentication:</em>
|
||||||
If you want to use an external
|
If you want to use an external
|
||||||
authentication system like Shibboleth or CUWebAuth, you will need to
|
authentication system like Shibboleth or CUWebAuth, you will need to
|
||||||
set two additional properties in this file. See the section below
|
set two additional properties in this file. See the step below
|
||||||
entitled <a href="#external_auth">Using an External Authentication
|
entitled <a href="#external_auth">Using an External Authentication
|
||||||
System with VIVO</a>.
|
System with VIVO</a>.
|
||||||
</p>
|
</p>
|
||||||
|
|
@ -235,11 +231,11 @@
|
||||||
the client. To make this possible, VIVO's default namespace must have a
|
the client. To make this possible, VIVO's default namespace must have a
|
||||||
certain structure and begin with the public web address of the VIVO
|
certain structure and begin with the public web address of the VIVO
|
||||||
installation. For example, if the web address of a VIVO installation is
|
installation. For example, if the web address of a VIVO installation is
|
||||||
"http://vivo.example.edu/" the default namespace must be set to
|
"http://vivo.example.edu/", the default namespace must be set to
|
||||||
"http://vivo.example.edu/individual/" in order to support linked data.
|
"http://vivo.example.edu/individual/" in order to support linked data.
|
||||||
Similarly, if VIVO is installed at "http://www.example.edu/vivo" the
|
Similarly, if VIVO is installed at "http://www.example.edu/vivo", the
|
||||||
default namespace must be set to
|
default namespace must be set to
|
||||||
"http://www.example.edu/vivo/individual/"<h5>* The namespace must end with "individual/" (including the
|
"http://www.example.edu/vivo/individual/".<h5>* The namespace must end with "individual/" (including the
|
||||||
trailing slash).</h5>
|
trailing slash).</h5>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
|
|
@ -635,6 +631,22 @@
|
||||||
/usr/local/vivo/harvester/
|
/usr/local/vivo/harvester/
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
|
|
||||||
|
<tr>
|
||||||
|
<td colspan="2">
|
||||||
|
Types of individual for which we can create proxy editors.
|
||||||
|
If this is omitted, defaults to http://www.w3.org/2002/07/owl#Thing
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd_row">
|
||||||
|
<td>
|
||||||
|
proxy.eligibleTypeList
|
||||||
|
</td>
|
||||||
|
<td>
|
||||||
|
http://xmlns.com/foaf/0.1/Person, http://xmlns.com/foaf/0.1/Organization
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
<h3 id="deploy">V. Compile and deploy</h3>
|
<h3 id="deploy">V. Compile and deploy</h3>
|
||||||
|
|
@ -670,14 +682,16 @@
|
||||||
<h4>Set security limits</h4>
|
<h4>Set security limits</h4>
|
||||||
<p>
|
<p>
|
||||||
VIVO is a multithreaded web application that may
|
VIVO is a multithreaded web application that may
|
||||||
require more threads than are permitted under your Linux installation's
|
require more threads than are permitted under your
|
||||||
default configuration. Ensure that your installation can support the
|
Linux installation's default configuration. Ensure
|
||||||
required number of threads by making the following edits to <code>/etc/security/limits.conf</code>:
|
that your installation can support the required number
|
||||||
|
of threads by making the following edits
|
||||||
|
to <code>/etc/security/limits.conf</code>:
|
||||||
</p>
|
</p>
|
||||||
<pre> apache hard nproc 400<br> tomcat6 hard nproc 1500 <br> </pre>
|
<pre> apache hard nproc 400<br> tomcat6 hard nproc 1500 <br> </pre>
|
||||||
<h4>Set URI encoding</h4>
|
<h4>Set URI encoding</h4>
|
||||||
<p>
|
<p>
|
||||||
In order for Solr to correctly search for international characters (>127),
|
In order for VIVO to correctly handle international characters,
|
||||||
you must configure Tomcat to conform to the URI standard by
|
you must configure Tomcat to conform to the URI standard by
|
||||||
accepting percent-encoded UTF-8.
|
accepting percent-encoded UTF-8.
|
||||||
</p>
|
</p>
|
||||||
|
|
@ -696,58 +710,82 @@
|
||||||
</pre>
|
</pre>
|
||||||
<h4>Take care when creating Context elements</h4>
|
<h4>Take care when creating Context elements</h4>
|
||||||
<p>
|
<p>
|
||||||
Each of the webapps in the VIVO distribution (VIVO and Solr) includes a "context fragment" file,
|
Each of the webapps in the VIVO distribution (VIVO and
|
||||||
containing some of the deployment information for that webapp.
|
Solr) includes a "context fragment" file, containing
|
||||||
|
some of the deployment information for that webapp.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Tomcat allows you to override these context fragments by adding Context elements to "server.xml".
|
Tomcat allows you to override these context fragments
|
||||||
If you decide to do this, be sure that your new Context element includes the necessary
|
by adding Context elements to "server.xml". If you
|
||||||
deployment parameters from the overridden context fragment.
|
decide to do this, be sure that your new Context
|
||||||
|
element includes the necessary deployment parameters
|
||||||
|
from the overridden context fragment.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
See <a href="#tomcat_connector">Section X</a> below,
|
See <a href="#tomcat_connector">Step X</a> below,
|
||||||
for an example of overriding the VIVO context fragment.
|
for an example of overriding the VIVO context fragment.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3 id="start_tomcat">VII. Start Tomcat </h3>
|
<h3 id="start_tomcat">VII. Start Tomcat </h3>
|
||||||
<p>
|
<p>
|
||||||
Most Tomcat installations can be started by running <code>startup.sh</code>
|
Most Tomcat installations can be started by running <code>startup.sh</code>
|
||||||
or <code>startup.bat</code>
|
or <code>startup.bat</code> in Tomcat's bin directory. Point your
|
||||||
in Tomcat's bin directory. Point your
|
browser to <a href="http://localhost:8080/vivo/">http://localhost:8080/vivo</a> (or the appropriate URL based on the <code>webapp.name</code> value in deploy.properties) to test the application.
|
||||||
browser to "http://localhost:8080/vivo/" to test the application. If
|
</p>
|
||||||
Tomcat does not start up, or the VIVO application is not visible, check
|
<p>
|
||||||
the files in Tomcat's logs directory. Error messages are commonly found
|
On start up VIVO will run some diagnostic tests. If a
|
||||||
in <code>catalina.out</code>
|
problem is detected, the normal VIVO pages will redirect
|
||||||
or <code>localhost.log</code>
|
to a startup status page describing the problem. You
|
||||||
|
can stop tomcat, attempt to fix the problem and
|
||||||
|
proceed from <a href="#deploy">Step V</a>. The
|
||||||
|
startup status page may offer a continue link which
|
||||||
|
will allow you to use VIVO inspite of the problems.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
If Tomcat does not start up, or the VIVO application
|
||||||
|
is not visible, check the files in Tomcat's logs
|
||||||
|
directory. Error messages are commonly found
|
||||||
|
in <code>tomcat/logs/catalina.out</code>
|
||||||
|
or <code>tomcat/logs/vivo.all.log</code>
|
||||||
|
or <code>tomcat/logs/localhost.log.</code>
|
||||||
</p>
|
</p>
|
||||||
<h3 id="add_rdf">VIII. Log in and add RDF data </h3>
|
<h3 id="add_rdf">VIII. Log in and add RDF data </h3>
|
||||||
<p>
|
<p>
|
||||||
If the startup was successful, you will see a welcome message
|
If the startup was successful, you will see a welcome
|
||||||
informing you that you have successfully installed VIVO. Click the "Log
|
message informing you that you have successfully
|
||||||
in" link near the upper right corner. Log in with the <code>rootUser.emailAddress</code>
|
installed VIVO. Click the "Log in" link near the upper
|
||||||
you set up in Step IV. The initial password for the root account is
|
right corner. Log in with
|
||||||
"rootPassword" (without the quotes). On first login, you will be
|
the <code>rootUser.emailAddress</code> you set up in
|
||||||
prompted to select a new password and verify it a second time. When login is
|
Step IV. The initial password for the root account is
|
||||||
complete, the search index is checked and, if it is empty,
|
"rootPassword" (without the quotes). On first login,
|
||||||
a full index build will be triggered in the background, in order to ensure
|
you will be prompted to select a new password and
|
||||||
complete functionality throughout the site.
|
verify it a second time. When login is complete, the
|
||||||
|
search index is checked and, if it is empty, a full
|
||||||
|
index build will be triggered in the background in
|
||||||
|
order to ensure complete functionality throughout the
|
||||||
|
site.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
After logging in, you will be presented with a
|
After logging in, you can navigate to the "Site Admin" page that presents a menu of
|
||||||
menu of editing options. Here you can create OWL classes, object
|
editing options. Here you can create OWL classes,
|
||||||
properties, data properties, and configure the display of data.
|
object properties, data properties, and configure the
|
||||||
Currently, any classes you wish to make visible on your website must be
|
display of data. Currently, any classes you wish to
|
||||||
part of a class group, and there are a number of visibility and display
|
make visible on your website must be part of a class
|
||||||
options available for each ontology entity. VIVO comes with a core VIVO
|
group and any individual must have an rdfs:label.
|
||||||
ontology, but you may also upload other ontologies from an RDF file.
|
There are a number of visibility and display options
|
||||||
|
available for classes and properites. VIVO comes with a
|
||||||
|
core VIVO ontology, but you may also upload other
|
||||||
|
ontologies from an RDF file.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Under the "Advanced Data Tools" click "Add/Remove RDF Data." Note
|
Under the "Advanced Data Tools" section, click "Add/Remove RDF
|
||||||
that Vitro currently works best with OWL-DL ontologies and has only
|
Data." Note that Vitro currently works best with
|
||||||
limited support for pure RDF data. You can enter a URL pointing to the
|
OWL-DL ontologies and has only limited support for
|
||||||
RDF data you wish to load or upload from a file on your local machine.
|
pure RDF data. You can enter a URL pointing to the
|
||||||
Ensure that the "add RDF" radio button is selected. You will also
|
RDF data you wish to load or upload the RDF data from a file on
|
||||||
likely want to check "create classgroups automatically."
|
your local machine. Ensure that the "add RDF" radio
|
||||||
|
button is selected. You will also likely want to check
|
||||||
|
"create classgroups automatically."
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Clicking the "Index" tab in the navigation bar at the top right of
|
Clicking the "Index" tab in the navigation bar at the top right of
|
||||||
|
|
@ -948,6 +986,11 @@
|
||||||
account.
|
account.
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
<p>
|
||||||
|
The startup status will indicate if the basic
|
||||||
|
configuration of the system was successful. It can be
|
||||||
|
accessed from <strong>siteAdmin -> Startup status</strong>.
|
||||||
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Here is a simple test to see whether the ontology files were
|
Here is a simple test to see whether the ontology files were
|
||||||
loaded:
|
loaded:
|
||||||
|
|
@ -991,12 +1034,11 @@
|
||||||
field "URI" - it will be used in the next step.
|
field "URI" - it will be used in the next step.
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
Open a new web browser or browser tab to the page <a href="http://marbles.sourceforge.net/">http://marbles.sourceforge.net/</a>.
|
Open a new web browser or browser tab to the
|
||||||
In
|
page <a href="http://marbles.sourceforge.net/">http://marbles.sourceforge.net/</a>.
|
||||||
the
|
In the pink box on that page enter the URI of the
|
||||||
pink
|
individual you created in the previous step and
|
||||||
box on that page enter the URI of the individual you
|
click "open."
|
||||||
created in the previous step and click "open."
|
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
In the resulting page search for the URI of the "test
|
In the resulting page search for the URI of the "test
|
||||||
|
|
@ -1012,11 +1054,14 @@
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>
|
<li>
|
||||||
Type the word "Australia" into the search box, and click on the
|
Type the word "Australia" into the search box, and
|
||||||
Search button.You should see a page of results, with links to countries
|
click on the Search button.You should see a page
|
||||||
that border Australia, individuals that include Australia, and to
|
of results, with links to countries that border
|
||||||
Australia itself. To trigger the search index, you can log in as a site
|
Australia, individuals that include Australia, and
|
||||||
administrator and go to "http://your-vivo-url/SearchIndex".
|
to Australia itself. To trigger the search index,
|
||||||
|
you can log in as a site administrator and go
|
||||||
|
to <strong> Site Admin -> Rebuild search
|
||||||
|
index</strong>.
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
<h3 id="termsofuse">XIII. Review the VIVO Terms of Use</h3>
|
<h3 id="termsofuse">XIII. Review the VIVO Terms of Use</h3>
|
||||||
|
|
@ -1038,10 +1083,8 @@
|
||||||
<div id="footer" role="contentinfo">
|
<div id="footer" role="contentinfo">
|
||||||
<p class="copyright">
|
<p class="copyright">
|
||||||
<small>
|
<small>
|
||||||
©2011 All Rights Reserved
|
All Rights Reserved <a href="license.txt">see license</a>
|
||||||
</small>
|
</small>
|
||||||
| Powered
|
|
||||||
by <a class="powered-by-vivo" href="http://vivoweb.org" target="_blank"><strong>VIVO</strong></a>
|
|
||||||
</p>
|
</p>
|
||||||
<div id="nav" role="navigation">
|
<div id="nav" role="navigation">
|
||||||
<ul id="footer-nav" role="list">
|
<ul id="footer-nav" role="list">
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue