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.

See the topic about creating a non-default job scheduler and grid endpoint database.

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 console or by scripting. This topic discusses how to configure the job scheduler using the console. To configure the job scheduler using the scripting language, see information on the job scheduler configuration administrative tasks.

(zos) The job scheduler process does not support multiple servants. We must ensure that the wlm_maximumSRCount custom property is set to zero (0).gotcha

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, you might want to use our own database. See the topic on creating a job scheduler and grid endpoint database for more information.

2. Log on to the console.

3. Click System administration > Job scheduler to view the Job scheduler page.

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.

    See the topic on securing the job scheduler for more information. A link to the topic on securing the job scheduler is located at the bottom of this topic. Only authorized users who are granted the lrmonitor, lrsubmitter, and lradmin roles, or a combination of the roles, through the console are allowed access to the job management console.

Subtopics

• Job scheduler WebSphere variables
  Use WebSphere variables to modify the job scheduler configuration. We can configure the amount of time that the job scheduler waits before signaling a problem with the endpoint and waits between polling the endpoint.

• Job scheduler System Programming Interfaces (SPI)
  Use SPIs to manage a list of groups to which a user is assigned, to control user actions against jobs, to suppress the writing of log lines, and to provide an installation-specific audit string validation rule.

• Create the job scheduler and grid endpoint database
  We can create a database for the job scheduler and grid endpoint if we do not use the default Apache Derby database. The job scheduler stores job information in a relational database while the grid endpoint uses the database to track the progress of a batch job.

• Verify the job scheduler installation
  This topic describes how to verify that the job scheduler is installed correctly. The job scheduler is a system application and is not in the list of installed applications on the Enterprise applications page of an console.

Related concepts

Environment planning for transactional batch applications and compute-intensive applications

xJCL elements

Related tasks

Configure WebSphere grid endpoints

Secure the job scheduler using roles

Submitting batch jobs

JobSchedulerCommands (AdminTask)

Job scheduler custom properties