The Runtime tab is an object classThere are four classes of objects: executable, active, passive and system objects.-specific tab which is available in every executable object in AE. It can be used to specify parameters for a taskAn executable object that is running. Tasks are also referred to as activities.'s 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). behavior.
The Runtime tab is structured as follows:
Field/Control |
Description |
---|---|
Definition for ENDED_OK |
|
Return code <= |
Maximum return codeThe value that represents the result of tasks and script functions. for a task's normal end. A task ends normally (Status "ENDED_OK") if its return code lies below or is equal to the specified maximum return code. |
Else execute |
You can execute an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task if the task does not end with a return code that lies within the ENDED_OK area. Note that this object will not be processed if the task is terminated by using the scriptA particular Automation Engine object type. statement :EXIT. |
End statusThis represents the condition of a task (such as active, blocked, generating). for forecastEstimates a task's runtime on the basis of previous executions. |
Selection listShows entities in a grid view for the end status that this task should return when you make a forecast calculation. |
Estimated runtime (ERT) |
|
Current ERT = |
Displays the task's next estimated runtime (ERT). You can enter the estimated runtime here. This value applies until the ERT calculation is made after the task's next execution. Format: "hours:minutes:seconds". |
Use default (UC_CLIENT_SETTINGS) |
Selecting this option has the effect that the calculation method that the administrator specified in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS using the key "ERT_METHOD" is used to calculate the estimated runtime. |
Fixed value |
A fixed value is entered as the estimated runtime. |
Dyn. method |
Selection list for the dynamic method that is used to calculate the estimated runtime
from the actual runtime.
|
from the last ... runs |
Number of past runs that are considered for the ERT calculation. Allowed values: 0 to 25. |
+ ... % |
Value in percent for an upward ERT correction. |
Differences > ... % are ignored |
You can ignore possible huge differences to of actual runtimes. Upper limit (in percent) for actual runtimes that should be included in estimated runtime calculation. |
but do use ... runs at least |
Number of past runs that should be considered regardless of differences. Allowed value: 0 to 25. |
Show Chart |
Button that can be clicked in order to update the estimated runtime according to the current settings. A diagram displays in a separate window; it shows the last 25 ERT/RRT runs. Windows that are already open are updated. |
Reset Values |
Button that can be used to delete the real and estimated runtimes. |
Maximum runtime (MRT) |
|
None |
The maximum runtime is not monitored. |
Fixed value |
The maximum runtime is monitored. The allowed time is entered as a fixed value in the format "hours:minutes:seconds". An actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios. as an ELSE condition must be specified which reacts when maximum runtime is exceeded. |
ERT |
The maximum runtime is monitored. The valid estimated runtime (ERT) at the time of the task's activation is used as the maximum runtime. An action as an ELSE condition must be specified which reacts when maximum runtime is exceeded. |
+ ... % |
A correction in percent can be specified for ERT for the maximum runtime. The determined value is added to the estimated runtime. |
Curr. date + day(s) |
The maximum runtime is monitored. A number of days and time of day are set for when the task must be finished. The starting point for the calculation of the date is the real date of the task. An action as an ELSE condition must be specified which reacts when maximum runtime is exceeded. |
TimeZone |
Selection of a TimeZone object. |
Minimum runtime (SRT) |
|
None |
The minimum runtime is not monitored. |
Fixed value |
The minimum runtime is monitored. The allowed time is entered as a fixed value in the format "hours:minutes:seconds". You must specify an action (ELSE condition) that applies if the maximum runtime has been exceeded. |
ERT |
The minimum runtime is monitored. The valid estimated runtime at the time of the task's activation is used as its maximum runtime. You must specify an action (ELSE condition) that applies if the maximum runtime has been exceeded. |
- ... % |
When you select the ERT, you can also specify a correction value in percent for the maximum runtime. The value you determine is added to the estimated runtime. |
Else |
|
Cancel / Quit |
If you activate this check box is activated, the task is canceled or quit if the runtime has been exceeded. Only available if the maximum runtime is monitored. |
Execute |
If you activate this check box, you determine that the task is executed. You can directly select the executable object. If the runtime is exceeded or not reached, the specified task is executed. Only available if the runtime is monitored. |
A different type of runtime monitoring can be used for tasks that have been activated in 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 using a Schedule objectIt starts executable objects periodically. A particular Automation Engine object type.. You can define it in the properties of the relevant object (Runtime tab). The setting that are defined within the context of a workflow or schedule overrule the settings that have been defined in the task itself.
You can also assume these setting for runtime monitoring in the workflow or schedule. This is the default setting.
The quality of the ERT calculation is dependent on the available data. In case of a reorganization of the databaseA database is an organized collection of data including relevant data structures. there could be not enough datasets available. The calculation might be wrong in this case.
A lot of statistical data will be read from the object for the ERT calculation. Therefore this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… should be only activated for individual objects, not clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.-wide.
See also:
Runtime Evaluation
Runtime Monitoring
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |