DLXS Installation


The goal of the install process is to create an initial working system that can function using the sample collection data.

On the open source CD you'll find:

XPAT is on the second CD.

There are two methods to do the open source install:

Installer only installs the middleware not the open source binaries or XPAT binaries

The install process

There are 3 parts to installing DLXS:

  1. Pre-install. Preparation for middleware installation.
  2. Running Installer
  3. Post-install steps. Operations not handled by Installer

Pre-install steps

Decide where to install

Installer will ask for a path to a directory which initially should not exist, e.g. /usr/local/dlxs. Installer will create dlxs under /usr/local and populate it.

This path will be referred to as DLXSROOT and is accessed by the middleware via the DLXSROOT environment variable set by the web server. You should set DLXSROOT in your unix shell and for the Apache web server. Web server configuration info follows below. Setting DLXSROOT in the shell is necessary when running some DLXS command line scripts or the debugging the middleware.

Super-user privileges are not required. Only user write access to the directory containing DLXSROOT. Set your umask to 022 so files/directories will be created 664/775.

Extracting/Installing XPAT

Uncompress and untar the XPAT tarfile where you would like to store the XPAT executables. For example, at many sites, this is /usr/local/.

This directory should be in your shell $PATH. This enables Installer to offer you their actual locations when it prompts. We'll illustrate the case where the CD and destination are local to one machine. We'll assume /usr/local, xpat-5.3.2, Sun Solaris and a cdrom mount point of /cdrom:

    cd /usr/local
    zcat /cdrom/xpat-5.3.2/xpat_solaris-5.3.2.tar.gz | tar xf -

Unlink any previous symlink from a version-specific directory of XPAT to an xpat directory (i.e., one without a specific version name. For example:

    cd /usr/local
    rm xpat

Create a symlink from the new version-specific directory of XPAT to an xpat directory (i.e., without version name). For example:

    cd /usr/local
    ln -s xpat-5.3.2 /usr/local/xpat

Other Binaries

There are 3 other binaries which you may need. Install these on your system as required for the Classes you plan to use.

Installation steps for tif2web, mrsid_retrieve, cjpeg and kdu_* are identical to those for XPAT.

Only c42pdf is not part of the DLXS distribution. Obtain as follows:

Get Required Perl modules

We currently recommend you use the standard Perl 5.8.3 (or higher) release.

In addition you'll need to install additional modules which can be obtained from CPAN.

Installer checks existence and version for each of these. Installer will list those not found and those with a version less than the recommended version.

It's OK to install without first obtaining the additional modules so long as you fetch and install them before running the DLXS middleware.

Install steps

Install problems. If for any reason the install is unsuccessful you may repeat the process. Simply delete the DLXSROOT directory (if it has been created) and run Installer again.

Using the example paths from earlier:

  cd /usr/local/dlxs
  perl Installer.pl

Installer will run and prompt you to answer a number of questions. Installer.pl does not hard-code a Perl path so be sure to run it as an argument to the Perl command line as shown above.

There are several functions performed by Installer:

Post-install steps

Create session directories (Required for CSV sessions)

If your session database type is CSV, create the session and sessionlock subdirectories in the locations you specified when configuring DlpsSession.cfg and change the permissions on them to give write access for the UID of the web server.

Change directory and file permissions

The DLXSROOT/web/t/text/gifcvtdir is created by the Install program with 777 permissions. Optionally, you may want to change permissions on this directory to make it writeable only to the UID of the web server.

The files (sample database tables) in DLXSROOT/misc/db are installed with 666 permissions. Optionally, you may want to change permissions on these files to make them accessible only to the UID of the web server.

Apache config sample files

Examine DLXSROOT/bin/installer/config-examples/httpd.conf.dlxs. You may integrate this segment into your Apache configuration file, adapting as necessary. It assumes you want to run your DLXS installation on a virtual host called dlxs.<?dlxs-install var="hostname"?> (where the part between the braces will be replaced with the hostname of the machine you installed on) and that you have created the proper DNS record, typically dlxs.<?dlxs-install var="hostname"?> IN CNAME <?dlxs-install var="hostname"?>

Take a look at this Apache virtual host configuration for one of the workshop users.

If you would like to run your DLXS installation on a different virtual host, please consult your Apache documentation.

You can comment-out the Basic Authentication section in httpd.conf.dlxs Basic Authentication for the collmgr. If you disable this be aware that the collmgr requires some form of authentication which sets the REMOTE_USER variable for proper operation. So, to run "out of the box", the easiest thing to do is to use the "Basic Authentication" sample configuration.

The file DLXSROOT/bin/installer/config-examples/htpasswd.dlxs codes the administrative user ID dlxsadm for the collmgr with the password collmgr. Change the password to a different value using the Apache program:

htpasswd passwordfile username

where passwordfile is APACHE/conf/htpasswd.dlxs and username is dlxsadm. Note: place htpasswd.dlxs in the conf subdirectory of you Apache installation.

Database migration

Please see the workshop page about moving and converting the dlxs database.