Step 2: Installation

First-time installation

To get a feel for ClearDDTS, you can install the product to test its features, but you should return to the planning step before you are ready to implement your live version. To install ClearDDTS:

1. Follow the directions in Chapter 1, Installing ClearDDTS, in the ClearDDTS Installation and Licensing Guide. Specifically:
• downloading the product materials from the CD-ROM
• running the installation script ddtsinstall (have your license certificate ready)
• modifying your HTTP server configuration to recognize the location of the ClearDDTS CGI scripts (you must have an HTTP server configured and running to use the web interface to ClearDDTS)
  
2. Do not complete the section of Chapter 1 entitled "Checking the Installation and Informing New Users" until you complete any customizations you have planned, unless you are only evaluating the product.

Upgrading from a previous release

To upgrade from a previous release:

1. Gather information about customizations you have made to your current installation.
2. Back up your current installation to tape or another safe storage area.
3. Follow the directions in Chapter 2, Upgrading from a Previous Release, in the ClearDDTS Installation and Licensing Guide.
4. Read the Release Notes files for important changes to ClearDDTS.
5. Verify that your customizations have been carried forward to the new installation (or are no longer necessary).
6. After upgrading, thoroughly test your new version of ClearDDTS to make sure it works properly before you delete the OLDCLEARDDTS directory. With ClearDDTS 4.0, you may also need to make some additional customizations to the master.tmpl file to optimize the new webddts interface.

Multiple installations

If you have multiple installations, consider whether they are on the same or different networks. To have multiple installations under the same NIS server:

1. Designate one installation as the global, or default, ClearDDTS server. This installation should be listed in the NIS map. Simply install this site as usual following the steps in Chapter 1, Installing ClearDDTS, in the ClearDDTS Installation and Licensing Guide.
2. Before installing at subsequent sites, make an entry for ddts in that machine's local /etc/passwd file. This entry must use the same user and group ID as the global/default ClearDDTS user ID listed in the NIS map, but should specify a different home directory from the global ClearDDTS user ID.
3. Install this second and subsequent sites following the steps in the ClearDDTS Installation and Licensing Guide. Be sure to perform all operations on the second machine in the home directory of the local ddts user.

Sharing a common mail spool

If you share a common mail spool (NFS mounted), all servers will try to read the mail spool at the same time, causing contention. To fix this, redirect all incoming mail for one of the "ddts" users to another userid (say, ddtstest). This new user account "ddtstest" is a pseudo user and is only used to resolve the incoming mail folder conflict. Create the new account by creating a user account 'ddtstest' with the same uid and gid as the user ddts on the same machine.

After configuring one of the "ddts" users to read incoming mail from the pseudo account "ddtstest", inform ClearDDTS to expect incoming mail from /usr/spool/mail/ddtstest, instead of /usr/spool/mail/ddts. The daemon that reads incoming mail is mail.in. The method by which you inform mail.in to read incoming mail from an alternate mailbox depends on the version of ClearDDTS you are using (use the command whichddts to determine the installed version).

[Version 3.1]

First, rename mail.in to mail.in.bin. Then write a shell script called mail.in, which contains the following:

#! /bin/sh
<path to ddts_home>/bin/mail.in.bin -b /usr/spool/mail/ddtstest

Then run chmod +x on mail.in.

[Version 3.2 and later]

In version 3.2 and later, you can create a file called conf/mailfile that specifies which mailbox to use. For example, the file would contain just one line:

/usr/spool/mail/ddtstest

Issues

Redirecting mail raises two issues:

• Any errors that are meant for the second system will still be sent to the first system.
• If the two sites have to be connected, it will be difficult.

You can fix this by reconfiguring sendmail to rewrite the Sender and Recipient fields for ClearDDTS. This is done by adding the following to the sendmail.cf file on the second ClearDDTS server (note that the white space on these lines MUST BE tab characters):

# Sender Field Pre-rewriting
S1
Rddts	$@ddtstest
Rddts<@testmach>	$@ddtstest

# Recipient Field Pre-writing
S2
Rddts	$@ddtstest
Rddts<@testmach>	$@ddtstest

Note: If the two "ddts" users do not have the mail spool nfs mounted, then you only need to do one thing: prevent ClearDDTS from being aliased for mail going to that second machine. You can do that by changing the sendmail.cf file on the mail host and adding the following line to ruleset 1:

Rddts<@testmach> $@ddts<@testmach>

Please note that a tab (NOT spaces) should be used as the white space between the lines:

"Rddts" and "$@ddtstest" && "Rddts<@testmach>" and "$@ddtstest". 

[TOC] [Step 1: Planning] [Step 2: Installation] [Step 3: Customization] [Step 4: User Access] [Step 5: Distribution]