This is a list application scheduler settings that can be modified.
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 application scheduler. Each repeating task that is created using this application scheduler uses the number of alarm threads specified in the work manager, which affect the number of tasks that can run concurrently. Use the work managerService Names property to limit the amount of context information that is propagated to the task when it runs.
Application schedulers can be used by users with different roles in order to develop (Developer role), administer (Administrator role) and operate (Operator role) the application scheduler service. To enable global secureity, select that option. When this option is selected, the administration roles are enforced when using application scheduler JMX or APIs to create and modify tasks. If this option is not enabled, then all users can create and modify tasks. The table shown here shows the option parameters for administration roles.