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.
Note that authorizations must not be changed while the agent is running.
When a loginAn Automation Engine object type that stores account credentials used by agents on target systems. is specified in the scriptA particular Automation Engine object type. element PREP_PROCESS, the eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. file is created in the HOME directory of the user for security reasons. If no login is specified, the system assumes that the succeeding event jobAn Automation Engine object type for a process that runs on a target system. runs with agent rights. Therefore, PREP_PROCESS creates the file name with the temp path of the agent.
At the time when PREP_PROCESS is being processed, the system does not know whether the job will use a login or not. From a technical perspective, this cannot currently be determined, because the event job could also specify the login dynamically (with a PUT_ATT script statement). There are two possible solutions:
Authorizations for jobreport files are specified using the INI-file parameter ReportMode=.
See step 1: Unloading the TAR files and setting up the system environment.
Read the note referring to processes on AIX.
Note that on AIX, the size for Core files must be extended.
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.
![]() |
0. | Rights of the user ID "AE" |
---|
![]() |
1. | Transferring the TAR files to the hostComputer, target system. and setting up the system environment |
---|
chown root ucxj???
chmod 4755 ucxj???
![]() |
2. | Configuring authentication via PAM (optional) |
---|
Authentication via (Pluggable Authentication Modules) is now supported for the agents of the following UNIX platforms: Solaris, Linux and AIX.
![]() |
3. | Starting the Agent |
---|
Quitting with the DEL key is only possible as of version 1.20 and when the corresponding parameter in the INI file has been set. Automic recommends that you do not set this parameter, but quit from another terminal using the kill -TERM instead.
Enter the following if the directory $HOME/bin
has been set in the system environment PATH:
nohup ucxj??? 1> ucxj???.log
2>&1 &
Enter the following if the directory $HOME/bin has not
been set in the system environment PATH:
nohup ./ucxj??? 1> ucxj???.log
2>&1 &
Note displayed process ID pid.
Information about this process with ps
-ppid. Not always available.
Information about all UCX processes with ps
-ef | grep ucx.
Information about all processes with ps
-e.
Use the ServiceManager to start or end agents.
![]() |
4. | Ending the Agent |
---|
kill-TERM pid
kill
-KILL pid or
kill -9 pid
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |