OTN Home > Oracle WebLogic Server 12.2.1.4.0 Documentation > Administration Console Online Help > Configure the batch runtime

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure the batch runtime

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.

To configure the batch runtime:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, under Domain Structure, select the domain name.
  3. Select Configuration > General > Batch.
    1. In Data Source JNDI Name, select the JNDI name of an XA-capable data source that will access the JobRepository tables for batch jobs.
    2. In Schema Name, enter the schema name where the JobRepository tables have been created.

      Note: If the JobRepository data source is shared by applications then this schema name must be same name that the application expects.

    3. In Executor Service Template, select the managed executor service (MES) template that will be used to run batch jobs in the domain. If an MES template is not selected, the default MES (as defined by the Java EE spec) will be used.
  4. Click Save.
  5. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Back to Top