Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 352: Batch Applications for the Java Platform

List of Batch Applications Compatible Implementations


Updates to the Original JSR

The following information has been updated from the original proposal on the date shown.

2013.10.16: Scott Kurz, IBM, has become the Maintenance Lead.

Maintenance Lead: Scott Kurz, IBM

E-Mail Address:

Telephone Number: -

Fax Number: -


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Specification license
RI/TCK license

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: IBM

Name of Contact Person: Chris Vignola

E-Mail Address:

Telephone Number: +1 720 396 7501

Fax Number: +1 720 396 7501

Specification Lead: Chris Vignola

E-Mail Address:

Telephone Number: +1 720 396 7501

Fax Number: +1 720 396 7501

Initial Expert Group Membership:


Supporting this JSR:


Section 2: Request

2.1 Please describe the proposed Specification:

This proposal intends to specify the following:

  1. Batch job
  2. A batch job represents a series of closely related processing steps that, taken together, perform a discrete business process. For example, common bulk-oriented extract, transform, and load data processing fits this model.

  3. Batch job step
  4. A batch job step is a unit of execution within a job, representing a discrete processing task within the overall business process. A job contains one or more steps. Steps may be executed in sequence or concurrently. Steps may be executed as singletons or multiple parallel instances. Steps may be optional, with the decision to execute or skip them conditioned on the outcome of prior steps in the same job.

  5. Batch application
  6. A batch application is a deployable unit comprised of one or more job steps.

  7. Batch executor
  8. A batch executor is a container that manages the execution of batch jobs. It manages the lifecycle of a batch job, including the lifecycle of each of its constituent steps. The container optionally manages checkpoint transactions for transactional job steps that support positioned restart.

  9. Batch job manager
  10. A batch job manager (scheduler) is the initiator of jobs. It is responsible for responding to requests to run jobs and dispatching them to batch containers execution. The batch scheduler can also support various scheduled job executions, such as calendar and event based triggering.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Java EE,SE

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

The JSR should allow creation of batch applications that may execute in the Java SE environment or Java EE environment without change to the application. There may be different qualities of service among each environment - e.g. JTA transactions in a Java EE environment.

2.4 Should this JSR be voted on by both Executive Committees?

No. By the SE/EE EC only.

2.5 What need of the Java community will be addressed by the proposed specification?

The ability to implement batch applications using a standardized programming model; The ability to schedule batch jobs using standardized interfaces.

2.6 Why isn't this need met by existing specifications?

There is no programming model definition for batch applications. Existing scheduling mechanisms in EE, such as timer based do not go far enough to cover common batch scheduling requirements, such as external dependencies.

2.7 Please give a short description of the underlying technology or technologies:

The JSR will provide a Java API & SPI using annotations and CDI where beneficial.

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)


2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?


2.10 Are there any security issues that cannot be addressed by the current security model?


2.11 Are there any internationalization or localization issues?


2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?


2.13 Please describe the anticipated schedule for the development of this specification.

For batch job, batch job step, batch application, and batch executor:

  • Q3 2011 Expert Group formed
  • Q4 2011 Early Draft
  • Q1 2012 Public Review
  • Q2 2012 Final Release

The batch job manager will be considered in a future revision of the specification.

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

The primary means of communication will be email, with conference calls and face-to-face meetings scheduled as needed.

2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:

A project site will be used to track all issues and disseminate information on the progress of the JSR.

- The public can read the names of the people on the Expert Group.

This information will be on on the project page for the JSR. It will also be part of every specification draft.

- The Expert Group business is regularly reported on a publicly readable alias.

The Expert Group will conduct business on a publicly readable alias.

- The schedule for the JSR is publicly available, it's current, and I update it regularly.

The schedule will be available on the project page for the JSR.

- The public can read/write to a wiki for my JSR.

We'll use a public mailing list for comments.

- I have a discussion board for my JSR and I regularly read and respond to posts on that board.

We'll track such discussions and respond to them or redirect users to the public comment mailing list.

- There is an issue-tracker for my JSR that the public can read.

Yes, it will be accessible from the JSR project page.

- I have spoken at conferences and events about my JSR recently.


- I am using open-source processes for the development of the RI and/or TCK.

Yes, the Reference Implementation will be developed as a project.

- The Community tab for my JSR has links to and information about all public communication mechanisms and sites for the development of my JSR.

It will point to the project page for the JSR.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The batch components described herein shall run on SE and on EE without change. The EE EG shall determine where to include the RI and TCK and how best to integrate.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Specification license
RI/TCK license

Note that this information has been updated from this original proposal.

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications. project "jbatch" Homepage:

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

ANSI/ISA S88 Batch Standard -

3.2 Explanation of how these items might be used as a starting point for the work.

The ANSI/ISA S88 Terminology (S88.01) will be loosely adopted.