The Edit Tasklet interface allows for editing existing Tasklets. Tasklets can be enabled or disabled. Disabling a Tasklet will prevent it from being executed when the Job is run.
Place your mouse over the "Name" or "Description" labels to see a tooltip of the full text. This can be helpful if the job's name or description are long.
The error dependency settings control how the job proceeds with its execution if the Tasklet produces certain kinds of errors. This is often needed when the job is made up of multiple Tasklets. You can decide if a job continues to run or stops completely if certain errors occur during Tasklet processing.
If the Tasklet has an input JavaBean and has an associated Weblet implemented in its Bundle, the input JavaBean properties can be edited and managed using this Weblet GUI. The Weblet is also known as the input JavaBean Customizer, because its primary purpose is to edit the input JavaBean, at design time, that is used later by the Tasklet when the Tasklet is run in a Job.
Tasklet versioning is a very powerful feature. It allows you to set Tasklet JavaBean properties (edit the input JavaBean) that will take effect at a given time in the future. For example, if a Tasklet has an input JavaBean with an email address property, and the email address needs to change at the start of the new year, then create a new version that takes effect at the start of the new year with the new email address. To edit or view a Tasklet at a given effective date in the future, click the "Edit/View Versions" link. This will allow you to create new versions and edit/view existing ones.
If the Tasklet has an input and/or output JavaBean, the user has the option of saving the input and/or output JavaBean when the Job is run. This allows the Job to log exactly what inputs the Tasklet used when it ran and what outputs it generated during its job processing. This is a very powerful auditing tool for the user. Using this, the user can view exactly how the Job was run and under what conditions (inputs and outputs). A Tasklets input/output JavaBean can be viewed using the Job Tracker tool. There is an optional GWT GUI interface called the RuntimeViewer that are associated with a Bundle and Tasklet, that if implemented in the Bundle, allow the user to visualize the input and output JavaBeans used during every job run of the Tasklet. And this allows the Bundle developer to customize how to view the status of a Tasklet as it runs or to view that Tasklet's input/output status after it has finished running.
By choosing to save the input and/or output JavaBean, you allow the user to access the optionally implemented RuntimeViewer GWT GUI associated to a Tasklet. The RuntimeViewer can be accessed when you navigate to the "Summary of Executed Tasklets" panel, from within the Job Tracker tool. The RuntimeViewer can often also show runtime status information about the running Tasklet/Job if the Tasklet/Job is still running. If the Tasklet is has finished running, the RuntimeViewer often shows the output results of the Tasklet.
This allows the user to configure if a Tasklet will wait for all background java threads, created in the Tasklet, before it exits. Normally, if the main java thread used by a Tasklet completes, the Tasklet will get marked as completed. However, if the Tasklet starts secondary/background threads, this property can allow the Tasklet to decide if it should wait on all background threads or not, before marking the Tasklet as complete. You can typically leave this set to "No" unless your Tasklet requires special handling.
Leaving the list blank will allow the Weblet and RuntimeViewer, using the UniversalClient GWT API,
to call any Mule endpoint they wishes. You can restrict the Weblet to access
only certain Mule endpoints by listing them out. If you do not want the Weblet
to have access to any Mule endpoints, then enter a fake endpoint like
vm://xyz, for example.
The Mule related features will only be available if your JobServer environment has the Mule package included in the JobServer installation. If Mule is not enabled in your JobServer environment, you will not see the related Mule features.