The job scheduler accepts job submissions and determines where and when to run them. As part of managing jobs, the job scheduler persists job information in an external job database. Configurations for the job scheduler includes the selection of the deployment target, datasource JNDI name, database schema name, and endpoint job log location to be configured for the scheduler.
See Creating the job scheduler database for information on how to create a non-default job scheduler database.
If
you are using the Compute Grid component with the Operations Optimization component, the dynamic
application placement function with the job scheduler is supported.
The application placement controller, along with the scheduler and
autonomic request flow manager, provides overload protection of servers
as long as both online and batch workloads are on dynamic clusters.
This overload protection is not supported for static clusters member.
Since batch jobs can consume a lot of CPU and run for a long period
of time, utilization limit might be exceeded.
When the Operations Optimization component is installed with the
Compute Grid component, the application placement controller is consulted
by the job scheduler during its endpoint selection process. The custom
property, UseAPCEndpointSelection; value = false, can be configured
on the job scheduler to disable the application placement controller/job
scheduler integration. Use this custom property to disable the application
placement controller during the job scheduler's endpoint selection
process.
If there are multiple active editions of the Compute Grid application running in the cell, you can specify the custom property, default.edition.AppName=Edition, where AppName is the application name and Edition is the application edition which is specified during installation. For example, default.edition.TestBatchApplication=1.0. The value Base is used if the application edition is not defined. The job scheduler directs the job to the endpoint which hosts the default edition of that application if the xJCL does not specify the edition, as shown in the following code:
<job-scheduling-criteria> <required-capability expression="application_property$edition=1.0" /> </job-scheduling-criteria>
The job scheduler can be configured using the administrative console or by scripting. To configure the job scheduler using scripting language, use the link to the job scheduler configuration administrative tasks provided in the related links section at the bottom of this page. To configure the job scheduler using the administrative console, see the following procedure.