Before you begin
The database administrator must create the JobRepository tables needed to persist batch job details. Also, the WebLogic Server administrator must configure an XA-capable data source for the JobRepository tables. When a Java EE component 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. See Create JDBC generic data sources.
Use this page to configure a batch runtime (per JSR 352), which 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. 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.
For information about configuring and using the batch runtime in Oracle WebLogic Server, see "Using the Batch Runtime" in Administering Server Environments for Oracle WebLogic Server.
Note: If the JobRepository data source is shared by applications then this schema name must be same name that the application expects.