Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer the batch environment > Administer the batch environment
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 admin console or by scripting.
To configure the job scheduler using the scripting language, use the link to the job scheduler configuration administrative tasks provided in the related links at the bottom of this topic.
To configure the job scheduler using the admin console, see the following procedure.
Procedure
- 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 your own database. See the topic on creating a job scheduler and grid endpoint database for more information.
- Log on to the admin console.
- Expand System Administration > Job Scheduler. The job scheduler panel opens.
- In the Scheduler hosted by list, select the deployment target.
- Type the database schema name. The default is LRSSCHEMA.
- Select the data source JNDI name from the list. If the default of jdbc/lrsched is selected, the default embedded Derby job scheduler database is created.
- Type the directory where the job scheduler and the batch execution environment write the job logs. The default is ${GRID_JOBLOG_ROOT}/joblogs.
- Click OK and save the configuration.
- If administrative security is enabled, enable application security and secure the job scheduler. See the topic on securing the job scheduler for more information. Only authorized users who are granted the lrmonitor, lrsubmitter, and lradmin roles, or a combination of the roles, through the admin console are allowed access to the job management console.
Batch environment planning for transactional batch applications and compute-intensive applications
xJCL elements
Create the job scheduler and grid endpoint database
Configure WebSphere grid endpoints
Secure the job scheduler using roles
Submit batch jobs
Verify the job scheduler installation
Related
JobSchedulerCommands command group
Job scheduler custom properties
Job scheduler WebSphere variables