Compute Grid batch or JSR 352

You can use the Compute Grid batch support to run Java batch jobs in WebSphere® Application Server. Starting in Version 9, WebSphere Application Server also provides an implementation of the Batch Applications for Java Platform 1.0 (JSR 352) programming model. This JSR 352 support offers specification-compliant, though limited, support for authoring and running Java batch jobs.

Compute Grid batch

The topics about batch applications in this WebSphere Application Server documentation apply to the Compute Grid batch support.

The Compute Grid batch support evolved from WebSphere Extended Deployment Compute Grid Version 8 and the Feature Pack for Modern Batch, which was offered with WebSphere Application Server Version 7.

The Compute Grid batch support offers the job scheduler, job management console, and other elements for a batch environment. See Learn about batch applications and Getting started with the batch environment for information about the batch environment and instructions for running Java batch jobs.

JSR 352

The JSR 352 support is not recommended for running batch jobs in WebSphere Application Server Version 9.

The following restrictions apply to JSR 352 support.
  • The Job Repository implementation is in-memory. Any knowledge about jobs that have executed is lost when the server (or servant) is ended.
  • The operational features that are provided for batch in Liberty (for example, the batchManagement-1.0 feature) are not present in the JSR 352 support for WebSphere Application Server.
  • JSR 352 batch applications cannot be managed in the job scheduler.
  • The thread pool that is used is bound to the JNDI name of java:comp/DefaultManagedExecutorService. By default, the thread pool is mapped to the WebSphere Default WorkManager with JNDI name wm/default. This mapping is defined in the Integrated Solutions Console under Resources > Java EE default resources.
You can disable the IBM built-in JSR 352 implementation in a server by setting the com.ibm.ws.jbatch.disable JVM property to true. The property defaults to false, which means that by default the IBM implementation is enabled. To disable JSR 352 for a server in the administrative console, complete the following steps:
  1. Click Servers > Server Types > WebSphere application servers > server_name > Process definition > Java Virtual Machine > Custom properties > New.
  2. In the Custom properties settings page, set Name to com.ibm.ws.jbatch.disable and Value to true.