Administration Guide > Installation > New Installation > Installing the Agent for UNIX

Installing the Agent for UNIX

This document guides you through the new installation of a UNIX agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host.

Each supported UNIX variant is assigned a three-character code. This code appears in all of the agent's file names and is described in the terminology. In this document the specific code is replaced by "???."

64-bit UNIX platforms: Automic recommends using a 64-bit agent in order to start 64-bit programs and applications. Problems may occur when you use a 32-bit agent for this purpose.

The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used if you intend to use one of the available authentication methods. More detailed information is provided in the document Advanced Security.

Automic strongly recommends installing the agent in a separate directory.

Automic recommends running the UNIX agent with root rights. Without root rights, the agent cannot switch to the context of another userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. and jobs and file transfers must always run under the user under which the agent has started.
You can define the relevant rights for the agent by starting it under the real "root" user. Another method is to set the sbit for the agent and to define "root" as the ownerEntities are owned by a specific user or team. Only this user//users inside the team may change the entity.. The effect is that every user of the groupAn Automation Engine object type that integrates tasks so that they can be processed together. that is assigned to the agent can start it. 

Requirements

Supplied Files

The files of the UNIX agent are supplied in compressed form:
ucxj???.tar.gz ... files of the actual agent,
ucxb???c.tar.gz ... files for the CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program..

Eacht TAR file is found in the subdirectory of IMAGE:AGENTS\UNIX that corresponds with the appropriate UNIX version.

File name Description
ucxj??? UNIX agent
ucxj???m Message Program for UNIX agent
ucxjxxx.ini Sample of the INI file for the UNIX agent

ucx.msl

Message library

ucxe???f

Help program for extended querying of the file system

ucx???s IO Service Program, needed for the execution of a FileSystem Event objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, if FE_VERSION is set to "2".

The CallAPI files and their implementation are described in a separate document.


Procedure

0. Rights of the user ID "AE"
1. Transferring the TAR files to the hostComputer, target system. and setting up the system environment
2. Configuring authentication via PAM (optional)
  1. PAM library installation
    The PAM library must be installed on your system (depends on the platform you use).

  2. PAM library configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied.
    The configuration process depends on the UNIX platform that you use. Typically, you will handle it by using the files /etc/pam.d or /etc/pam.conf
    The name of the service complies with the name of the executable agent file (ucxj???).

  3. Configuring the agent
    In the INI file of the UNIX agent, set the parameter authentication= ([MISC] section) to "pam". In the parameter libname= ([PAM] section), you must specify the path and the file name of the PAM library:

    [MISC]
    authentication=pam

    [PAM]
    libname=/usr/lib/libpam32.o
3. Starting the Agent

Use the ServiceManager to start or end agents.

4. Ending the Agent

 


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

Copyright © 2016 Automic Software GmbH