Use this page to modify scheduler settings.
To view this administrative console page, click Resources > Schedulers > scheduler_name.
Configuration tab
The name by which this scheduler is known for administrative purposes.
Data type | String |
The JNDI name for the scheduler.
The JNDI name specifies where this scheduler instance is bound in the namespace. Clients can look this name up directly, although the use of resource references is recommended.
Data type | String |
A description of this scheduler for administrative purposes.
Data type | String |
A string that can be used to classify or group this scheduler.
Data type | String |
Data source where persistent tasks will be stored.
Any data source available in the name space can be used with a scheduler. Multiple schedulers can share a single data source while using different tables by specifying a table prefix.
Data type | String |
Alias to a user name and password used to access the data source.
Data type | String |
The prefix to apply to all of the scheduler tables and indices. This can optionally include a schema name if the database requires one.
Data type | String |
The interval at which the scheduler daemon polls the database.
Each poll operation can be expensive. If the interval is extremely small and there are many scheduled tasks, polling can consume a large portion of system resources.
Data type | Integer |
Units | Seconds |
Default | 30 |
Range | Any positive long integer |
Specifies work managers used by this scheduler.
The work manager is a server object that serves as a logical thread pool for the scheduler. Each repeating task that is created using this scheduler uses the Number of alarm threads specified in the work manager, which affect the number tasks that can run concurrently. Use the work manager Service Names property to limit the amount of context information that is propagated to the task when it runs.
Specifies whether to use the defined scheduler roles.
Schedulers require several user roles to plan for, develop, administer and operate the scheduler service: administrator, developer and operator. If checked, and global security is enabled, then administration roles are enforced when using scheduler JMX or APIs to create and modify tasks. If this option is not enabled, then all users can create and modify tasks.
Data type | check box |
Default | unchecked |
Range |
|
Related concepts
Scheduler daemon
Related tasks
Creating a scheduler resource reference
Configuring schedulers