Deploying Java batch applications in Liberty
You can develop Java™ batch applications that are based on Java Specification Request (JSR) 352, and then submit Java batch jobs to run on a Liberty server.
Subtopics
- Java batch and managed batch overview
The Java batch function extends the application server to accommodate applications that must perform batch work alongside transactional applications. Batch work might take hours or even days to finish and uses large amounts of memory or processing power while it runs. - Configuring Liberty for the batch REST API
WebSphere Application Server Liberty includes a RESTful management interface to manage your Java batch jobs. Managed batch enables a secure HTTPS REST interface so that you can externally manage your Java batch jobs. - Java batch persistence configuration
Java batch uses a persistent store to persist status, checkpoints, and application persistent data across multiple runs of a job instance. The persistent store enables a job instance to be restarted if an earlier run fails or must be stopped by supplying the restarted job with the appropriate data. - Securing the Liberty batch environment
The Liberty batch framework allows you to configure role-based access to all batch management operations and also to view metadata and logs associated with your batch jobs. - Java batch shutdown and recovery
The Java batch feature behaves differently when the server is shut down while jobs are still running. - Batch REST API
The WebSphere Application Server Liberty includes a RESTful management interface to manage your batch jobs. - Enabling multiple server support by using the Liberty embedded messaging provider
The batch environment can be set up to have servers function as batch dispatchers while other servers function as batch executors. Batch dispatchers accept requests from external clients and make them available to the batch executors. The batch executors receive requests that match its defined capabilities and execute those requests. Batch dispatchers and batch executors communicate by using Java Messaging Service (JMS). - Enabling multiple server support by using the IBM MQ messaging provider
The batch environment can be set up to have servers function as batch dispatchers while other servers function as batch executors. Batch dispatchers accept requests from external clients and make them available to the batch executors. The batch executors receive requests that match its defined capabilities and execute those requests. Batch dispatchers and batch executors communicate by using Java Messaging Service (JMS). - Enabling multiple server partitions support by using the Liberty embedded messaging provider
You can set up the batch environment to have servers function as batch dispatchers, while other servers function as batch executors. - Enabling multiple server partitions support by using the IBM MQ messaging provider
You can set up the batch environment to have servers function as batch dispatchers, while other servers function as batch executors. - Enabling batch job events publishing
By using Java Messaging System (JMS), the batch server can publish job-related events to external clients. - batchManager command-line client utility
The batchManager command-line client utility provides a command-line interface for managing your batch jobs that run on Liberty. - Viewing Java batch job logs
When you are running Java batch jobs in the WebSphere Application Server Liberty, a log is written for each job.
Parent topic: Deploying applications in Liberty


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-libcore-mp&topic=twlp_container_batch
File name: twlp_container_batch.html