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.