This document provides you with the information necessary to install and to configure Adabas on Windows platforms.
The following main topics are described:
This section describes the prerequisites for installing Adabas and how to perform the Adabas installation on Windows.
The installation procedure uses the standard InstallShield mechanism.
If for any reason you wish to stop the installation procedure before it has completed, you can choose .
This section contains the following topics:
Before you start installing Adabas make sure that you meet the prerequisites for your environment as described below.
Caution:
On Windows server operating systems, you can switch on 'Disk Write
Caching'. This may increase the operating system performance, but it is
strongly recommended to use it only for disks with a backup power supply,
because otherwise it may result in a corrupted database.
For the installation of Adabas, the following hardware requirements apply:
| Hardware Prerequisites for Windows | |
|---|---|
| Processor: | x86 or x86-64 |
| RAM: | 2GB |
| Disk space: |
Installing the optimized version of Adabas requires approximately 75MB. An additional 25MB are required if you install the trace version of Adabas. These figures do not include disk space requirements for other databases that you will create. |
| CD-ROM drive: | A CD-ROM drive to install the software. |
Note:
The RAM size given in the hardware prerequisites only applies if you
do not intend to use LOBs. For LOB processing, you need at least four times the
size of the LOB data concurrently accessed. However, it may happen also with
this memory size that large LOBs cannot be processed because of memory
fragmentation.
For the installation of Adabas, the following software requirements apply:
| Software Prerequisites for Windows | |
|---|---|
| Operating System: |
Adabas Version 6.3 is available for the following Windows platforms:
|
We suggest that you install all of the manufacturer's recommended patches before you start the installation - there should be no open critical patches.
If you have fulfilled the prerequisites as described above, you can proceed with the installation itself, which will only take a few minutes.
To perform the installation, you must be logged on as a user with administration rights.
To start the installation, insert the CD-ROM into the CD-ROM drive. If the Windows Autorun mode is active (this is the default), the installation procedure will ask you whether you want to run setup.exe or not. If Autorun mode is not active, you can install manually by running setup.exe in the root folder of the CD-ROM.
Also, the CD-ROM should not be removed from the CD-ROM drive until the installation is finished.
The Adabas installation offers the three installations "Typical", "Compact", and "Customized". "Typical" performs a complete installation (including the examples, DBA Workbench and the documentation). If you select "Compact", Adabas will be installed with just the nucleus, the utilities, the adabas client, DBA Workbench and the examples. The "Customized" installation allows you to select the components you wish to install. "Customized" scenarios include just the nucleus and the Adabas client only (the absolute minimum configuration), the nucleus, the Adabas client and the DBA Workbench, or just the nucleus alone (when installing a new patch level). You should also choose Customized if you want to install the trace version of Adabas. If you choose not to install one or more units during the installation procedure, you can add them at a later stage by re-running the Adabas installation procedure. Note that the installation procedure does not check which units are already installed.
Notes:
On a server operating system such as Windows Server 2008, you may have more than one DBA, and only DBAs should have access to the database directories and be allowed to execute Adabas utilities. You can achieve this as follows:
Create a user group, for example adadba, and include all adabas DBAs.
Modify the permissions of the ADADIR folder:
Add the group adadba with full control permissions.
Deselect the inheritance of permissions from the object's parent in order to disable the permissions for other users, then remove all unwanted users who inherited permissions.
On Windows 7 and Windows server 2008, there is a separate ADAPROGDIR folder, you should modify the permissions for this folder as follows:
Add the group adadba with read and execute permissions.
Deselect the inheritance of permissions from the object's parent in order to disable the permissions for other users, then remove all unwanted users who inherited permissions.
In some cases, you may have the situation in which DBAs are only allowed to maintain a subset of the Adabas databases. If this is the case, you should proceed as follows:
Create user groups for the administration of the different groups of databases, for example adadbatest and adadbaprod for the administration of the test and production databases, and include all Adabas DBAs that are allowed to administrate the corresponding databases.
After you have created a database, modify the permissions of the database folder in ADADIR:
Add the relevant group with full control permissions.
Deselect the inheritance of permissions from the object's parent in order to disable the permissions for other DBAs, then remove the group adadba.
When a new database is created, the database folder and the files stored in it inherit their permissions from the parent folder, and the user that created it has full control of the files in the database folder. If you don’t change the permissions, all users that belong to the group Users usually have the permission to create new files, and read permission for existing files in the folder. In addition, administrators have full control. However, note that there is different behavior between older Windows operating systems, such as Windows XP, and the newer operating systems Windows 7 and Server 2008: on the old operating systems, administrators automatically had administrator rights, but on the new operating systems they don’t have administrator rights by default, except when they run an application as an administrator. This has the following consequences:
On the old operating systems, it is not a problem for administrators to start a database created by another user.
If you start a database created by another user on one of the new operating systems, the database is started as a read-only database.
For Windows operating systems prior to Windows 7, both program files and data files are installed below the same folder, ADADIR. This folder can be specified only in a customized installation when you install the first Adabas version on the system; if another version of Adabas is already installed, the new Adabas version is installed below the same folder that is already used for the existing Adabas version.
This has been changed on Windows 7 because with Windows 7, administrator rights are required to write in the program files folder: program files are installed by default below the folder %ProgramFiles%\Software AG\Adabas, now referenced as ADAPROGDIR, and data files are installed by default below the folder %ALLUSERSPROFILE%\Software AG\Adabas, now referenced as ADADIR.
Notes:
The Adabas kit contains several example files. These files include both input data for creating and loading the demo files, as well as sample programs for accessing this data and for user exits and hyperexits. Please refer to the following sections for further information about the example files:
Appendix A - Example Utility Input Files in Utilities
Appendix D - Example Files In The Adabas Kit in Command Reference
Adabas utilities and the nucleus can be executed by non-administrator users.
Note:
If you are an administrator on Windows 7, you should not run utilities
including the DBA Workbench or the nucleus as administrator. If you do so, any
files generated by the nucleus or utilities can no longer be processed without
administrator rights.
By default, previous installations of Adabas on Windows platforms installed all files in the Program Files folder. Because Adabas also writes into some of these files, you can only continue working with Adabas in the XP compatibility mode. Upgrading to a new Adabas version is not possible.
We therefore recommend that you proceed as follows:
Create a backup of all your databases with ADABCK
Delete the databases
Uninstall Adabas
Upgrade to Windows 7
Install Adabas
Recreate the databases with the Adabas Workbench
Restore the databases with ADABCK
Continue working with the databases
To uninstall Adabas, use the standard feature in the Windows Control Panel. In the list of installed programs in the Add/remove Programs feature, Adabas appears as Software AG Adabas n.n.n.n, where n.n.n.n is the product version number.
The Adabas client package that appears as Software AG Adabas ClientPackage n.n.n.n has to be uninstalled separately.
