Installing the AE - UNIX

The following steps will help you install the Automation Engine on UNIX.

Notes:

This page includes the following:

Requirements

When using an Oracle Database

Platform specific three-character codes for UNIX

Each supported UNIX variant is assigned a three-character code. This code appears in all of the agent's file names and is explained below:

UCXJSSVA

SSV = System ID and Version
A = Task (only for messenger program and CallAPI)

System ID and Version Hardware, Operating System, Version

D..

UNIX - DEC OSF

DA4 Alpha - DEC-OSF/1 - Digital UNIX - Tru64 UNIX
H.. UNIX - HP-UX
HP1 HP Workstation (9000), HP-UX

HI6

rx2600 machine with Itanium, HP-UX

A..

UNIX - IBM AIX

A64 Power PC64, AIX
AP6 Power PC, AIX
L.. UNIX - Linux
LI3 Intel, Linux

LI6

Itanium, Linux
LX6 Linux (x64)

LZ3

zSeries, zLinux
LZ6 zSeries, zLinux 64bit
C.. UNIX - SCO
CI5 Intel, SCO-UNIX ODT
CI7 Intel, SCO Unixware
U.. UNIX - Sun OS (Solaris)
U64 Sparc64, Solaris
US8 Sparc, Solaris
UI8 Intel, Solaris
SI6 Intel 64 bit (x64), Solaris

In this document, the specific code is replaced by the characters "???." This document describes the installation of the Automation Engine for Oracle databases.

Install the AE

Oracle Databases

  1. Log on as AE.
  2. Create a new directory: /opt/automic/server.
  3. Transfer the ucs???.tar.gz file from /cdrom/cdrom0/<version>/AutomationEngine/unix/<platform> with ftp (binary) to the created directory.
  4. Unpack the tar file using one of the following commands:
    gzip -d ucs???.tar.gz
    gunzip ucs???.tar.gz
    tar xvf ucs???.tar
  5. Set the environment variables in $HOME/.profile  if the Automation Engine does not run on the same computer as the utilities. For more information, see Installing the Utilities - UNIX.
  6. Rename the ucsrv.ori.ini file to ucsrv.ini:mv ucsrv.ori.ini ucsrv.ini
  7. Adjust the INI file of the Automation Engine to your system environment ,see Automation Engine. The following list shows the INI file entries which must be adjusted in all cases. All other parameters can be configured as needed.
  8. Remove the AE IMAGE:
    umount /cdrom     or eject cdrom
  9. Check the libraries:

    • AIX:

      1. Check the Oracle library libclntst*.a.
      2. Library check:
        dump -X64 -H ucsrvcp > wk.txt         (use a blank after "dump").
      3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
      4. Repeat the above procedure with ucuoci.a and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.a, because it is a library instead of a main program. If these messages refer to the libraries ucuoci.a, libzu00132.a and libucudb32.a, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

    • HP-UX:

      1. Check the Oracle library libclntsh.so.*.0.
      2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd.
      3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
      4. Repeat the above procedure with ucuoci.sl and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.sl, because it is a library instead of a main program. If these messages refer to the libraries ucuoci.sl, libzu00132.sl, or libucudb32.sl, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

    • Linux, Solaris and zLinux:

      1. Check the Oracle library libclntsh.so.*.0.
      2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd.
      3. Open this file with a text editor (sed or vi). Verify that all libraries were found.
      4. Repeat the above procedure with ucuoci.so and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.so, because it is a library. If these messages refer to the libraries ucuoci.so, libzu00132.so, or libucudb32.so, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

      For more information, see Preparing the AE Database - Oracle).

DB2 Databases

Install the AE SNMP Subagent (Optional)

(Server computer). You may want to install the AE SNMP subagent to monitor the various conditions which occur within an AE system (e.g. availability of the Automation Engine and agents, active notifications or blocking tasks). For more information, see Installing the Automation Engine SNMP Subagent (UNIX).

Start the Automation Engine

Manually start the Automation Engine for a test. (Server computer).

  1. Log on with the AE User ID.

  2. Change to the installation directory of the executable programs:
    cd $UC4/bin

  3. Start the communication process in the background:
    ./ucsrvcp &

  4. Start the work process in the background:
    ./ucsrvwp &

  5. Verify that the Automation Engine is running:
    ps -ef|grep ucsrv or ps -fu uc4

  6. It should now be possible to log on to the active Automation Engine with an AWI. The relevant information about the running Automation Engine is available in the Administration perspective.

Shut Down the Automation Engine

(Server computer). Use the ServiceManager to start and end server processes. For more information, see ServiceManager and Start Parameters - ServiceManager.

Shutdown

Cancel

Possible Issues

At program start:

Next step: