This section provides you with the information necessary to install and to configure Adabas Manager on UNIX platforms.
The following main topics are described:
This section describes the prerequisites for installing Adabas Manager and how to perform the Adabas Manager installation on UNIX.
This section contains the following topics:
Before you start installing Adabas Manager make sure that you meet the prerequisites for your environment as described below.
For the installation of Adabas Manager, the following hardware requirements apply:
| Hardware Prerequisites for Linux | |
|---|---|
| Processor: | x86, EM64T and AMD64 (at least Intel Pentium III 300 MHz) |
| RAM: | 1GB |
| Disk space: |
Installing Adabas Manager requires approximately 85MB. |
| Drive: | A drive to install the software. |
For the installation of Adabas Manager, the following software requirements apply:
| Software Prerequisites for Linux | |
|---|---|
| Operating System: |
SUSE Linux Enterprise Server 10 (x86, EM64T, AMD64). |
|
Red Hat Enterprise Linux 4 and 5 AS (x86, EM64T, AMD64).
|
|
| Remote Access: |
Entire Net-Work Client 1.4 or above is required for remote access to mainframe machines. |
Note:
It is recommended to use the file system ext3 on Linux.
For the installation of Adabas Manager, the following hardware requirements apply:
| Hardware Prerequisites for IBM zLinux | |
|---|---|
| Architecture: | IBM zSeries (s390x) |
| RAM: | 1GB |
| Disk space: |
Installing Adabas Manager requires approximately 85MB. |
| Drive: | A drive to install the software. |
For the installation of Adabas Manager, the following software requirements apply:
| Software Prerequisites for IBM zLinux | |
|---|---|
|
SUSE Linux Enterprise Server 10 |
|
| Operating System: |
Red Hat Enterprise Linux 4 and 5 AS
|
| Remote Access: |
Entire Net-Work Client 1.4 or above is required for remote access to mainframe machines. |
In this section the following is assumed:
The user account for the administrator of Software AG products is called "sag".
The group to which the administrator and all users of Software AG products are assigned is called "sag".
The home directory for the user "sag" is /opt/softwareag.
The root directory for Software AG products is /opt/softwareag.
To perform these steps, use an appropriate system administration
tool (e.g. smit).
Create one administrator's account and one group for all Software AG products when you install your first Software AG product.
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 for the Bourne shell, this shell is required as the login shell for the administrator account.
Define a group to which the administrator and all users of Software AG products belong.
Create a login directory for the user "sag".
It is assumed that user and group accounts are defined in the respective files in /etc.
The following is a possible entry in the system file /etc/group:
sag:*:21:sag
The following is a possible entry in the system file /etc/passwd:
sag::100:21:SAG - Product Administrator:/opt/softwareag:/bin/sh
SAG
environment variable
The environment variable "SAG" defines the default location under which the directory trees of installed Software AG products are located. In the Bourne shell you can define it like this:
SAG=/opt/softwareag ; export SAG
The Adabas Manager software will be installed in, and under the subdirectory ama of the location specified by $SAG.
Once you have set up your installation environment as described above, you can proceed with the installation itself.
Important:
Before you start the installation, read the
install.txt on the distribution medium and ensure that all
prerequisites for the installation have been satisfied.
The installation procedure examines the environment variable
DISPLAY to determine whether to run in graphical
or interactive text-oriented mode. If the environment variable
DISPLAY points to an active X-Server, the
graphical installation mode starts, otherwise the interactive text-oriented
installation mode starts. There is also a batch mode available (see
Batch Installation for further
information).
Note:
If you run the installation procedure in character mode, at each
command prompt, you must type in the exact wording (for example:
"accept" for "accept", not just
"y" or the ENTER key).
To set the DISPLAY environment
variable
Enter the following shell commands (this example is for Bourne shell):
DISPLAY="<machine_name>:0" export DISPLAY
replace "<machine_name>"by the name of your terminal device.
Note that the graphical mode can only start if there is an X-Server currently active.
To install the Adabas Manager product
To perform this step, you must be the user "sag" with "su" or "sudo" privileges.
You need to have superuser permissions for some parts of the installation procedure. You can choose between entering the password of the root user and entering your own password if the third party tool "sudo" is installed and configured.
Mount the distribution medium (in the following it is assumed that the mountpoint is "/cdrom").
Start the installation procedure from a writable working directory.
Enter the command:
/bin/sh /cdrom/setup.ux
The setup program is started and guides you through the installation.
Since Linux S/390 systems usually do not have a drive, it is necessary to perform the following preparations prior to the actual installation:
To copy the distribution medium contents to a zLinux system and
prepare the installation
Load the distribution medium on a Windows or UNIX machine that has a network connection to the zLinux system.
Copy the file AMA774n.tgz that is located in the root directory of the distribution medium to a temporary area such as /tmp/cdrom in your zLinux environment, using for example ftp in the binary mode.
Unpack the tgz file using the command
tar -xzvf AMA774n.tgz, where "n" is the number of
the Adabas Manager patch level. Now follow the
subsequent instructions for the main installation process.
To install the Adabas Manager product on a zLinux system
To perform this step, you must be the user "sag". Do not perform this step as the user "root".
Start the installation procedure from a writable working directory. We recommend $SAG/INSTALL.
Enter the command:
sh <AdabasManagerRoot>/setup.ux
The setup program is started and guides you through the installation.
If you install the product in character mode, the option
-batch can be used to execute the installation program without
further user interaction. If user input is required, the default values are
used; if these values are not appropriate, the correct values have to be set
using the corresponding options in the command line. The available command line
options can be displayed by calling the installation program with the
-help option.
 |
