The application scheduler collection panel provides a list of existing...schedulers?. Each of the headings is described here. To add and configure a new application scheduler, select: Resources > Schedulers > New .
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.
Any data source available in the name space can be used with a application scheduler. Multiple schedulers can share a single data source while using different tables by specifying a table prefix.
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.
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.
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.
You can use this verification method in production and development environments without altering database properties.
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 and configuring application schedulers using the administrative console.
This method of removing scheduler tables and indices is recommended for development environments and does not delete previously scheduled tasks.
copy from here to there