This document covers the following topics:
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 this documentation.
For you to use sudo in the installer, the user that you are using to install must be in the sudoers configuration. If you are creating or installing from an installation script, the installer cannot execute the script because it does not store the sudo password for security reasons. You must therefore execute the script manually after the installation.
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. You can then exit the installer and use a different user ID or - in case you also want to install other products - return to the product selection tree and deselect Adabas.
During the installation, you are asked to specify an installation directory. Specify the installation directory in which to install your Software AG products. By default, the name of the main installation directory is /opt/softwareag.
The user that you are using to install must have full read and write permissions to this directory.
Adabas requires an Adabas Data Directory (ADADATADIR) for storing information on the Adabas configuration and the available Adabas databases. In particular, if you use Adabas Extended Operations or the Adabas Manager, it is required that the databases to be accessed are described in ADADATADIR.
Per default, ADADATADIR is the installation directory. If you install more than one Adabas version, you have different installation directories. Using the installation directories as ADADATADIR would mean that you have different ADADATADIRs. However this is usually not desirable, because then the databases defined for one version are not visible for the other version. This has the following disadvantages:
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.
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. This may be necessary to test a new Adabas version before it is taken over into a production environment.
Each version, however, must be installed in a separate directory. That is, when Adabas is already installed in the default main directory /opt/softwareag, you can install a second instance of Adabas, for example, in a directory named /opt/softwareag2.
Since Empower only offers the latest version of Adabas and other products, it is recommended that you create and keep an image of installed Adabas versions for possible later use. Installing from an image rather than downloading it from Empower will usually be faster, too. For further information, see Using the Software AG Installer.
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.