The command line program of Process AnalyticsAn Automic graphical analysis tool that displays the activities, statistical data and forecast data per Automation Engine system client in a bar diagram and that can be used to calculate the critical path. [Formerly called "ClearView," "Graphical Workload Analyzer," or "JobMonitoringStudio (JMS)."] Admin starts the ETL process (data-loading process). The following steps define the ETL process).
The AE databaseA database is an organized collection of data including relevant data structures. stores the meta data of tasks (executable objects such as workflows or jobs) in the AE system. It is stored in the following AE database tables and can be called by using the ETL process.
A* Tables: Information about tasks that have already run (statisticsThis is a list of a task's previous runs.).
E* Tables: Information about active tasks (such as the 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).).
F* Tables: Information about scheduled tasks that have not yet been processed (forecasts).
O* Tables: Runtime information (minimum, maximum) of tasks that have already run.
Depending on the taskAn executable object that is running. Tasks are also referred to as activities. model, the data is converted accordingly. Each task is converted in a way that it can be displayed in Process Analytics as a long-running task, a single task or as a parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task.
The task model data is loaded to the Process Analytics Database. The following Process Analytics database tables refer to the ETL process and store the following information:
ACT Table: Information about long running tasks such as Schedules and period containers.
CON Table: Data of all individual tasks and parent objects.
DEP Table: Information about explicit and external task dependencies.
LI Table: Information about executed ETL processes.
LO Table: Information about currently active loading processes. This ensures that only one loading process is executed at a time.
TACT, TCON, TDEP (Temporary Tables): Buffer for the data of the ACT, CON and DEP tables.
The AE system data is initially buffered in the temporary tables when a loading procedure is triggered. This serves the following purposes:
Consistency:
The data that AE Process Analytics displays remains valid during the ETL process because this data does not change until the data has completely been loaded from the AE database. Afterwards, all data is moved to the tables ACT, CON and DEP and can be accessed by Process Analytics.
Reliability:
A failed data-loading process does not affect the displayed data. You can restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. the data-loading process after the temporary tables have been cleared in order to avoid inconsistencies.
Performance:
Data is only retrieved from the AE database during this process. There is no need to merge or delete data. The time that is required to access the AE database is reduced to a minimum.
You can determine the source database (AE database) and the target database (Process Analytics database) during the Process Analytics Admin configuration process.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |