Administer the batch environment
With WebSphere Application Server v9, we can use the JSR-352 programming model instead of using Compute Grid to run Java batch jobs.
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 provided for batch in Liberty (for example, the batchManagement-1.0 feature) are not present in the JSR-352 support for WAS.
- JSR-352 batch applications cannot be managed in the Compute Grid job scheduler.
- 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.
- Configure the batch environment
- Configure the unit test environment (UTE) in Rational Application Developer
- Configure the job scheduler
- Secure the job scheduler
- Configure WebSphere grid endpoints
- Run batch jobs under user credentials
- Batch jobs and their environment
- Create and manage reports for batch statistics
- Job scheduler integration with external schedulers
- Configure the external scheduler interface
- Requirements-based job scheduling
- Service policies for batch jobs
- Batch job classification
- Job usage data for charge-back accounting support
- Integrate batch features in z/OS operating systems
- Rolling out batch application editions
- Job scheduler custom properties
- Port number settings for batch
- Batch administrator examples
- WSGrid properties file examples
- Administer with the batch administrative console help files
Script for batch applications Developing batch applications Deploy batch applications Submitting batch jobs Troubleshoot batch applications JobSchedulerCommands