The database administrator must create the job repository tables needed to persist batch job details. The schema name used to created these tables will be denoted by the getSchemaName() method in the BatchConfigMBean when configuring the batch runtime for the domain. See Configure the Batch Runtime to Use a Dedicated Batch Data Source and Managed Executor Service.

The job repository tables can be created using the Repository Create Utility (RCU) or using SQL scripts for the databases supported for use with WebLogic Server 14c. Schemas for creating these tables are in the following location:

ORACLE_HOME/oracle_common/common/sql/wlservices/batch/dbname

Iwhere ORACLE_HOME represents the top level installation directory for Oracle WebLogic Server, and dbname represents the name of the database.

For information about the supported databases for WebLogic Server 14c, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network.

• Creating Job Repository Tables Using RCU
  
• Creating Job Repository Tables Using an SQL Script
  

For a dedicated batch runtime within a domain, the WebLogic administrator must configure an XA-capable data source for the database that will contain the job repository tables. When a Jakarta EE component submits a batch job, the batch runtime updates the job repository tables using this XA data source, which is obtained by looking up the data source's JNDI name.

When you create the batch data source using WLST, you must use the schema owner created with RCU (e.g., jbatch_wls) or the SQL script jbatch, as described in Create the Job Repository Tables.

For instructions on configuring JDBC data source, see Creating a JDBC Data Source in Administering JDBC Data Sources for Oracle WebLogic Server.

For optimum performance, the batch runtime can be configured to use application-scoped Managed Executor Services by configuring Managed Executor Service Templates (MES Template) that use the same name as the batch runtime setBatchJobsManagedExecutorServiceName(). If no MES Template is specified when configuring the batch runtime, it will instead use the default Jakarta Managed Executor Service that is bound to (java:comp/DefaultManagedExecutorService).

When a new instance of a Managed Executor Service is created for each MES template, it will then run batch jobs that are submitted for applications that are deployed to the domain. For example, if there are two MES Templates named MES1 and MES2 in a domain, then when BatchApp1 and BatchApp2 are deployed, each application will get an instance of MES1 and MES2.

However, if you have set the setBatchJobsExecutorServiceName("MES2"), then all batch jobs submitted from BatchApp1 or BatchApp1 (or from any application deployed to the domain), will use MES2.

For instructions on configuring a Managed Executor Service Template, see Configuring Concurrent Managed Objects.

You can use WLST with the BatchRuntimeConfigMBean and DomainMBean to configure the batch runtime to use a specific database for the job repository:

def update_domain_batch_config(domainName, jndiName, schemaName):
    connect('admin','passwd')
    edit()
    startEdit()
    cmo.setDataSourceJndiName(jndiName)
    cd('/BatchConfig/' + domainName)
    cmo.setSchemaName(schemaName)
    save()
    activate()

In this example, if the administrator has created a data source with the JNDI name jdbc/batchDS, then, calling update_domain_batch_config('mydomain','jdbc/batchDS','BATCH') will configure the batch runtime to store all the job repository tables in the schema 'BATCH' in the database that is pointed by the data source that is bound to the jndiName: 'jdbc/batchDS'.

You can use WLST to configure the batch runtime to use specific Managed Executor Services for batch job execution. However, you must first create an Managed Executor Service and the name of the Managed Executor Service must be provided to the DomainMBean.

   connect('admin','passwd')
    edit()
    startEdit()
    cmo.setBatchJobsExecutorServiceName('mesName')
    save()
    activate()

where mesName is the name of the Managed Executor Service that has already been created (and targeted) to this domain.

The batch runtime can be configured to use different Managed Executor Services using the getBatchJobsManagedExecutorServiceName() method in the DomainMBean. However, a Managed Executor Service Template by the same name must exist and be targeted to the domain scope when a batch job is submitted.

See the BatchConfigMBean and DomainMBean in the MBean Reference for Oracle WebLogic Server.

See WebLogic Server WLST Online and Offline Command Reference in the WLST Command Reference for Oracle WebLogic Server.

The getJobDetails() attribute returns details about all the jobs submitted by applications deployed to the domain. Each entry in the collection contains an array of the elements.

