Versions Compared

Old Version 1

changes.mady.by.user Jim Blake

Saved on

compared with

New Version 2

changes.mady.by.user Jim Blake

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

February 16,2011 - Upgrading from Release 1 v1.1 to Release 1 v1.2
*Release announcement for V1.2Upgrade Guide
*Upgrade process for V1.2Guide
This document provides a short description of the steps involved in upgrading your installation of VIVO from Release 1, Version 1.1 to Version 1.2. This and other documentation can be found on the support page at VIVOweb.org

...

Example Value

Default namespace: VIVO installations make their RDF resources available for harvest using linked data. Requests for RDF resource URIs redirect to HTML or RDF representations as specified by 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 installation. For example, if the web address of a VIVO installation is "

No Format
http://vivo.example.edu/

" the default namespace must be set to "

No Format
http://vivo.example.edu/individual/

" in order to support linked data. Similarly, if VIVO is installed at "

No Format
http://www.example.edu/vivo

" the default namespace must be set to "

No Format
http://www.example.edu/vivo/individual/

"

  • The namespace must end with "individual/" (including the trailing slash).|

    Vitro.defaultNamespace

    *

    No Format
    http://vivo.mydomain.edu/individual/

    *

    Directory where Vitro code is located. In most deployments, this is set to ./vitro-core (It is not uncommon for this setting to point elsewhere in development environments).

    vitro.core.dir

    ./vitro-core

    Directory where tomcat is installed.

    tomcat.home

    /usr/local/tomcat

    Name of your VIVO application.

    webapp.name

    vivo

    Directory where uploaded files will be stored. Be sure this directory exists and is writable by the user who the Tomcat service is running as.

    upload.directory

    /usr/local/vivo/data/uploads

    Directory where the Lucene search index will be built. Be sure this directory exists and is writable by the user who the Tomcat service is running as.

    LuceneSetup.indexDir

    /usr/local/vivo/data/luceneIndex

    Specify an SMTP host that the form will use for sending e-mail (Optional). If this is left blank, the contact form will be hidden and disabled.

    Vitro.smtpHost

    smtp.servername.edu

    Specify the JDBC URL of your database. Change the end of the URL to reflect your database name (if it is not "vivo").

    VitroConnection.DataSource.url

    jdbc:mysql://localhost/vivo

    Change the username to match the authorized user you created in MySQL.

    VitroConnection.DataSource.username

    username

    Change the password to match the password you created in MySQL.

    *VitroConnection.DataSource.password

    password

    -*

    Panel

    • Specify the Jena triple store technology to use. SDB is Jena's SPARQL database; this setting allows RDF data to scale beyond the limits of the JVM heap. Set to RDB to use the older Jena RDB store with in-memory caching.*

    • -*

      • VitroConnection.DataSource.tripleStoreType*

      SDB

      -*

    • Specify the maximum number of active connections in the database connection pool to support the anticipated number of concurrent page requests. It is not necessary to adjust this value when using the RDB configuration.*

    • -*

      • VitroConnection.DataSource.pool.maxActive*

      40

      -*

    • Specify the maximum number of database connections that will be allowed to remain idle in the connection pool. Default is 25% of the maximum number of active connections.*

    • -*

      • VitroConnection.DataSource.pool.maxIdle*

      10

      -*

    • Change the dbtype setting to use a database other than MySQL. Otherwise, leave this value unchanged. Possible values are DB2, derby, HSQLDB, H2, MySQL, Oracle, PostgreSQL, and SQLServer. Refer to

      No Format
      http://openjena.org/wiki/SDB/Databases_Supported

      for additional information.*

    • -*

      • VitroConnection.DataSource.dbtype*

      MySQL

      -*

    • Specify a driver class name to use a database other than MySQL. Otherwise, leave this value unchanged. This JAR file for this driver must be added to the the webapp/lib directory within the vitro.core.dir specified above.*

    • -*

      • VitroConnection.DataSource.driver*

      com.mysql.jdbc.Driver

      -*

    • Change the validation query used to test database connections only if necessary to use a database other than MySQL. Otherwise, leave this value unchanged.*

    • -*

      • VitroConnection.DataSource.validationQuery*

      SELECT 1

      -*

    • Specify the name of your first admin user for the VIVO application. This user will have an initial temporary password of 'defaultAdmin'. You will be prompted to create a new password on first login.*

    • -*

      • initialAdminUser*

      defaultAdmin

      -*

  • The URI of a property that can be used to associate an Individual with a user account. When a user logs in with a name that matches the value of this property, the user will be authorized to edit that Individual. For example, to use the netID at Cornell University as the property:

...

  • 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 baed 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

...