Warning: Since the value of $SAG cannot be set using an option, it must already have the correct value in the calling shell. |
When Adabas Manager is installed, a script $SAG/ama/v774/INSTALL/AMAv774Inst.sh is created, which can be modified and then used for batch installation.
All prerequisites and parameters are checked for correctness: missing or invalid values will cause the batch installation to terminate.
Installation programs that require post-installation actions executed as a system administrator usually have the following three options:
| Variable/Flag Name | Type | Value | Explanation |
|---|---|---|---|
| -user | string | ( ) | Software AG administrator |
| -password | string | ( ) | System administrator password (usage not recommended) |
| -authcmd | string | (none) | System administrator user or command |
It is possible to specify a password for the system administrator (or the user's password in connection with -authcmd sudo) as value of the -password option; however, this should be avoided for security reasons. The password would appear as readable plain text on screen, or be stored in the calling shell script, or, in the worst case, be stored in the user's shell history file. It may also be looked up with ps -ef during the installation's runtime by every user on the system.
# Unsafe, because everyone can see the password: sh /cdrom/setup.ux -batch -authcmd sudo -password secret
It is recommended to start the installation program using su or sudo, specifying the name of the administrator for the Software AG products as value of the -user option:
# Recommended way to start the installation with super user # permissions: su root -c "sh /cdrom/setup.ux -batch -user sag"
This example shows a generated batch file AMAv774Inst.sh that was created during installation. The user is sag and does not have a root login on the machine (-authcmd none)
#!/usr/xpg4/bin/sh
# ----------- <Start of generated batch script> ----------
# -- <Adapt the following lines until end of generated> --
# ------------ < batch script to your needs > ------------
#
# Please consult the installation documentation for the
# necessary prerequisites.
#
# Make sure that the following Internal Products are installed
# below the same $SAG, before the batch is actually started.
# - arg v812 "System Management Hub"
# You will find the batch scripts for the other installations
# in the respective INSTALL/ directories of the products.
#
# You should replace SECRET by the actual password
# or (even better) call this script with superuser privileges.
#
SAG="/opt/softwareag"; export SAG
/bin/sh /cdrom/setup.ux ama v774 -batch -directory a64b \
-user sag \
-authcmd none \
-password SECRET \
-sagenv /opt/softwareag/sagenv.new \
-packages "" \
-products "
cjp v16 : on
ctp v80 : on
adi v541 : on
acl v6315 : on
ada v63002 : on
wcl v140 : on
wcb v110 : on
ama v774 : on"
To run an installation of Adabas Manager for administrating only local databases on Open Systems with batch scripts, the following steps must be executed:
sh CJPv16Inst.sh su root -c "sh CTPv80Inst.sh" (or sudo sh CTPv80Inst.sh) su root -c "sh ARGv812Inst.sh" (or sudo sh ARGv812Inst.sh) sh AMAv774Inst.sh
To run a full installation with batch scripts, the following steps must be executed:
sh CJPv16Inst.sh su root -c "sh CTPv80Inst.sh" (or sudo sh CTPv80Inst.sh) su root -c "sh ARGv812Inst.sh" (or sudo sh ARGv812Inst.sh) sh ADIv541Inst.sh sh WCLv140Inst.sh sh WCBv110Inst.sh sh AMAv774Inst.sh
Note that CTP and ARG must always be installed with root privileges. ADI and WCL must be installed with root privileges if they are installed as system services.
Note:
The SAG environment defined in sagenv.new must always be
set before the execution of each script, i.e., the command .
sagenv.new must be executed in a shell which is compatible to the
Bourne Shell. When the installation has completed, the SAG environment must be
set and the System Management Hub must be restarted
using the command: argsrvs.bsh restart.
This section contains information about what to do after the actual Adabas Manager installation. For a summary of bug fixes, known problems and restrictions and last-minute news please see the README.TXT file, which has been copied to $SAG/ama/vnnn. The contents of this file are displayed automatically after the basic component has been installed.
This section contains the following topics:
By convention, a link to a lock file (install.lock) is written to $SAG during the installation in order to prevent parallel installation into $SAG at the same time.
This link remains if you accidently close XWindows sessions, or if you end your installation/uninstallation process with a kill command.
You must remove this link, because as long as this link exists it is not possible to install into this $SAG or uninstall. Before you remove install.lock make sure that the process on the machine mentioned in the link no longer exists.
The link below contains the current user, host ip address and process id.
lrwxrwxrwx 1 sag sag 22 Feb 12 10:25 install.lock -> sag@10.20.96.151:26372
Verify your Adabas Manager installation by registering an Adabas database.
To verify your Adabas Manager installation
for administrating databases on mainframe:
From a web browser, logon to System Management Hub at http://"<hostname>":49981/smh/login.htm.
The logon screen for the System Management Hub (SMH) appears.
Logon to the System Management Hub...
The System Management Hub main panel appears.
Select the name of the managed host on which Adabas Manager is installed.
Expand the tree-view frame for the managed host by clicking the plus sign (+) to the left of its name.
Expand the tree-view for Adabas Manager.
Right-click Adabas Databases in the tree-view.
Select in the drop-down menu.
The Database Registration panel appears in detail-view.
Enter the ID and name of the database to be registered.
Click to complete the registration, or the button to quit the registration window without registering the database. Press the button for more information about registering a database.
Note:
If the database is currently unreachable, you will be prompted to
verify that you still want to register it.
If you clicked , a message is eventually returned indicating that the database has been successfully registered. The database appears as an option in tree-view.
Click in detail-view to complete the transaction.
To verify your Adabas Manager installation
for administrating local databases on open systems :
Note:
Before you verify your installation, ensure that the
prerequisites listed in the install.txt on the
distribution medium have been met.
From a web browser, logon to System Management Hub at http://"<hostname>":49981/smh/login.htm.
The logon screen for the System Management Hub (SMH) appears.
Logon to the System Management Hub...
The System Management Hub main panel appears.
Select the name of the managed host on which Adabas Manager is installed.
Expand the tree-view frame for the managed host by clicking the plus sign (+) to the left of its name.
Expand the tree-view for Adabas Manager.
Right-click Adabas Databases in the tree-view.
Select in the drop-down menu.
The Create New Database panel appears in detail-view.
Enter the ID of the database to be created.
Click and check Load Demofiles.
Click to create the database
Expand Adabas Databases and right-click the new database you have just created..
Select Start Database.
The detail-view panel displays a message that the database has been started successfully. Confirm and return to the Database Overview information.
If Adabas for Open Systems has been installed on a UNIX platform but
the functionality cannot be reactivated, the system may issue the following
error message: Adabas is not installed on this
system.
The following steps will solve the issue:
Open the script ${SAG}"/common/arg/bin/argsrvs.bsh in a text editor.
Find
. ${ARGDIR}"/INSTALL/argenv > /dev/null
and replace with
. ${SAG}"/sagenv.new >
/dev/null.
Adabas Manager can now be activated.
In order to uninstall AdabasManager on UNIX platforms, perform the steps that are described in the following section.
Start the SAGRM utility from the $SAG directory by issuing the
sagrm command.
For more detailed information please see the install.txt on the distribution medium.