Table 6-1 describes the elements in the getJobDetails attribute in the BatchJobRepositoryRuntimeMBean.

Here is an example of a WLST script that uses getJobDetails() to print a list of all batch jobs deployed in a domain.

connect('admin', 'admin123')
domainRuntime()
cd('BatchJobRepositoryRuntime')
cd('myserver')
executions=cmo.getJobDetails(6)
print "JobName  AppName   InstanceID  ExecutionID  BatchStatus  StartTime  EndTime  ExitStatus"
 print e[0], " ", e[1], " ", e[2], "   ", e[3], "  ", e[4], "  ", e[5], " ", e[6],   ",e[7]

Here is sample output after running getJobDetails():

JobName   InstanceID  ExecutionID   BatchStatus       StartTime                      EndTime                   ExitStatus
PayrollJob     6           6         COMPLETED   Fri Apr 24 10:11:00 PDT 2015   Fri Apr 24 10:11:01 PDT 2015   COMPLETED
PayrollJob     5           5         COMPLETED   Fri Apr 24 10:10:57 PDT 2015   Fri Apr 24 10:10:58 PDT 2015   COMPLETED
PayrollJob     4           4         COMPLETED   Fri Apr 24 10:10:56 PDT 2015   Fri Apr 24 10:10:56 PDT 2015   COMPLETED
PayrollJob     3           3         COMPLETED   Mon Apr 20 11:32:12 PDT 2015   Mon Apr 20 11:32:12 PDT 2015   COMPLETED
PayrollJob     2           2         COMPLETED   Mon Apr 20 11:32:10 PDT 2015   Mon Apr 20 11:32:11 PDT 2015   COMPLETED
PayrollJob     1           1         COMPLETED   Mon Apr 20 11:25:26 PDT 2015   Mon Apr 20 11:25:26 PDT 2015   COMPLETED

The getJobExections attribute returns details about a particular job execution. Each entry in the collection contains an array of the elements.

Table 6-2 describes the elements in the getJobExecutions() attribute of the BatchJobRepositoryRuntimeMBean.

Here is an example of using getJobExectuions() in a WLST script to get details for a given ExecutionID: getJobExecutions(6). To get a list of all ExecutionIDs, use the getJobDetails() method.

connect('admin', 'admin123')
domainRuntime()
cd('BatchJobRepositoryRuntime')
cd('myserver')
executions=cmo.getJobExecutions(6)
print  "JobName    InstanceID   ExecutionID   BatchStatus   StartTime   EndTime    ExitStatus"
for e in executions
   print e[0], "  ", e[1], "    ", e[2], "    ", e[3], "    ", e[4], "  ", e[5], "  ", e[6]

Here is sample output after running getJobExecutions():

JobName   InstanceID  ExecutionID   BatchStatus       StartTime                      EndTime                   ExitStatus
PayrollJob     6           6         COMPLETED   Fri Apr 24 10:11:00 PDT 2015   Fri Apr 24 10:11:01 PDT 2015    COMPLETED

The getStepExecutions attribute returns metrics about each step in a Job execution. Each entry in the collection contains an array of the elements.

Table 6-3 describes the elements in the getStepExecutions() attribute in the BatchJobRepositoryRuntimeMBean.

Here is an example of using getStepExecutions() in a WLST script to get details for a given StepExecutionID: getStepExecutions(6). To get a list of all ExecutionIDs, use the getJobDetails() method.

connect('admin', 'admin123')
domainRuntime()
cd('BatchJobRepositoryRuntime')
cd('myserver')
executions=cmo.getStepExecutions(6)
print  "StepName   StepExecutionID   BatchStatus    StartTime    EndTime    ExitStatus"
   print e[0], "     ", e[1], "      ", e[2], "     ", e[3], " ", e[4], "   ", e[5], "]

Here is sample output after running getStepExecutions():

StepName   StepExecutionID  BatchStatus       StartTime                      EndTime                   ExitStatus
PayrollJob     6           6         COMPLETED   Fri Apr 24 10:11:00 PDT 2015   Fri Apr 24 10:11:01 PDT 2015    COMPLETED