NIHVIVO-3845 update the Upgrade document for 1.5
This commit is contained in:
j2blake
parent
aadc4825db
commit
14ab5d559d
3 changed files with 180 additions and 18 deletions
|
|
@ -149,7 +149,7 @@
|
|||
Apache Tomcat 6.x or 7.x <a href="http://tomcat.apache.org">http://tomcat.apache.org</a>
|
||||
</li>
|
||||
<li>
|
||||
Apache Ant 1.7 or higher, <a href="http://ant.apache.org">http://ant.apache.org</a>
|
||||
Apache Ant 1.8 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>
|
||||
|
|
|
|||
|
|
@ -684,10 +684,7 @@
|
|||
you will need to rerun the knowledge base migration.
|
||||
</dd>
|
||||
</dl>
|
||||
<p>
|
||||
|
||||
</p>
|
||||
</p>
|
||||
|
||||
<h3 id="kbm">IV. Knowledge Base Migration</h3>
|
||||
<h4 id="kbmprocess">i.Knowledge Base Migration Process</h4>
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -37,7 +37,15 @@
|
|||
<toc>
|
||||
<ol class="roman2">
|
||||
<li><a href="#preparation">Before Performing the Upgrade</a></li>
|
||||
<li><a href="#changes">Noteworthy Changes</a> <br>
|
||||
<li>
|
||||
<a href="#changes">Noteworthy Changes</a>
|
||||
<ol class="roman2">
|
||||
<li><a href="#upgradeAnt">Ant version 1.8 is required</a></li>
|
||||
<li><a href="#customShortView">Custom short views</a></li>
|
||||
<li><a href="#openSocial">Support for OpenSocial gadgets</a></li>
|
||||
<li><a href="#browsers">Supported Browsers</a></li>
|
||||
</ol>
|
||||
</li>
|
||||
<li><a href="#upgrade_process">Upgrade Instructions</a></li>
|
||||
<li><a href="#kbm">Knowledge Base Migration</a></li>
|
||||
<li><a href="#termsofuse">Review the VIVO Terms of Use</a></li>
|
||||
|
|
@ -86,32 +94,41 @@
|
|||
</li>
|
||||
</ul>
|
||||
|
||||
<h1>BOGUS -- INSERT REAL STUFF HERE, EVENTUALLY</h1>
|
||||
<h3 id="changes">II. Noteworthy Changes</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<h4 id="upgradeAnt">Ant version 1.8 required</h4>
|
||||
<h4 id="upgradeAnt">Ant version 1.8 is required</h4>
|
||||
<p>
|
||||
See J.Blake for details.
|
||||
The VIVO build script has been revised, and now requires features from
|
||||
version 1.8 of Apache Ant. Version 1.8 has been available since February, 2010.
|
||||
The current version of Apache Ant is 1.8.4.
|
||||
</p>
|
||||
<p>
|
||||
You can find recent versions of Apache Ant at
|
||||
<a href="http://ant.apache.org">http://ant.apache.org</a>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<h4 id="customSearchView">Custom search views</h4>
|
||||
<h4 id="customSearchView">Custom short views</h4>
|
||||
<p>
|
||||
"Custom search views" have been re-implemented as part of the more flexible "Custom short views" mechanism.
|
||||
If you have custom search views, you will need to re-configure them.
|
||||
See J.Blake for details.
|
||||
If you have implemented custom search views, you will need to re-configure them to fit the new framework.
|
||||
For an explanation of how to use custom search views, consult the
|
||||
<a href="http://sourceforge.net/apps/mediawiki/vivo/index.php?title=Using_Short_Views_in_Release_1.5">
|
||||
SourceForge Wiki page on custom search views
|
||||
</a>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<h4 id="openSocial">Support for OpenSocial gadgets</h4>
|
||||
<p>
|
||||
You can now add OpenSocial support to your VIVO instance. Look at setting_up_orng.html for details.
|
||||
See J.Blake for details.
|
||||
VIVO can now be configured to support Open Research Networking Gadgets,
|
||||
an extension of OpenSocial gadgets. For a description of this, and instructions
|
||||
for configuring VIVO, look at <a href="./setting_up_orng.html">setting_up_orng.html</a>, in this directory.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<h4 id="openSocial">Supported Browsers</h4>
|
||||
<h4 id="browsers">Supported Browsers</h4>
|
||||
<p>
|
||||
For this release, the following browsers are supported.
|
||||
</p>
|
||||
|
|
@ -137,12 +154,159 @@
|
|||
</ul>
|
||||
|
||||
|
||||
<h1>BOGUS -- INSERT REAL STUFF HERE, EVENTUALLY</h1>
|
||||
<h3 id="#upgrade_process">III. Upgrade Instructions</h3>
|
||||
|
||||
<h1>BOGUS -- INSERT REAL STUFF HERE, EVENTUALLY</h1>
|
||||
<h3 id="kbm">IV .Knowledge Base Migration</h3>
|
||||
<p>
|
||||
1. Download the new distribution file and unpack it into a new
|
||||
source directory.
|
||||
</p>
|
||||
<p>
|
||||
2. Create a new deploy.properties using the same settings as in
|
||||
your previous installation and set values for the new variables as described
|
||||
below:
|
||||
<br>
|
||||
</p>
|
||||
<p>
|
||||
<!-- deploy.properties table from install.html -->
|
||||
</p>
|
||||
<table border='1' bordercolor="#CCCCCC" cellspacing="5">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>
|
||||
Property Name
|
||||
</th>
|
||||
<th>
|
||||
Example Value
|
||||
</th>
|
||||
</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 blue">
|
||||
<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.
|
||||
For instructions, look at <a href="./setting_up_orng.html">setting_up_orng.html</a>, in this directory.
|
||||
If you are creating
|
||||
a VIVO installation that does not use OpenSocial gadgets, these values are omitted.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="odd_row blue">
|
||||
<td>
|
||||
OpenSocial.shindigURL<br>
|
||||
OpenSocial.tokenService<br>
|
||||
OpenSocial.tokenKeyFile<br>
|
||||
OpenSocial.sandbox
|
||||
</td>
|
||||
<td>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
<p>
|
||||
3. Apply any previous changes you have made to the new source
|
||||
directory.
|
||||
</p>
|
||||
<blockquote>
|
||||
<strong>Special notes regarding source files</strong>
|
||||
<ul>
|
||||
<li>
|
||||
This process assumes any changes made to the application
|
||||
were
|
||||
made in the source directory and deployed, and were not made directly
|
||||
within the Tomcat webapps directory.
|
||||
</li>
|
||||
<li>
|
||||
In many cases, simply copying the modified files from your
|
||||
original source directory will not work since the files on which they
|
||||
are based have changed. It will be necessary to inspect the new source
|
||||
files and add any changes to them at that time.
|
||||
</li>
|
||||
<li>
|
||||
NIH-funded VIVO implementations will need to apply the
|
||||
Google
|
||||
Analytics Tracking Code (GATC) to <code>googleAnalytics.ftl</code>
|
||||
in
|
||||
the theme:<pre>[new_source_directory]/themes/[theme_dir]/templates/googleAnalytics.ftl</pre>
|
||||
A sample <code>googleAnalytics.ftl</code>
|
||||
is included in the built-in
|
||||
theme. This file serves only as an example, and you must replace the
|
||||
tracking code shown with your institution's own tracking code. For
|
||||
additional information about the GATC for the NIH-funded VIVO
|
||||
implementation sites and a copy of your institution's tracking code,
|
||||
see the <a href="https://confluence.cornell.edu/display/ennsrd/Google+Analytics+for+UI">VIVO
|
||||
Google
|
||||
Analytics
|
||||
wiki
|
||||
page</a>.
|
||||
</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<p>
|
||||
5. Stop Apache Tomcat and from your VIVO source directory, run
|
||||
ant
|
||||
by typing: <code>ant all</code>
|
||||
</p>
|
||||
<p>
|
||||
6. Start Apache Tomcat and log into VIVO as the root user when the upgrade is
|
||||
completed. Depending on the size of your database, the migration process may
|
||||
take up to several hours. When it is complete, you will
|
||||
see a message in the catalina.log file that the server has started.<pre>INFO: Server startup in XXXXX ms</pre>
|
||||
</p>
|
||||
<p>
|
||||
7. As root or an administrator, request a rebuild of the Solr search index:
|
||||
Go to the "Site Admin" page and click on "Rebuild Search Index" under the
|
||||
heading "Refresh Content".
|
||||
</p>
|
||||
<p>
|
||||
8. Review and save aside the knowledge base migration logs.
|
||||
The knowledge base migration process described in the next section will generate logs.
|
||||
These logs will be overwritten if you redeploy the VIVO application (but not if you restart tomcat), and since
|
||||
they may be a useful reference if questions come up about your 1.5 VIVO data after deployment,
|
||||
you should save them aside.
|
||||
The logs are created in the Tomcat <code>webapps/vivo/WEB-INF directory</code>:
|
||||
</p>
|
||||
<dl>
|
||||
<dt>
|
||||
<code>ontologies/update/logs/knowledgeBaseUpdate.(timestamp).log</code>
|
||||
</dt>
|
||||
<dd>
|
||||
A log of a summary of updates that were made to the knowledge
|
||||
base. This file should end with "Finished knowledge base migration".
|
||||
If this file contains any warnings they should be reviewed with your
|
||||
implementation team representative to see whether any corrective action needs to be taken.
|
||||
</dd>
|
||||
</dl>
|
||||
<dl>
|
||||
<dt>
|
||||
<code>ontologies/update/logs/knowledgeBaseUpdate.(timestamp).error.log</code>
|
||||
</dt>
|
||||
<dd>
|
||||
A log of errors that were encountered during the upgrade
|
||||
process. This file should be empty if the upgrade was successful. If any errors are encountered
|
||||
you will need to rerun the knowledge base migration.
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h3 id="#kbm">IV. Knowledge Base Migration</h3>
|
||||
|
||||
<p>
|
||||
Changes to the VIVO core ontology may require corresponding
|
||||
modifications to the knowledge base instance data and ontology annotations.
|
||||
When VIVO first starts up following the upgrade, it will
|
||||
|
|
@ -191,6 +355,7 @@
|
|||
An N3 file containing all the statements that were added to the knowledge base.
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h3 id="termsofuse">V. Review the VIVO Terms of Use</h3>
|
||||
<p>
|
||||
VIVO comes with a "Terms of Use" statement linked from the footer. The "Site Name"
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue