Java Reference
In-Depth Information
the BATCH_STEP_EXECUTION table, and BATCH_JOB_EXECUTION_CONTEXT refers to the
BATCH_JOB_EXECUTION table). Table 2-7 shows what the tables contain.
Table 2-7.
BATCH_JOB_EXECUTION_CONTEXT and BATCH_STEP_EXECUTION_CONTEXT Tables
Field
Description
Value
JOB_EXECUTION_ID /
STEP_EXECUTION_ID
Foreign key to the BATCH_JOB_EXECUTION /
BATCH_STEP_EXECUTION table
1
SHORT_CONTEXT
A string representation of the context
{"map":""}
SERIALIZED_CONTEXT
The serialized execution context for future use
on retries, and so on
NULL
Summary
In this chapter, you got your feet wet with Spring Batch. You walked through the batch domain covering
what a job and step are and how they interact through the job repository. You learned about the
different features of the framework, including the ability to map batch concepts in XML, robust
parallelization options, the formal documentation (including a list of the available sample jobs), and the
administration application Spring Batch Admin.
From there, you wrote the Spring Batch version of “Hello, World!”. You learned the different
methods of obtaining the Spring Batch framework, including checking it out from Git, using the
SpringSource Tool Suite, and downloading the zip distribution. When you had your project set up, you
created your job in XML, coded a tasklet, and executed your job. Finally, you explored the job repository
that Spring Batch uses to maintain information about the jobs it runs.
I want to point out that you've barely taken a peek into what Spring Batch can do. The next chapter
walks through the design of a sample application that you'll build later in this topic and outlines how
Spring Batch addresses issues that you'd have to deal with yourself without it.
