2.Installation

A.LDM Preinstallation Requirements

1.Platform Requirement:

UNIX workstations, PC platforms (running on Solaris x86 or Linux Redhat 7.0+). The following installation is based on UNIX workstations. We will install LDM in PC platforms in future.

2.Memory Requirement:

Depending on the platform, 256MB RAM is adequate.

3.Network Requirements:

3.1 Support for TCP/IP protocols
3.2 Access to the Internet

4. 3rd Party Software Requirements:

4.1 Complete installation of perl 5 version of perl is required.
4.2 A web browser for access to online LDM documentation and statistics.
4.3 An ANSI C compiler is needed for source code installation.
4.4 Installation of the network time protocol, ntp. In case you need to install ntp on your system, see http://www.eecis.udel.edu/~ntp/

5. Configuring the Operating System as root

• Add the following lines to file /etc/services
  ldm 388/udp unidata # UCAR Unidata LDM
  ldm 388/tcp unidata # UCAR Unidata LDM
  This allows programs such as netstat to associate activity on IP port 388 with the LDM.

• Add the following line to file /etc/rpc
  ldmd 300029 ldm

This allows programs such as rpcinfo to identify RPC program number 300029 as the LDM.

• The LDM uses the system logging daemon, syslogd, to write error messages by the local0 facility.
  Add the following entries to file /etc/syslog.conf
  o local0.debug /usr/local/ldm/logs/ldmd.log
  
  oMdify the following lines in file /etc/syslog.conf so that LDM messages will not be written to the console
  *.err;kern.notice;auth.notice;user.none;local0.none /dev/console
  o *.err;kern.debug;daemon.notice;mail.crit;user.none;local0.none /var/adm/messages
  

• Create the user account called 'ldm'
  By convention, the LDM home directory should be /usr/local/ldm or /home/ldm. If /home/ldm is used then a link needs to be made from /usr/local/ldm to /home/ldm, ie

% cd $HOME
% ln -s $HOME /usr/local/ldm

6. The User 'ldm' Account

• When installing the LDM, do not use root as the owner of the LDM files. Make 'ldm' the owner of the files.
  
• Use the C-shell for the LDM user account
  
• Use a common group ID to allow other non-LDM processes to write files (decoders, etc.)
  
• In the .cshrc file:
  setenv LDMHOME /usr/local/ldm
  Prepend $HOME/decoders to the environment PATH variable for the shell
  Prepend $HOME/util to the environment PATH variable for the shell
  Prepend $HOME/bin to the environment PATH variable for the shell
  Prepend $HOME/man to the environment MANPATH variable for the shell
  
• Make changes active, source .cshrc
  

  7. Creating the LDM Symbolic link directories
  

• Change to the LDM home directory
  
• Create links for the version-dependent subdirectories
  % cd ~ldm
  % ln -s runtime/bin bin
  % ln -s runtime/man man
  % ln -s runtime/src src
  % ln -s runtime/lib lib
  % ln -s runtime/include include
  

  8. Creating the Other Directories
  

  The etc/ directory contains configuration files for the LDM. As a general rule, these files do not change between minor version releases of the LDM. Also, you do not want to recreate these files after each upgrade.

% cd ~ldm
% mkdir etc

Decoders are not included with the LDM release, but are run by the LDM. By convention, the executables for the decoders are kept in a subdirectory called "decoders."

% cd ~ldm
% mkdir decoders

Other programs that might be used with the LDM, but that are either a decoder or part of the LDM distribution are, by convention, kept in a directory called "util."

% cd ~ldm
% mkdir util

9. Choose Type of Installation

There are two types of installation. One is binary LDM installation; the other is source code LDM installation. The following installation is based on binary LDM installation.

B. LDM Binary Installation

1.Obtain the LDM Distribution
The LDM binary distributions are available via anonymous FTP from ftp://ftp.unidata.ucar.edu/pub/binary/.

2. Unpack the Distribution in LDM Home Directory
% cd ~ldm
% zcat ldm.tar.Z | tar xvf -

This will create a version directory (e.g. ldm-5.1.2/).

3. Run the scriptconfig script
In {version-directory}/bin run the script scriptconfig to configure the perl scripts with location of perl, LDMHOME, and the fully qualified hostname.

% cd ~ldm/{{version-directory}/bin
% scriptconfig

4. Copy distribution configuration files
Copy the contents of {version-directory}/etc to ~ldm/etc

% cd ~ldm/{version-directory}/etc
% cp * ~ldm/etc

5. Make rpc.ldmd and hupsyslog suid root
Change permissions for rpc.ldmd and hupsyslog to be setuid root. This step needs to be done as root

% cd ~ldm/{version-directory}/bin
% chown root rpc.ldmd
% chown root hupsyslog
% chown root rpc.ldmd
% chown root hupsyslog
% chmod u+srwx,g+rx,o+rx rpc.ldmd
% chmod u+srwx,g+rx,o+rx hupsyslog

6. Change the runtime link
Install the runtime link

% cd ~ldm
% ln -s {version-directory} runtime

Create the LDM log file

% touch logs/ldmd.log

7. Start the LDM

• For a new LDM installation:

First create the queue: ldmadmin mkqueue

Then run: ldmadmin start

• For an existing LDM installation:

Just run: ldmadmin start

• At this point, the LDM should be running with the new release and the distribution configuration files. Because the configuration files: ldmd.conf and pqact.conf are not tailored for your site, no data will be arriving. The next step will configure the ldmd.conf and pqact.conf files.

8. Stop the LDM
Run: ldmadmin stop