Administration Guide > Installation > New Installation > Installing the Automation Engine for UNIX

Installing the Automation Engine for UNIX

This document guides you through the new installation of a Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. for UNIX.

The Automation Engine for UNIX is available for different platforms; a three-figure code is supplied for each supported UNIX platform. The codes are the same as for agents and are described in the terminology. In this document, the specific code is replaced by the characters "???." This document describes the installation of the Automation Engine for Oracle and DB2 databases. Specific differences are described in the individual processing steps.

Automic strongly recommends installing the Automation Engine in a separate directory (such as /opt/uc4/server).

Requirements

General:

When using an Oracle Database:

When using a DB2 Database:

Supplied Files

Data for the Automation Engine for UNIX is supplied in compressed form. The relevant tar file is found in one of the appropriate UNIX platform subdirectories: IMAGE:AUTOMATIONENGINE\UNIX\.
UCS???.tar.gz ( Automation Engine files).

File name Description
ucsrvcp Communication process
ucsrvwp Work process
uc.msl Message library
ucsrv.ori.ini INI file
libsysapi, libuccache, libucudb32, libzu00132,
libzusynchk, libuc001, libucdsfun, libucmsgq, libucmsgxml, libucrtl, libucsbepm, libzuxml, libucsj, ucsj_1, ucsj_2, ucsj_3, libgcc_s, libstdc++, libucldap, libssp

For Oracle database: ucuoci
For DB2 database: ucucli

Runtime libraries

Files ending with "a" indicate AIX.
Files ending with "sl" indicate HP-UX.
Files ending with "so" indicate Solaris, Linux and zLinux.

syntax.bin

Description of scriptA particular Automation Engine object type. language

Procedure

1. Installing the Automation Engine

HP-UX:

Linux, Solaris and zLinux:

AIX:

HP-UX:

Linux, Solaris and zLinux:

2. Installing the AE SNMP subagent (optional)
3. Starting the Automation Engine

Manually start the Automation Engine for a test.

4. Shutting down the Automation Engine

Use the ServiceManager to start and end server processes.

Possible Problems

At program start:

Missing libraries or other errors are best found by starting the Automation Engine using:
truss 2>truss.out -f ucsrvcp

The resulting file, truss.out, contains all system calls of the Automation Engine and all attempts to load shared objects.

If a library is missing, the problem can be that it exists in the system, but its path has not been specified in the environment variable (LIBPATH, SHLIB_PATH or LD_LIBRARY_PATH). Search the library as "root" by using:
find / -name 'library' -print

(wildcard charactersThese are placeholders for characters when you specify filters. ? stands for exactly one character, * for any number of characters. are allowed).
Add the located path to the environment variable. If the library cannot be found, it has not been installed on this system or it has been deleted. Search the library to check whether it is available:

AIX, Linux, Solaris and zLinux: /var/sadm/install/contents
HP-UX: /var/adm/sw/ sw install.log and /var/adm/sw/ sw remove.log

See also:

Number of Server Processes
Installing the AE SNMP Subagent (UNIX)

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH