- -
- +
diff --git a/doc/upgrade-1.5.html b/doc/upgrade-1.5.html
index 8b429d11..b83478fb 100644
--- a/doc/upgrade-1.5.html
+++ b/doc/upgrade-1.5.html
@@ -37,7 +37,15 @@
- 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. +
++ You can find recent versions of Apache Ant at + http://ant.apache.org
"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 + + SourceForge Wiki page on custom search views +
- 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 setting_up_orng.html, in this directory.
For this release, the following browsers are supported.
@@ -137,12 +154,159 @@+ 1. Download the new distribution file and unpack it into a new + source directory. +
+
+ 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:
+
+
+ +
+| + Property Name + | ++ Example Value + | +
|---|---|
| + 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. + For instructions, look at setting_up_orng.html, in this directory. + 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 + |
+ + + | +
+ 3. Apply any previous changes you have made to the new source + directory. +
++ Special notes regarding source files +++
+- + 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. +
+- + 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. +
+- + NIH-funded VIVO implementations will need to apply the + Google + Analytics Tracking Code (GATC) to
+googleAnalytics.ftl+ in + the theme:[new_source_directory]/themes/[theme_dir]/templates/googleAnalytics.ftl+ A samplegoogleAnalytics.ftl+ 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 VIVO + Google + Analytics + wiki + page. +
+ 5. Stop Apache Tomcat and from your VIVO source directory, run
+ ant
+ by typing: ant all
+
+ 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.
INFO: Server startup in XXXXX ms+ +
+ 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". +
+
+ 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 webapps/vivo/WEB-INF directory:
+
ontologies/update/logs/knowledgeBaseUpdate.(timestamp).log
+ ontologies/update/logs/knowledgeBaseUpdate.(timestamp).error.log
+ 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. +
VIVO comes with a "Terms of Use" statement linked from the footer. The "Site Name"