The MPE 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 works together with the AE system via a TCP/IP interface.
The MPE agent provides the following functions:
In AE jobs are defined and maintained in the form of objects that include various tabs. The JCL is stored in
the Process tab. Its logic can be very complex if you make use of AE's scriptA particular Automation Engine object type. elements. You can use # as the prompt character in the JCL because the characters !
and : introduce comment lines and script statements in AE
script.
You can also start JCL lines by using the script statement :DATA. In doing so, you can keep ! and : as prompt characters.
See: User Guide - Job and Job
- Execution
In AE, you can start jobs either manually or via control mechanisms such
as workflows or schedules. The Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. then generates an executable jobAn Automation Engine object type for a process that runs on a target system. and sends it to the MPE agent via a file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object)..
See: Inside AE Guide - Executing Objects
The MPE agent reads the job and passes it to the MPE job queueA particular Automation Engine (AE) object type. In AE, a queue determines the maximum number of concurrent tasks, their priorities and the order in which tasks should be executed. In ARA, queues are containers for workflow executions that should be executed at a certain time one after another..
The job notifies the agent about the beginning and end of an execution. The agent then passes this information on to the Automation Engine.
The agent monitors the job's statusThis represents the condition of a task (such as active, blocked, generating). in regular intervals. This ensures that an abnormal end can be determined if a job vanishes (fatal error or ABORTJOB). The job's return codeThe value that represents the result of tasks and script functions. is available in AE.
The job reportA report provides more detailed information about a task's execution or a component. ($STDLIST) is stored in the file that is specified by the Automation Engine. If specified in the job, the agent transfers the report to the Automation Engine which stores it in the AE databaseA database is an organized collection of data including relevant data structures.. The agent copies the job output from the Spooler. Therefore, you must use an OUTCLASS of priority 1.
In AE, file transfers are defined and maintained in the form of objects that include various
tabs. They are executed with the character conversions that are defined in these tabs (such as UC_CODE).
See: User Guide - FileTransfer
In AE, events are defined and maintained in the form of objects that include various tabs.
Only events of type File System are currently supported.
See: User Guide - Event
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |