Note: additional installation information is available in these companion documents:
|Authentication and Authorization:||http://webservices.itcs.umich.edu/mediawiki/dlxs14/index.php/Authentication_and_Authorization|
|DLXS daemon (optional):||http://webservices.itcs.umich.edu/mediawiki/dlxs14/index.php/DLXS_Daemon:_Installing_and_Configuring|
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 several methods to do the open source install:
Installer only installs the middleware not the open source binaries or XPAT binaries
Installer will ask for a path to a directory which initially should not exist, e.g. /l1/workshop/text02/dlxs. Installer will create dlxs under /l1/workshop/text02 and populate it.
Consider that you may want to install into a directory that is explicit about the release number you are installing. For example,
/usr/local/dlxs-13. This way you can create a private virtual host to develop under latest installed version while keeping an earlier version running in production under a public virtual host. Here is an extended treatment describing some ideas for this approach.
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 shell and Apache DLXS virtual host configuration. Virtual host configuration info follows below. Set DLXSROOT in the shell when running some DLXS command line scripts or the debugging the middleware at the command line.
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.
Untar the XPAT tarfile where you would like to store the XPAT executables. For example, /usr/local/
This directory should be included in your shell PATH environment variable. 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, Linux and a cdrom mount point of /cdrom:
% cd /l/local % tar xvf /cdrom/xpat_linux-5.3.2.tar
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 /l/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 /l/local % ln -s xpat-5.3.2 /l/local/xpat
There are several other binaries which you may need. Install these on your system as required for the Classes you plan to use.
Installation steps for these binaries are identical to those for XPAT.
c42pdf is not part of the DLXS distribution. Get it from http://c42pdf.ffii.org/ -- we are currently using version 0.12 for Linux.
We currently recommend you use the standard Perl 5.8.8 (or higher) release.
In addition, you'll need to install additional Perl modules. Get them 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 the additional Perl modules after installing the DLXS middleware.
Install problems? If, for any reason, the install is unsuccessful you can repeat the process. Simply delete the DLXSROOT directory (if it has been created) and run Installer again.
Using the example paths from the workshop:
cd /l1/INSTALL_CDROT/cd 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:
The Installer creates $DLXSROOT/web/cache 777 permissions. Optionally, you may want to change permissions on this directory to make it writeable only by the UID of the web server.
The $DLXSROOT/bin/managesessions.pl, $DLXSROOT/bin/manageportfolios.pl and $DLXSROOT/bin/managecache.sh scripts are typically run by a cron job to periodically expire user sessions, remove temporary ImageClass portfolios and maintain $DLXSROOT/web/cache at the desired size. An example crontab can be found in $DLXSROOT/bin/installer/config-examples/crontab.dlxs.
Examine $DLXSROOT/bin/installer/config-examples/httpd.conf.dlxs. You may integrate this segment into your Apache configuration file, adapting as necessary. The example 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"?>
Here is the 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 for the collmgr. If you disable this be aware that the collmgr requires some form of authentication which sets the REMOTE_USER environment 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.
Covered in this workshop page (next)..