Schedulers collection

Use this page to manage scheduler configurations.

To view this administrative console page, click Resources > Schedulers.

 

Configuration tab

Name

The name by which this scheduler is known for administrative purposes.

Data type String

JNDI name

The JNDI name for the scheduler.

The JNDI name specifies where this scheduler instance is bound in the name space. Clients can look this name up directly, although the use of resource references is recommended.

Data type String

Data source JNDI name

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

Table prefix

The prefix to apply to all of the scheduler tables and indices. This can optionally include a schema name if the database requires one.

Multiple independent schedulers can share the same database if each instance specifies a different prefix string.

Data type String

Poll interval

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

Work managers

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 will use the "Number Of Alarm Threads" specified in the work manager, which affects 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.

When a task runs, 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.

Verify tables

Validates that scheduler data sources, table prefixes, security authentication information and tables are configured correctly.

Use this verification method in production and development environments without altering database properties.

Create tables

Creates the necessary tables and indices required for a scheduler to operate.

This method of creating scheduler tables is designed for simple topologies and development environments. Use the supplied scheduler data definition language files for advanced or production environments and for databases that do not support this feature. For details, see the topic "Creating Scheduler tables using the administrative console."

Drop tables

Specifies the removal of tables and indices required for schedulers to operate.

This method of removing scheduler tables and indices is recommended for development environments and does not delete previously scheduled tasks.

 

See also


Schedulers settings

 

See Also


Scheduler daemon