Domain: Configuration: Batch
Configuration Options Related Tasks Related Topics
A batch runtime (per JSR 352) provides support for defining, implementing, and running batch jobs. Batch jobs are tasks that can be executed without user interaction and are best suited for non-interactive, bulk-oriented and long-running tasks that are resource intensive, can execute sequentially or parallel, and may be initiated ad hoc or through scheduling.
Use this page to define the Batch configuration of this WebLogic Server domain.
The batch runtime in WebLogic Server uses a data source, also known as the JobRepository, and a managed executor service to execute asynchronous batch jobs. When a Java EE component that is deployed to the domain submits a batch job, the batch runtime updates the JobRepository tables using this data source, which is obtained by looking up it's JNDI name.
Name Description Data Source JNDI Name
Returns the Batch DataSource jndi name. This jndi name will be used to lookup an instance of a DataSource that will be used to store the Batch jobs data.
The schema name where the JobRepository tables have been created. Note that if the JobRepository data source is shared by applications, then this schema name must be the same name that the application expects.
Executor Service Template
Returns the name of the application-scoped ManagedExecutorService. This ManagedExecutorService instance will be used to run batch jobs that are submitted from applications deployed to the domain. The ManagedExecutorServiceTemplate by the same name must exit when a batch job is submitted in the domain. If this returns null, then the batch runtime will look to use the default Java EE ManagedExecutorService that is bound to the JNDI name:
- Configure the batch runtime
- Configure JDBC generic data sources
- Configure concurrent managed object templates