+

Search Tips   |   Advanced Search

Develop a simple transactional batch application

We can write a simple batch application using a batch job controller and EJB data stream, the command line, or the Apache ANT tool.

If the batch step uses a batch data stream (BDS) whose data is local to the file system of the application server to which the batch application is deployed, then certain steps must be followed to support job restart scenarios. If such a batch application is deployed to application servers that can run on multiple machines, then there is no guarantee that the restart request is accepted by the machine on which the batch job originally ran. This occurs when the batch application is deployed to a cluster, and if a batch job that runs against such an application is canceled and then restarted. In this scenario, the deployment might send the restart request to an application server that runs on a different machine. Therefore, in cases where file-based affinity is required, we can apply the following solutions to support the job restart scenario:

The batch application developer must ensure that transactional work done in the batch step callback methods inherits the global transaction started by the grid endpoints. This action ensures that work performed under a batch step only gets committed at every checkpoint and rolls back if the step fails.

Some commands are split on multiple lines for printing purposes.


Tasks

We have developed a simple transactional batch application using a batch job controller and EJB data stream, the command line, or the ANT tool.


What to do next

Install the compute-intensive application and configure WebSphere grid endpoints.


Subtopics


Related:

  • Batch job steps
  • Batch controller bean
  • Batch data stream framework and patterns
  • xJCL elements
  • Configure WebSphere grid endpoints
  • Install the batch application
  • Deploy batch applications
  • Retry-step processing