Use this page to modify scheduler settings.
To view this administrative console page, click Resources > Scheduler Configurations > scheduler_name.
Configuration tab
Data type | String |
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 |
Data type | String |
Data type | String |
Any datasource available in the name space can be used with a scheduler. Multiple schedulers can share a single datasource while using different tables by specifying a table prefix.
Data type | String |
Data type | String |
Multiple independent schedulers can share the same database if each instance specifies a different prefix string.
Data type | String |
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 |
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 will use the "Number Of Alarm Threads" specified in the Work Manager which will affect the number tasks that can run concurrently. Use the Work Manager's "Service Names" property to limit the amount of context information that is propagated to the task when it executes.
When a task fires, the task is run in the work manager associated with the scheduler instance. Configuring a scheduler with a specific work manager enables you to control how many tasks are actively running at a given time.
Note: Although work managers and scheduler instances are configured at different scopes, a scheduler must reference a work manager in the same scope. For example, a scheduler instance configured at the server1 scope must use a work manager also configured at the server1 scope.