In this case, no errors occur, so the Job triggers the second tJava component only.
Double-click the tHMap component to open the Map
editor.
Right-click the outputKey element and click
Go to Structure Element.
Change the tHMap_1_output
structure that opens from Read Only to
Editable and then change the Data Type for outputKey to
Integer (32). This means that this element
can only be an Integer, and since this does not
match the input, an error will occur.
In the Run tab, click Run to execute the Job again.
In this case, the Job still triggers the second tJava component even though there is an error, because the
threshold above which an exception should be thrown (thus enabling the
downstream components to detect the error) is set as Fatal. However, the third tJava
component is also triggered since there is an error in the execution of the
map.
Select the tHMap component
and click Component > Advanced settings, then change the value of the Exception
Threshold drop-down list to Error.
This causes an exception to be thrown when the map has a severity of Error or higher.
In the Run tab, click Run to execute the Job for a third time.
In this case, the Job detects the error and triggers the first tJava component (OnSubjobError).
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!