Getting started with the batch environment

The major components of the batch environment include the job scheduler, the interfaces to the job scheduler, the job database, and grid endpoints.

The following diagram shows the major components. You can use the command-line interface, the Enterprise JavaBeans (EJB) interface, the web services interface, and the job management console to communicate with the job scheduler. The job scheduler has a job database that contains all the jobs. The job scheduler in the diagram communicates with two node endpoints. An application server that is doing transactional work runs on another node, but does not communicate with the job scheduler. This application server is not part of the batch environment.
Figure 1. Batch components
Interfaces to the job scheduler, the job database, and nodes

The job management console provides a graphical user interface (GUI) with which you can perform job management functions. Most of the function from other interfaces is also available from the job management console.

With the command-line interface, you can submit and control the batch jobs in the system. The enterprise bean and web services interfaces provide similar function to both Java™ Platform, Enterprise Edition (Java EE) and non-Java EE programs through programmatic interfaces. The administrative console provides a graphical user interface (GUI) with which you can configure the job scheduler, and view the location of endpoint servers.

Batch administrators and submitters can use the job management console to view, manage and perform job-related actions that include submitting a job, viewing of jobs, canceling or suspending a job, and resuming a suspended job.

The job scheduler accepts and schedules the execution of batch jobs. It manages the job database, assigns job IDs, and selects where jobs run.

The grid endpoints are application servers that are augmented to provide the runtime environments needed by batch applications.

  • The grid endpoints support batch applications that are compute-intensive. Compute-intensive batch applications are built using a simple programming model based on asynchronous beans. Read about compute-intensive programming for more information.
  • The batch system supports transactional batch applications. These applications perform record processing like more traditional Java EE applications, but are driven by batch inputs rather than interactive users. This environment builds on familiar Plain Old Java Objects (POJOs) to provide batch applications with a rich programming model that supports container-managed restartable processing and the ability to pause and cancel running jobs. Read about the batch programming model for more information.

Icon that indicates the type of topic Concept topic



Timestamp icon Last updated: March 5, 2017 17:23
File name: cgrid_xdbgcmp.html