Upgrade Installation

To upgrade the full DVN installation, you must upgrade each of the following components. Follow the general procedures to upgrade the DVN application, and then review the summary of the changes entailed in upgrading to the current version:

Upgrade the DVN Application

There are two parts to upgrading the DVN application: upgrade the DVN software, and upgrade environment and configuration settings for the new version. See these topics for details:

Upgrade the Software

To upgrade the DVN software:

  1. Download the latest DVN-EAR_<version>.ear and buildupdate_<version>.sql database script from SourceForge.net.
  2. Open the GlassFish Admin Console to manage the Applications options.
  3. For the Enterprise Applications, redeploy the DVN-EAR package.
  4. Use the GlassFish option to locate the updated DVN-EAR.ear file, and select it to redeploy the updated code.

    When the application is deployed, you might see SQL warnings that, in summary, state that the required tables exist already in the database.
  5. Update the database.

    Open the database in the PostgreSQL pgAdmin tool and execute the buildupdate.sql script.
 Type the following: 

    psql -d <your database name> -f /<DVN>/buildupdate.sql
    
Notes:
    • If there were no changes to the database, you do not need to run the buildupdate.sql script.
    • The buildupdate.sql script updates the database from one version to the next. If you upgrade from one version of the DVN application to another that is not the next sequential version, you must run the update script for all versions in between.

Log in to the Dataverse Network homepage to use the upgraded DVN.

Upgrade the Configuration and Environment - Version 1.3

If you upgrade from an existing installation of the DVN core code to version 1.3 of the code, perform the following summary steps to upgrade the application:

  1. Upgrade the DSB machine.
    
Install RServe, update R, and update Zelig.
  2. Deploy the v1.3 EAR file.
  3. Run the buildupdate script, changing the version number to 1.3.
  4. Copy the oaicat.properties file from the SVN download into the directory /usr/local/glassfish/nodeagents/domains/master/config to remove the invalid OAI Server protocol, MIF.
    Then, restart the GlassFish server to make the oaicat.properties take affect.
  5. Reindex all studies in the DVN.
    See Index Utilities in the Network Admins guide for detailed information about how to reindex all studies in the DVN.
    Note: Locks might be created when you reindex the studies. Also, check that the last index update time is correct.
  6. Update the membership of the OAI sets (including the no set membership) used in harvesting by using the Export Utilities.
    This populates the new harveststudy table needed to harvest sets. A call is made to populate the table after the export finishes, comparing lastExportTimes to the lastUpdateTimes of the table. Since the table is currently empty, it adds all studies (including harvested studies).
    See Export Utilities in the Network Admins guide for detailed information about how to update the membership of the OAI sets.
  7. If you harvest the ODUM DVN (http://arc.irss.unc.edu/dvn/), delete manually any ODUM studies that they deleted before you upgraded your version of the DVN code.

Upgrade DSB Services

Follow the steps described in the section Install DSB Services. Be sure to download the new dvn-dsb package files from SourceForge.net.

Upgrade Dependent Components

Install new versions of the Java SE, GlassFish, and PostgreSQL applications or R package and RServe service in your production environment only after you test them for the DVN build you are running. Some DVN builds might require that you upgrade to a new version of a dependent application.

See the following for details about how to upgrade a specific component:

Upgrade R Package

To upgrade the R package for use with the DVN application:

  1. Obtain the R rpm from the official CRAN site at http://cran.r-project.org/. 
If the version recommended by the DVN project is no longer on CRAN, please contact the DVN team.
  2. Install the rpm.
    If you already have an older version installed, do not upgrade. That is, do not use the rpm -U R command. Perform the following instead:
    1. Uninstall the old version first. Type:
      rpm -e R
    2. Delete all third-party packages from the old installation using one of the following commands, depending on your architecture:
      rm –rf /usr/lib/R
      rm –rf /usr/lib64/R
    3. Install the new rpm. Type:
      rpm –ivh R-<version>.rpm
  3. Obtain and rebuild all third-party modules.
    The DSB installation comes with a script that rebuilds these modules through the R package's built-in mechanism for resolving such dependencies. Make sure your system has all the necessary build components installed.
    To install these packages:
    • On a RedHat 4 system type the following:
      up2date <build components>
    • On a RedHat 5 system, use the new RedHat yum framework.
  4. Download and build the modules. Type the following:
    cd /usr/local/VDC/R
    ./installR.sh