This 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."] attribute must be set if workflow tasks that use the same agent groupAn agent group combines agents of the same platform. The agents that should be included in an agent group are specified by entering the agent name or via filters. A task that runs in an agent group is processed on one or all of the agent group's agents, depending on the specified mode. A particular Automation Engine object type. should also use the same hosts.
Tasks that include an agent group: The system first checks whether the option Re-using agent group calculation is set for the workflow of which it is part:
Storing the calculated agent groups in the top workflow ensures that all tasks of sub-workflows can use the same agent that had to be calculated only once. agent groups of workflow tasks are only stored if the option Re-using agent group calculation is selected.
Note that agent group calculation takes place when the task starts and not when it is activated. Therefore, the option 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). affects this point in time.
Re-using agent group calculation is not possible in:
Agent group agents are retrieved for each individual task if this setting is not active. Therefore, tasks of the same agent group can run on different agents.
This functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… requires that the setting "Re-using agent group calculation" is activated in both workflows (Workflow1 and Workflow2 in the illustration below).
The workflow's first task (Job1) is processed first. It uses AgentGroup1. Host1 is selected because there are no internal entries for a former agent group calculation. Subsequently, AgentGroup1 and the corresponding agent Host1 are stored in the workflow.
Workflow2 is subordinate to the top workflow (Workflow1). The subordinate workflow's task Job3 re-uses AgentGroup1. When task Job3 starts, the agent Host1 that has already been stored in the top workflow is selected for the execution.
Therefore, all tasks of the same agent group use the same agent regardless of their subordination level. Note that this only applies to workflow tasks in which the option Re-using agent group calculation has been activated.
See also:
Workflow
Workflow - Attributes tab
Agent Group
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |