Child pages
  • How to Update to Variations 5.0.7 Client and Server

This space has moved to IU's Confluence.
It is located at https://uisapp2.iu.edu/confluence-prd/display/iulV3/

Skip to end of metadata
Go to start of metadata

How to Update to Variations 5.0.7 Client and Server

This page lists explains how to upgrade from 5.0.6 to 5.0.7 for both the Variations server and client. If you have any questions about or problems with the update process, please contact Chris Colvard (812-856-0026, cjcolvar@indiana.edu).

Note: The 5.0.7 server should accompany a distribution of 5.0.7 clients. Previous clients will work with the 5.0.7 server but may encounter issues with vocabulary changes. 5.0.7 clients are not compatible with pre-5.0.7 servers.

Step 1. Upgrade the Variations Servers from 5.0.6 to 5.0.7

Note: The upgrade process will stop your cataloging and production servers. You will also have to allow time for some hand-editing of configuration files to preserve your local customizations, as indicated by the output of the update script you will run. And finally you will have to restart your Variations server applications.

To install the server update, execute the following commands from your Variations install directory, /home/dmlserv.

  1. Download the Variations_5.0.7_Update.tar.gz file to /home/dmlserv
  2. First, untar the server update file: tar xvfz Variations_5.0.7_Update.tar.gz
  3. Then change directories to the update directory: cd Variations_5.0.7_Update
  4. Run the update script and create a log of its output: ./update.sh | tee -a update.sh.log
  5. Read through the output of the update script (also available in the log file, update.sh.log).
  6. Manually edit any files that did not patch correctly or need manual editing as noted by the update output.
    • Example versions of files that need to be manually edited can be found in /home/dmlserv/Variations_5.0.7_Update/.
  7. Restart the Variations cataloging and production servers.

Step 2. Upgrade Variations clients from 5.0.6 to 5.0.7

Ideally, this should be done by creating a new Variations installer based on a Variations 5.0.7 client Windows zip or Mac tar.

  1. Download and unzip (or untar) the 5.0.7 client distribution
  2. Copy over any configuration files you modified for your 5.0.6 client. See Configuring the Client - 5.0.7 for a list of client configuration files. See Windows Client Changes and Mac Client Changes below for files that have changed in 5.0.7 and should be merged with 5.0.6 copies.
  3. Follow the directions in Building the Client Installer - 5.0.7

Server Changes

File

Change

~/VERSION

Changed from 5.0.6 to 5.0.7

~/bin/run_RMIRegistry.sh, ~/bin/v2run.sh

Changes to support 1.5 and 1.6 Java JREs

~/data/ServerLegalNotices.txt, ~/data/legal_notices.html

Changed from 5.0.6 to 5.0.7

~/data/accessPages/access.xsl

Changes for DRAM support

~/server.jar

Bug fixes and changes to support DRAM, the Access Manager Webapp, and other changes:
See Variations3 Release 5.0.7 for more information.

Windows Client Changes

File

Change

Program Files/Variations/Client/readme.rtf

Added version 5.0.7 to Revision History

Program Files/Variations/Client/VERSION

Changed from 5.0.6 to 5.0.7

Program Files/Variations/Client/data/legal_notices.html

Changed from 5.0.6 to 5.0.7

Program Files/Variations/JRE

Updated bundled JRE to 1.6.0_14

Program Files/Variations/Client/client.jar

Bug fixes and other changes
See Variations3 Release 5.0.7 for more information.

Mac Client Changes

File

Change

Variations.app/Contents/Info.plist

Bumped version number to 5.0.7 and Changed JRE version setting allow use of 1.6 (if available)

Variations.app/Contents/Resources/Java/VERSION

Changed from 5.0.6 to 5.0.7

Variations.app/Contents/Resources/Java/client.jar

Bug fixes and other changes
See Variations3 Release 5.0.7 for more information.

Variations.app/Contents/Resources/Java/data/legal_notices.html

Changed from 5.0.6 to 5.0.7

Variations.app/Contents/Resources/English.lproj/InfoPlist.strings

Bumped version number to 5.0.7

Terms-of-Use.html

Changed from 5.0.6 to 5.0.7

Configuration Changes

  • The status line in the player will now report the institution it is streaming from. This will default to the Library Name specified in dmlserver.xml, but can be adjusted by adding the dml.client.institutionName SystemProperty to both library server's configurations in dmlserver.xml.

Note that the configuration changes below were mostly made to avoid unnecessary configuration work and confusion for new installations of Variations. No action needs to be taken because of these changes.

  • All vocabularies now exist on the server only. Clients pull and cache vocabularies from the server as needed. If new terms need to be added to vocabularies, this can be done while the server is running and clients will see the changes after a restart. Term deletion requires editing all records which use the term thus should generally be avoided.
  • Authentication schemes are now indexed by realms instead of protocols. This change means that all authentication schemes are returned to the client login window for selection.
  • No labels