Installing and Setting Up Software AG Products under UNIX

This document contains general information which applies when installing and setting up any Software AG product on a UNIX platform. The following topics are covered:


General Information

Installation Package

The installation package containing Software AG products is provided on a CD-ROM conforming to the ISO 9660 standard.

The CD-ROM contains a complete directory structure which clearly specifies product and platform.

Software AG Environment

The following figure shows the general directory structure generated during installation and the environment variables which reference the specified directories:

graphics/ux-install-common-sagenv-new.png

The environment variable $SAG defines the root directory for all Software AG products. It is recommended to define SAG=/opt/softwareag.

Note:
If you want to use applications with S-bit, which call Adabas, it is required to define SAG=/opt/softwareag.

For each product, the variable $prodDIR is set to the path of the main directory of the product specified, where prod is a three-letter product code in upper-case letters. For example, all files for Natural, whose product code is NAT, are contained in the directory $NATDIR.

However, there are exceptions to this convention. For example, the product code for Predict is "PRD" but the environment variables use the prefix "DIC" instead.

The name of the main directory is usually the same as the product code in lower-case letters. For example, the main directory for Natural is named nat.

Version-independent parts of the product, such as examples or data, are stored in a subdirectory of the product main directory.

Version-dependent components of the product are kept in the version directory $prodDIR/$prodVERS. For example, the current version of Natural is stored in the directory $NATDIR/$NATVERS.

The environment variables prodDIR and prodVERS for all products specified during installation are defined in the file sagenv.new. The same applies for any other environment variables needed for the various products.

Multiple $SAG Environments on the same Machine

If you want to install more than one $SAG environment in parallel on the same machine, you should consider the following points:

  • In this case, no $SAG must be set to /opt/softwareag.

  • /opt/softwareag must not be defined as a link to one of the $SAG.

  • It is not possible to use applications with S-bit, which call Adabas.

  • The $SAG environments are not completely independent, in particular, it is not possible to start Adabas databases with the same database ID from different $SAG environments in parallel.

Before Installing your Software AG Product

It is recommended that you use /opt/softwareag as one common root directory for all of your Software AG products. For Linux systems, this location is the registered name with LANANA.

The default search path for dependent libraries of some Software AG products is /opt/softwareag. They are loaded from this location or using the environment variable $LD_LIBRARY_PATH ($SHLIB_PATH on HP-UX systems). If you install the product to a different location (for example, /usr/SAG instead of /opt/softwareag), you may create a symbolic link to your $SAG directory to get a valid default search path:

su
cd /opt
ln -s $SAG softwareag

The following activities must be performed if you are installing a Software AG product for the first time, or if your environment is not yet set correctly due to any other causes.

This section covers the following topics:

Creating the Administrator's Account and Group

You must create one administrator account and one group for all Software AG products when you install your first Software AG product.

  1. Define an administrator account to which all of the Software AG products installed at your site belong. Since all environment definition files for the products are written in Bourne shell syntax, the Bourne (or Korn) shell is recommended as the login shell for the administrator account. This section assumes that the administrator account is called "sag".

  2. Define a group to which the administrator belongs. This section assumes that this group is also called "sag".

  3. Create a login directory for the user "sag".

  4. Add the group "sag" in the system file /etc/group and the user "sag" in the system file /etc/passwd.

Note:
To perform these steps, use an appropriate system administration tool.

Backing Up Your Current Product Version

When upgrading a product, it is strongly recommended that you back up your current product version.

Logging in as User "sag"

This description assumes that the user "sag" is the administrator for Software AG products. Log in as the user "sag" (it is not recommended to log in as "root").

Installing the Contents of the CD-ROM to Disk

Before performing the following steps, make sure that the administrator user and group have been created and defined.

Start of instruction setTo install the contents of the CD-ROM to disk

  1. Load the CD-ROM in the CD-ROM drive and mount it if this is not done automatically.

    Command Description
    su - root
    To mount a CD-ROM you may need to be root.
    mkdir /mount-dir
    You may need to create a mount directory for the CD-ROM.
    mount platform-specific_mount_options device-name /mount-dir
    Execute the mount command (see the table below for operating system-specific mount commands).
    exit
    Return to "sag" user.

    Platform-specific mount command and options to mount the CD-ROM as ISO9660 or High-Sierra file system:

    Platform Mount Command
    AIX
    /usr/sbin/mount -F cdfs -o cdcase device-name /mount-dir
    HP-UX
    /usr/sbin/mount -F cdfs -o cdcase device-name /mount-dir
    Solaris
    /usr/sbin/mount -F hsfs -o ro device-name /mount-dir
    Linux (IA-32)
    /bin/mount -t iso9660 -o ro device-name /mount-dir

    Note:
    On Solaris, the volume management daemon vold might be active. This daemon mounts the CD-ROM automatically.

    Example for Linux:

    /bin/mount -t iso9660 -o ro /dev/cdrom/mnt
  2. Check the directory structure of the UNIX part of the CD-ROM. When you run an ls(1) command on the CD-ROM, you will see a structure like the following:

    graphics/ux-install-common-cdrom.png

    Note:
    Depending on the mount options used, the files will be all upper case or all lower case. If you mount the CD-ROM as a pure ISO 9660 Interchange Level I CD, you will also see a version number ;1 appended to all files. Please note this for the following steps and use the correct name format.

  3. For Linux S/390 the file ASGv231n.tgz is provided for your convenience. The following steps can be performed after you have loaded the CD-ROM on a Windows or UNIX machine that has a network connection to the Linux S/390 system:

    1. Copy the file ASGv231n.tgz that is located in the root directory of the CD-ROM to a temporary area such as /tmp/cdrom in your Linux S/390 environment, using for example ftp in binary mode.

    2. Unpack the tgz file using the command tar -xzvf ASGv231n.tgz, where n is the number of the patch level.

    3. Read the installation instructions for details on how to start the installation from this media in the file setup.txt in this directory. Instructions of how to proceed after installing the software will be displayed at the end of the installation and also copied onto your hard disk.

  4. Please continue reading the step-by-step installation instructions for the Software AG product being installed.