Inside Automation Engine > Executing Objects > Stage 2: Generation

Stage 2: Generation

The second stage is objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task generation. The specifications made in the object are now generated, and Sync objects or the maximum number of parallel running tasks are checked. Scripts are also processed in this stage.

The structure and start time of the generation stage depend on the setting "Generate at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start)." which is available in every executable object (Attributes tab). Depending on this setting, a scriptA particular Automation Engine object type. is processed either directly after the taskAn executable object that is running. Tasks are also referred to as activities.'s activation or just before its processing stage starts.

There is no remarkable difference between the above generation types when a task's activation stage is immediately followed by its start stage. But there can be a gap between them. As a matter of fact, the start time of the activated object is usually subject to superordinate objects such as a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."] or groupAn Automation Engine object type that integrates tasks so that they can be processed together..

Example:

A workflow contains several tasks. Activating this workflow means that its tasks are also activated. Object scripts are now processed provided that the setting "Generate at runtime" has not been activated. The individual workflow tasks start according to their position within the workflow order.

Advantage of object generation in the activation stage:

Advantage of object generation directly before the processing stage:

 

 

Status: Waiting for Predecessor

Status: Waiting for Start Time

Status: Registered

Generation

Steps

Description

Script
(not "Generate at runtime")

The script is processed directly after the activation stage.

 

Manual releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked.

In manual executions with options, you can select the option Wait for manual release. Tasks must be released in the Activity Window before their start can be initiated.

 

Sync verification

The system checks if the specified Sync objects are available.

 

Parallel running tasks

Use the Attributes tab to specify the maximum number of object executions which can run parallel.

 

Script
("Generate at runtime")

The script is processed just before the processing stage begins.

Script Processing in Detail

Not every script type is processed in the generation stage. !Process of Event objects and Child Post Processes are executed in the processing stateThe state a package or a task currently is in.. Post Processes are processed in the completion stage.

Steps

Description

Agent group resolution

The relevant 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 is selected for tasks that are processed in an agent group. Subsequent changes are possible in the Process tab.

 

Object variables

The object variablesPlaceholder for values that are stored in an object's "Variables & Prompts" tab/section. of the task and its superordinate taskThere are various ways of activating objects. The originator of the activation is referred to as the superordinate task (parent). are provided.

 

Pre-Process

Jobs: Pre-Process tab contents are processed.

 

Attribute dialog

The Attribute dialog is only displayed if the task is activated manually and NOT generated at runtime.

 

Header

Jobs: Header include and related 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. includes are processed.

 

Process

Process tab contents are processed.

 

Trailer

Jobs: Trailer include and related user includes are processed.

 

JCL generation

Jobs: JCL generation is possible after AE Script processing. JCL modifications are possible before the jobAn Automation Engine object type for a process that runs on a target system. starts on the destination computer.

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH