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 install:
Installer only installs the middleware not the open source binaries or XPAT binaries
There are 3 parts to installing DLXS:
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.
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.2.3, Sun Solaris and a cdrom mount point of /cdrom:
cd /usr/local
zcat /cdrom/xpat-5.2.3/xpat_solaris_5-2-3.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.2.3 /usr/local/xpat
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 and mrsid_retrieve are identical to those for XPAT.
XPAT and tif2web are part of the DLXS distribution. Obtain the others as follows:
We currently recommend you use the standard Perl 5.8.0 release.
In addition you'll need to install additional modules which can be obtained from CPAN.
There is currently an unresolved issue related to SQL::Statement and its existing versions 0.1021 and 1.005.
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. Only those not in the standard distribution need to be fetched from CPAN.
You may see Installer complain about an already installed Perl module due to dependencies it has on other not yet installed Perl modules. These will go away when all reported Perl modules are installed.
NOTE: Socket and Net ::hostent are used directly by Installer and must be available in order to run Installer.
With these 2 exceptions you may run the Installer without obtaining the additional modules so long as you fetch and install them before running the DLXS middleware.
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:
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.
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.
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.
For initial installations, if you chose MySQL for your database, use $DLXSROOT/bin/db/dbmove to move the sample CSV database into your MySQL database before you try to run the sample data. This assumes you've configured a MySQL database as described in the MySQL database configuration documentation.
If you are installing DLXS for the first time, conversion is not an issue.
If you have a Release 9 DLXS installation an upgrade utility called upgrade_2_3 in DLXSROOT/bin/db can be used to update your version 2 database to version 3. See documentation on database functionality for complete instructions
If you have a Release 8 DLXS installation an upgrade utility called upgrade_1_2 in DLXSROOT/bin/db can be used to update your version 1 database to version 2. See documentation on database functionality for complete instructions
If you have a DLXS installation that predates release 8, a conversion utility, called dbconv in DLXSROOT/bin/db can be used to capture the data in your existing colldb files and merged into the CSV tables located in DlXSROOT/misc/db. See documentation on database functionality for complete instructions.