litvinovg/vivo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

merge from rel-1.1-maint branch: small tweaks and fixed some tabbing issues NIHVIVO-411

Browse source
This commit is contained in:
nac26 2010-07-27 13:06:17 +00:00
parent b4e4619619
commit 8587c2d0c8
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/upgrade-1.1.txt
View file

@ -1,12 +1,12 @@
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
Upgrading NIH VIVO Upgrading VIVO
Steps to Upgrade from Release 1 Version 1.0 to Release 1 Version 1.1 Steps to Upgrade from Release 1 Version 1.0 to Release 1 Version 1.1
This file provides a short description of the steps involved in upgrading your This file provides a short description of the steps involved in upgrading your
installation of NIH VIVO from Release 1 Version 1.0 to Release 1 Version 1.1. installation of VIVO from Release 1 Version 1.0 to Release 1 Version 1.1.
This and other documentation can be found at: This and other documentation can be found at:
http://vivoweb.org/support http://vivoweb.org/support
@ -40,7 +40,7 @@ exceptions:
you back-up the MySQL database. you back-up the MySQL database.
* It is not necessary to add RDF data or reconfigure the Apache HTTP Server. * It is not necessary to add RDF data or reconfigure the Apache HTTP Server.
* First-time login of the administrator account will use the password * First-time login of the administrator account will use the password
previously set, NOT the password in deploy.properties. previously set, NOT the initial password referenced in deploy.properties.
* The first time Apache Tomcat starts up after the upgrade, it will * The first time Apache Tomcat starts up after the upgrade, it will
initiate a process that modifies the knowledge base to align the data initiate a process that modifies the knowledge base to align the data
with the revised ontology. See the section on "Ontology Changes" with the revised ontology. See the section on "Ontology Changes"
@ -65,13 +65,13 @@ II. The Upgrade Process
3. Create deploy.properties, using the same values as in your previous 3. Create deploy.properties, using the same values as in your previous
installation. installation.
4. Apply any changes you have made to the new source directory. 4. Apply any previous changes you have made to the new source directory.
************* Special notes regarding source files ******************** ************* Special notes regarding source files ********************
This process assumes any changes made to the application were made in This process assumes any changes made to the application were made in
the source directory and deployed, and were not made directly within the source directory and deployed, and were not made directly within
Apache Tomcat webapp. the Tomcat webapps directory.
In many cases, simply copying the modified files from your original In many cases, simply copying the modified files from your original
source directory will not work since the files on which they are based source directory will not work since the files on which they are based
@ -335,7 +335,7 @@ theme to VIVO 1.1.
identity.jsp => identity.ftl identity.jsp => identity.ftl
menu.jsp => menu.ftl and search.ftl menu.jsp => menu.ftl and search.ftl
footer.jsp => footer.ftl footer.jsp => footer.ftl and googleAnalytics.ftl
googleAnalytics.ftl is a new file included from footer.ftl to googleAnalytics.ftl is a new file included from footer.ftl to
which you will add your site's Google Analytics Tracking Code which you will add your site's Google Analytics Tracking Code