Configure the job scheduler

The job scheduler accepts job submissions and determines where to run them. As part of managing jobs, the job scheduler stores job information in an external job database. Configurations for the job scheduler includes the selection of the deployment target, data source JNDI name, database schema name, and endpoint job log location to be configured for the scheduler.

Stand-alone application servers or clusters can host the job scheduler. The first time a server or cluster is selected to host the grid scheduler, an embedded Apache Derby database is automatically created, and configured to serve as the scheduler database if the default data source JNDI name jdbc/lrsched is selected.

The job scheduler can be configured using the administrative console or by scripting. This topic discusses how to configure the job scheduler using the administrative console.

The job scheduler process does not support multiple servants. Ensure that the wlm_maximumSRCount custom property is set to zero (0).

Tasks

1. Choose the environment to host the job scheduler.

   Use a stand-alone server for test environments. The stand-alone server can use the default Derby database. Use a cluster host for production environments.

   Although Derby is used as the default job scheduler database, we might want to use our own database. See the topic Create a job scheduler and grid endpoint database

2. Log on to the administrative console.

3. To view the Job scheduler page.
   System administration > Job scheduler

4. In the Scheduler hosted by list, select the deployment target.

5. Type the database schema name. The default is LRSSCHEMA.

6. Select the data source JNDI name from the list. If the default of (none) is selected, a default embedded Derby job scheduler database is created with a value of jdbc/lrsched.

7. Type the directory where the job scheduler and the batch execution environment write the job logs. The default is...
   ${GRID_JOBLOG_ROOT}/joblogs

8. Optional: Check a usage data check box.

   Specifies if the scheduler records job usage data for charge-back purposes in the scheduler database.

   (ZOS) Specifies if job usage data for jobs are to be written in SMF.

   (ZOS) Job usage data can be recorded with either SMF120 subtype 20 records or SMF120 subtype 9 records. Use the RECORD_SMF_SUBTYPES job scheduler custom property to indicate the preferred subtype.

9. Click OK and save the configuration.

10. If administrative security is enabled, enable application security and secure the job scheduler.

    Only authorized users granted the lrmonitor, lrsubmitter, and lradmin roles, or a combination of the roles, through the administrative console are allowed access to the job management console.

Subtopics

• Job scheduler WebSphere variables
  
• Job scheduler System Programming Interfaces (SPI)
  
• Create the job scheduler and grid endpoint database
  
• Verifying the job scheduler installation
  

Related:

Job management console

Environment planning for transactional batch applications and compute-intensive applications

xJCL elements

Configure WebSphere grid endpoints

Secure the job scheduler using roles

Submitting batch jobs

JobSchedulerCommands

Job scheduler custom properties