The TDM library includes a set of generic flows for error handling and statistics gathering that are based on Broadway capabilities and are tailored for TDM business requirements.
These generic flows gather errors and statistics during task execution and populate them into dedicated tables. This data is used for monitoring TDM tasks and creating TDM execution reports.
The TDM library includes two utility flows that handle errors during the execution of TDM tasks:
Both utilities invoke the internal PopulateTableErrors.flow to populate data about errors into the task_exe_error_detailed table. The difference between the utilities is that PopulateTableErrorsWithFailed.flow sets on a session level:
ENTITY_STATUS = failed
PopulateTableErrorsWithFailed.flow also sets the error category as Entity Failed in the task_exe_error_detailed table, while PopulateTableErrorsWithReject.flow sets a record as Record Rejected.
The error handling utility is invoked from each Load flow's Load Data To Target Stage. An error can be suppressed in order to continue a task execution and reach the statistics gathering step.
By default, the PopulateTableErrorsWithFailed is invoked and the Suppress setting is unchecked, i.e. the entity is rejected due to the error:
If a record needs to be rejected instead of failing an entire entity, replace the Inner flow name with PopulateTableErrorsWithReject and check the Suppress setting.
Click to learn how to use the ErrorHandling Actor.
The task execution report includes the Statistics Report tab that compares the number of records in each table in the source and target environments.
The TDM library includes the StatsLoader Broadway actor that populates the statistics data into task_exe_stats_detailed TDM DB table. The generated load flows include the following Broadway actors:
See an example below:
The TDM library includes a set of generic flows for error handling and statistics gathering that are based on Broadway capabilities and are tailored for TDM business requirements.
These generic flows gather errors and statistics during task execution and populate them into dedicated tables. This data is used for monitoring TDM tasks and creating TDM execution reports.
The TDM library includes two utility flows that handle errors during the execution of TDM tasks:
Both utilities invoke the internal PopulateTableErrors.flow to populate data about errors into the task_exe_error_detailed table. The difference between the utilities is that PopulateTableErrorsWithFailed.flow sets on a session level:
ENTITY_STATUS = failed
PopulateTableErrorsWithFailed.flow also sets the error category as Entity Failed in the task_exe_error_detailed table, while PopulateTableErrorsWithReject.flow sets a record as Record Rejected.
The error handling utility is invoked from each Load flow's Load Data To Target Stage. An error can be suppressed in order to continue a task execution and reach the statistics gathering step.
By default, the PopulateTableErrorsWithFailed is invoked and the Suppress setting is unchecked, i.e. the entity is rejected due to the error:
If a record needs to be rejected instead of failing an entire entity, replace the Inner flow name with PopulateTableErrorsWithReject and check the Suppress setting.
Click to learn how to use the ErrorHandling Actor.
The task execution report includes the Statistics Report tab that compares the number of records in each table in the source and target environments.
The TDM library includes the StatsLoader Broadway actor that populates the statistics data into task_exe_stats_detailed TDM DB table. The generated load flows include the following Broadway actors:
See an example below: