The document shown below explains the platform-specific settings for a MPE jobAn Automation Engine object type for a process that runs on a target system..
Field/Control |
Description |
---|---|
Job reportA report provides more detailed information about a task's execution or a component. |
|
Database |
The job report is managed by AE. When the job has been processed, the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. takes the process protocol which has been stored 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 computer and stores it to the AE databaseA database is an organized collection of data including relevant data structures.. |
File |
The job report is managed by AE. After the job execution, the process protocol is available as a file in the target system. |
On error only |
In case of job interruption, the job report is saved in the AE database and/or a file in the target system. This is only available when "Database" and/or "File" have been selected. |
Runtime options |
The host attributesPlatform-independent attributes of the Job object. defined here are assigned to the command "JOB" as a parameter. They form the job card of the MPE job. |
Job name |
Specification of a name under which the job should be executed. |
Queue |
Selection listShows entities in a grid view for the 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. in which the job should run which determines the execution's priority. "BS" stands for the highest, "ES" for lowest priority. The default value is "DS". The administrator administers the queue in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_MPE_QUEUE. A maximum of 8 characters is allowed for 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.-defined queues. |
Input priority |
Specification of the input priority (INPRI). This value is used for the logon of the job. A value between "1" and "13" can be use for Input Priority. The default value is "8". Jobs must be prioritized so that they are above the current job fence set by the system operator. If a value is specified which is less than or equal to this, access is denied. |
HIPRI |
Check box for activating HIPRI. HIPRI can be used to overwrite the job fence or the limit for jobs set to be executed. The authorizations System Manager (SM) or System Operator (OM) are required. |
Other |
Additional parameters for the "JOB" command. A maximum of 256 characters are possible. The parameters must be specified according to the syntax.. |
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |