This topic describes elements that comprise a typical batch environment.
The job scheduler is the batch component that provides all job management functions, such as submit, cancel, and restart. It maintains a history of all jobs, including those waiting to run, those running, and those having already run. The job scheduler is hosted in a WebSphere® Application Server or cluster in a WebSphere Network Deployment environment.
The batch container is the batch component that provides the execution environment for the batch jobs. Java Platform, Enterprise Edition (Java EE) based batch applications run inside the batch container. The batch container is hosted in a WebSphere Application Server or cluster in a WebSphere Network Deployment environment.
Java EE batch applications are regular WebSphere Java EE applications, deployed as Enterprise Archive (EAR) files, that contain implementations of one or more Java batch applications. These Java batch applications follow either the transactional batch or compute-intensive programming models.
Jobs are described using a job control language. The batch jobs use an XML-based job control language. The job description identifies which application to run, its inputs, and outputs.
The job scheduler exposes three API types to access its management functions: A web interface called the job management console, a shell command line called lrcmd, and APIs, available as either web services and EJBs.
The job scheduler uses a relational database to store job information. It can be any relational database supported by WebSphere Application Server. If the job scheduler is clustered, the database must be a network database, such as DB2®.
The batch container uses a relational database to store checkpoint information for transactional batch applications. The database can be any relational database supported by WebSphere Application Server. If the batch container is clustered, the database must be a network database, such as DB2.
The JDBC is standard JDBC connectivity to the scheduler and container tables, as supported by the WebSphere Application Server connection manager.