Step Settings

A step of a batch job basically consists of ItemReader, ItemProcessor, and ItemWriter. Depending on the characteristics of these components, configure them as follows.

(1) When a business developer has directly implemented the step components as a bean, specify the bean name in "reader", "processor", and "writer" of "chunk" as shown below. As the standard composes ItemReader, ItemProcessor, and ItemWriter in a single bean, the names of reader, processor, and writer are the same.

You can configure the DataSource to be managed as a transaction in the step by using the "tm-datasource" attribute. If it is not specified separately, the default is "MainDS". For steps that execute some steps simultaneously (for example: split), this attribute must be defined.

When a batch job is restarted and its lower steps are executed, the unit steps that were completed in the previous execution are skipped because their processing has already been completed. If a step must always be executed upon batch job restart regardless of completion status (for example, a task to check whether the next step should proceed), specify the "allow-start-if-complete" attribute as "true" as shown below so that it is executed every time. (Default: false)

※ Note: If the parameter duplicate execution setting in Web Admin batch job management is set to "Y", the job is re-executed from the beginning and this option is not applied.