Administering the batch environment

You can configure the batch environment and manage batch jobs.

Before you begin

Starting in WebSphere® Application Server, you can use the JSR-352 programming model instead of using Compute Grid to run Java batch jobs in WebSphere Application Server.

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 Compute Grid job scheduler.
  • [z/OS]Each servant region has its own copy of a job repository as an in memory instance in its own JVM. There is no coordination between multiple servant region in-memory based job repositories.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:24
File name: container_computegrid_administering.html