Installing the Variations Server Software

How to install and configure the Variations server software. Some elements of the server software configuration may be dependent on settings created during the Server Setup process. Review the previous step if you have question relating to how your environment is setup.


Dmlserv Account

Login to the dmlserv account on your server machine.

Downloading files, executing commands, and editing configuration files as dmlserv is necessary (unless otherwise specified) for the proper installation and configuration of the Variations server.

Variations Software Download

Download the gzipped Variations tar file to /home/dmlserv.
To download the file,

Extract the server software files.

Variations Initialization

The Variations initialization script will:

The Variations initialization script requires four values:

These values will be used throughout the configuration process, and will be required for Client-Server communication. Check that you have the correct IP values and/or resolved hostnames before running the initialization scripts.

Since the script modifies and configures multiple directories and files:


Use the same values that you entered previously

Run the Variations Initialization Script

Successful execution will provide no output.

Variations Derivative Upload Service

As part of the digitizing ingest process, derivative files need to be transported from the digitizer's client computer to the Variations Streaming Server host computer. Currently two options are supported for the mechanism to provide this transport service, Samba or SFTP.

Samba provides a network connection on the streaming server host that the digitizer client can link to by defining a mapped network drive. SFTP is a file transport process that is implemented under SSH. The use of the selected service is determined by configuration of the digitizer client and performed by the client software. Either approach appears the same to the digitizer except for the Samba requirement of a mapped network drive on the client computer.

Variations Configuration

File paths are relative to /home/dmlserv/Variations-6.2 except where noted.

Server Configuration Files

Modify the main server configuration files.
The files dmlserver.xml and dmlscript.conf must be modified where specified in the configuration instructions on the server configuration page. Modifying the configuration files changes the Variations server settings which provide for integration with your university's systems.

Server Access Policy

Customize the server access policy configuration file
The access policy configuration file is used by Variations to control user access rights. The accessPolicy.xml file is referenced by Variations to determine access rights for user groups (e.g., catalogers). Later in the documentation you will be asked to create groups using the access management script. The groups created by the script will be dependent on the information in the accessPolicy.xml file. For more information on this process review Administrator's Guide - Authorization page.

Server-Client Configuration Files

Customize the server-client configuration file.
The client configuration files on the server allows many of the server scripts to access Variations as a client. Scripts like (described more below) utilize this configuration files in order to execute.

Statistics Files

Customize files containing IP lists for statistics.
The statistics files are used by Variations to generate user usage and streaming statistics. A Perl script compiles and displays the usage statistics through a web based CGI output page. The configuration files MusicLibraryComputers.txt and OnCampusComputers.txt allow for limiting of the statistics by IP address. The script utilizes the configuration files for the interpretation of the server logs, which are then processed appropriately to the CGI output page. Adding the applicable IP addresses to both the music library computers file and on campus computers file will support tracking of usage by location.

Vocabulary Files

Customize vocabulary files containing values to be used in the metadata when cataloging.

A number of files located in data/vocab/ provide string values used in the metadata. The only vocab files that should be changed are AudioDigitizationEquipment.vcb, ImageDigitizationEquipment.vcb, and Location.vcb. The files should be edited to include relevant information that can be used by digitizers and catalogers during the ingest process. The terms will be added to drop down boxes and can then be applied to media objects as metadata. The equipment lists should include the different types of equipment used in the digitization process like scanners, amplifiers, and other devices. The location file should be updated to include the storage location of the physical copies.

Access Manager and Metadata Schema Setup


Next you will need to create two separate databases. The first database will be used for access management and the other database will be used for the metadata schema.

The Variations library application server retrieves information for a user from the Access Manager Database, library_name_DMLLIB, when the user first connects to the server and starts a session. The library_name_DMLLIB database and the access policy will serve as the primary components for letting end users, catalogers, and digitizers access content in Variations. For more information read the Authorization section of the System Architecture Overview.

The metadata database is used to hold the related metadata schema that will be used for cataloging and accessing records in Variations. The library_name_METADATA database will hold the production metadata used by end users as well as the records being created by catalogers and digitizers. For more information on this database see the Databases section of the System Architecture Overview.

Set up Instructions

Throughout the following setup replace library_name with your library name, which was previously specified when running the initialization script.

Next, create a file in the dmlserv home directory named .my.cnf that contains the following:



Set permissions on the file to make sure that no one else can read the file:
chmod 600 /home/dmlserv/.my.cnf

Start, stop, and check the Variations Servers

Variations servers as a group

These commands operate on all the servers used by Variations

For just lease manager(s)

For just Variation service(s)

For more descritpions about these scripts and running Variations visit the Running Variations page.

The servers need to be running for the and commands to work.

Access Groups Setup

Access to your content is controlled through the access manager database. In order to create and change user access rights use the access management script( (Later on, if you set up the Variations Web Applications, you can manage access groups through the Variations Access Manager web application.)

Initially one or more of the following groups should be created in order to input content into the system:

Catalogers get access to the "Admin" tab, which can be used for cataloging (though few institutions actually do the Variations cataloging work). The windows accessible through the admin tab are sometimes needed for manually changing the status of records that need some rework, or for doing a search on records matching specific criteria. In general, Cataloger privilege is for people (1) managing the work of digitizers or (2) doing actual cataloging work to support the recording-score synchronization or the optional search function. Catalogers do not see the Digitizer tab.

Digitizers see the digitizer tab and can do all the ingest work. Once they publish an item, they may need someone with a higher level of privilege (Cataloger or Administrator) to manually change the record status before they can make certain changes to the record. Digitizers do not see the Cataloger tab.

Administrators have both cataloger and digitizer privileges and tabs, and in addition they can use the access manager web app to administer permissions overall, such as being able to add and delete members from the Digitizers or Catalogers groups. If you have only one or a very small number of people putting content in Variations, you may want to just use the Administrators group, or the Administrators and Digitizers groups.

Initially, use the script to set up the access groups.

Loading records into Metadata Schema

Cron Job Setup

Several cron jobs need to be set up to get Variations to work.

To set up the cron jobs:

Next Steps

You have completed the Variations server install process. Next start the section on Client Installation Overview.

Back to the Administrators Guide Home Page