Summary of Executed Tasklets
By clicking on a specific job RunID from the Job Tracker interface,
you can drill down and see the detailed logging for a particular
job run. This interface
shows each Tasklet that has run for the given job. Some jobs can have multiple Tasklets associated
with them. For each Tasklet, you can see when it started processing and when (and if) it
has completed processing. Here is the information that can be seen:
- TaskID: ID of the Tasklet. Each Tasklet within a job has a unique id. If you put the cursor over the ID you can
see the specific Tasklet component name and version appear as a tooltip.
- Name: User assigned name given to the Tasklet.
- Started: Date/Time the Tasklet started processing.
- Completed: Date/Time the Tasklet completed processing.
- State: State of a job can be:
running
, terminated
,
completed
(with or without errors), or failure
. If this Tasklet run is a retry (Tasklet was
previously run in a previous job run attempt) the Tasklet will be marked with a "*" or "**" depending on the type
of retry attempt (retry from start or retry from last aborted Tasklet respectively).
If failure, the failure will often have a tooltip detailing the failure reason message.
- Exit Condition: Possible values are:
NA
(typically means job is still running),
normal
, exit job
(job threw an exit condition),
failure/exit job
(job threw a failure exception), or internal error
.
- Error: This will be marked if any errors were logged by the Tasklet or a failure of any kind was thrown.
- Warn: This will be marked if any warnings are logged by the Tasklet
- Logs: Clicking this will take you to a screen the will show the detailed logs for the Tasklet.
- Runtime Viewer: If this link is present, it will take you to the
custom GUI viewer associated to the
Tasklet. This will allow the user to view the input and output JavaBean used by the Tasklet
and monitor the status of the Tasklet using a custom GUI.
Note, that this link will only be visible if the Tasklet as an assoicated custom RuntimeViewer GUI.
The user will also need to
have turned on the "save input/output JavaBean" feature from within the Job Designer in order
for the RuntimeViewer
to be able to read the input/output JavaBeans. This GUI viewer is also
often used to monitor the runtime results coming from the Tasklet as it is running.
- Status Code: Displays an optional integer status code that a Tasklet can set.
- Status Msg: Displays an optional string status message that a Tasklet can set.
Hints:
Note that any field that ends with a ".." at then end will have a tooltip associated with it that provides additional
information. If you hover the mouse over the label you will see the tooltip.