Jobs and file transfers must log on to the OS before they can be processed. Login data is stored in Login objects.
The 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 provides two methods of authenticating user nameName of the Automation Engine user. and passwords.
PAM authentication is only supported for the agent on AIX, Linux and Sun Solaris (SPARC).
The method to be applied is specified in the agent's INI file. The section [MISC] includes the parameter authentication= to which you can assign the value "local" or "PAM".
Example:
[MISC]
authentification=local
If you opt for PAM authentication, also specify the library name.
Example:
[PAM]
Libname=libpam.so
Store the path for the library in the environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. LD_LIBRARY_PATH if it is not stored in the default directory.
The agent must have root privilegesPrivileges in the Automation Engine refer to user rights to work with certain frontend and user interface functions. You grant privileges to users in the Automation Engine..
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |