tLogCatcher
Operates as a log function triggered by one of the three: Java exception, tDie or tWarn, to collect and transfer log data.
Both the tDie and tWarn components are closely related to the tLogCatcher component.They generally make sense when used alongside a tLogCatcher component in order for the log data collected to be encapsulated and passed on to the output defined.
Fetches set fields and messages from Java Exception, tDie and/or tWarn and passes them on to the next component.
tLogCatcher Standard properties
These properties are used to configure tLogCatcher running in the Standard Job framework.
The Standard tLogCatcher component belongs to the Logs & Errors family.
The component in this framework is available in all Talend products.
Basic settings
Schema and Edit Schema |
A schema is a row description, it defines the fields to be processed and passed on to the next component. The schema of this component is read-only. It describes the properties of the log data. You can click the [...] button next to Edit schema to view the predefined schema which contains the following fields:
|
Catch Java Exception |
Select this check box to trigger the tCatch function when a Java Exception occurs in the Job. |
Catch tDie |
Select this check box to trigger the tCatch function when a tDie component is called in a Job. |
Catch tWarn |
Select this check box to trigger the tCatch function when a tWarn component is called in a Job. |
Global Variables
Global Variables |
ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it. For more information about variables, see Using contexts and variables. |
Usage
Usage rule |
This component is usually used as the start component of a secondary Job which is automatically triggered at the end of the main Job. |