The Sync tab is objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task-type specific and is available in all executable objects.
Sync objects synchronize taskAn executable object that is running. Tasks are also referred to as activities. on the basis of defined conditions. Enter one or several Sync objects including the actions that should be taken in this tab if you want to make use of this possibility.
When the task starts, the Sync objects are checked one after the other. The Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. tries to use the Sync objectIt synchronizes executable objects based on defined states and actions. A particular Automation Engine object type. that is defined in the first line by calling the start actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios.. If this is not possible because of the Sync object's current condition, the task waits, aborts or is skipped. The type of reaction depends on the Else condition that is defined in the tab's last column. If "wait" has been specified, the task waits until it can use the Sync object with the start action. Then the Automation Engine checks the Sync object in the next line etc. The task starts as soon all Sync objects could successfully be used. Depending on the task's end statusThis represents the condition of a task (such as active, blocked, generating)., either an abend or end action is processed.
Up to 500 Sync objects can be specified.
All Sync objects must not include a total of more than 5000 rules. Rules are defined actions that are directly specified in the Sync object.
Task ends are administered by work processes but only the primary work processIt is responsible for the execution of Automation Engine-internal tasks and work processes. releases busy Sync objects. Because of this task allocation, it can take several seconds until a Sync object is released after a task has ended. In this case, the reportA report provides more detailed information about a task's execution or a component. entry includes a time stamp that shows a later time than the task has ended. These delays occur if the primary's work load is high or if it is processing lots of Sync objects.
Note that using many Sync objects and rules can reduce task clarity. Automic recommends reducing the number of Sync object to a minimum.
Only actions that have been defined in the Sync object can be selected.
Field/Control |
Description |
---|---|
Sync object |
Selects the Sync object that should be used to synchronize the task. |
Start action |
Defines the action that should be taken when the task starts. If this is not possible because of the Sync object's status, the Else condition becomes effective. |
Abend action |
This action is processed if the task aborts. |
End action |
This action is processed if the task ends successfully. |
Else |
You can define here what should happen to the task if the start action cannot be executed:
|
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |