This document covers the following topics:
When installing Adabas, the user ID under which you run the Software AG Installer must not be longer than eight characters. If you use a longer user ID, an error message is shown.
The user ID that you use to install the product must have full read and write permissions to the installation directory. In addition, it is helpful if the user has extended security privileges (sudo or su rights).
It is recommended that you use the user sag, for further information see Adding User Account for Administration of Software AG Products .
During the installation, the Sudo panel may appear. When you enter the sudo password in this panel, the installer will execute the scripts which require sudoers privileges. If sudoers privileges are not available you may run the script manually after installation as explained later in the section Final Installation Steps.
During the installation, you are asked to specify an installation directory in which to install your Software AG products. By default, the name of the main installation directory is /opt/softwareag.
The directory name should not contain embedded spaces. For further information, see Using the Software AG Installer.
You can install the same Adabas version more than once on the same machine. And you can also install several different versions of Adabas on the same machine. Each version, however, must be installed in a separate directory. You cannot overwrite an existing version, you can only uninstall it.
Choose for instance /opt/softwareag/Suite1 for the first installation and /opt/softwareag/Suite2 for the second one.
If several Adabas versions are installed on the same machine, any other Software AG products using Adabas must be installed into the directory where the specific Adabas version had been installed. As an alternative, you can create your own sagenv.new, which sets up the appropriate settings for other products installed in different libraries. This script can be called, for example, in the login script. Regardless of the option chosen, the Adabas SQL Gateway and Adabas Event Replicator must be installed in addition to each Adabas installation (for further information see Reinstall Adabas SQL Gateway and Adabas Event Replicator).
Adabas requires that every Adabas installation is licensed separately. The Adabas license has to be activated for each installation directory. For further information see Final Installation Steps.
The installation procedure generates the environment file called sagenv.new in the bin directory under the main installation directory. This script creates all environmental variables needed to run the Software AG products installed under the same main installation directory. It must be sourced before any of the products run.
Note:
If you schedule the automatic execution of a batch script, the
Software AG environment is usually not defined when the script is started.
Therefore, the script must first source the environment file before performing
any Adabas activities.
If systemd is enabled on Linux, it is possible to create an example systemd service file to start/stop an Adabas database on system start/stop.
For further information, execute Adabas/INSTALL/create_systemd_service_file.sh.
Note:
If you are using Adabas Manager to start/stop a database that is
under the control of systemd, systemd will not be aware this.
Adabas stores its configuration data and information about the available databases in a directory identifed by the environment variable ADADATADIR. In particular, if you use Adabas Extended Operations or the Adabas Manager, the descriptions of all databases to be accessed must be stored in ADADATADIR.
By default, ADADATADIR is the installation directory. If you install more than one Adabas version on the same machine, you will have to put those versions into different directories and therefore you will have several ADATADADIRs.
However, the database IDs used should be unique on the same machine. Moreover, the file ADABAS.INI located in $ADADATADIR/etc contains setup data that should be unique on your machine as well. Therefore, it is recommended to have all databases located in a directory common to all Adabas installations on the machine. A supplied script modifies the related environment file to let ADADATADIR point to such a common directory (for further information see Final Installation Steps).
Database IDs must be unique on the computer. In order to avoid double usage of database IDs it is useful to see all defined databases.
Typically you have installed an earlier Adabas version used for all databases. Then you install a higher version, and afterwards you want to convert the databases to the higher version. If you want to see which databases have already been converted, you must use the same ADADATADIR.
For this reason, a script is provided to change ADADATADIR.
As you move through the wizard, the installer stores some of the files it requires in a temporary directory. If you cancel the installer and later restart it on the same machine, the installer will use the stored files rather than downloading them from the installer server again, to improve performance. After a successful installation, the installer deletes the stored files.
If you cancel the installation before it has finished and if you want to remove already installed files, you have to do this manually. For further information, see Uninstalling Adabas.
The environment variables ADADATADIR and ADAPROGDIR are mandatory environment variables which must be defined for Adabas utilities. If either one or both is undefined, this will result in failure and Adabas utilities execution will end. Both environment variables ADADATADIR and ADAPROGDIR have a default value defined.