This topic covers a few basic ideas of what Agents in an Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. system are and do.
General Information about Agents
Agents are programs on the platform used (Windows, UNIX, zOS, etc.). They run in the background of the operating system. Agents have no UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]. They just create log files to record what occurs on 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.
Agents are configured by using their respective INI file.
An agent connects via TCP/IP to the communication processA communication process is part of the component Automation Engine. It is responsible for connecting the components. (CP) with the smallest number of existing connections and keeps that connection alive. When the connection is lost, the agent is forced to try to reconnect. The interval of reconnect attempts is configurable.
The communication between CP and agent is encrypted. In one Automation Engine systemAn environment that is managed by Automation Engine components. [Formerly called "UC4 system."] a high number of agents can be used. There exists no information even among Automic developers what the limit may be. AE systems with as many as 10,000 agents exist at customer sites.
Kinds of Agents
Agents are differentiated by operating system (OS) agents and those being used together with solutions like SAP, PeopleSoft, etc.
All agents have Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task execution implemented, in OS agents additionally FileSystem Event and FileTransfer objects can be executed. Two kinds of events exist, FileSystem Events and Console events.
Job Execution
If a Job is started on an OS agent, this jobAn Automation Engine object type for a process that runs on a target system. will be initiated in the OS, independent of the agent. The agent monitors the job and reports its statusThis represents the condition of a task (such as active, blocked, generating). to the AE in certain cycles. When the job finishes, the agent also reports this to the AE system. This may trigger possible follow-up jobs.
Job Reports
Job reports may be configured in the Job object. When the job is run, they are transferred to the AE databaseA database is an organized collection of data including relevant data structures.. The OS agent provides the reportA report provides more detailed information about a task's execution or a component. as a file. The AE loads the report as individual blocks into the database.
Should the report exceed a configurable limit, only data comprising the configured size will be transferred into the database, where the last block transferred always contains the file's end. Thus the beginning and end of a job report are available in the database.
FileTransfer Object
A FileTransfer is an executable object that is always executed between two OS agents. To this end a TCP/IP connection is created between the two agents. Here as well, the data transfer is encrypted. The agent sending files reports the job's status at intervals and the end of the job execution to the AE system. The connection between the two agents is closed at the end of the file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object)..
Schematic representation of an Automation Engine system
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |