Application scheduler settings

This is a list application scheduler settings that can be modified.

Draft comment:
This topic has been diamondiszed from WAS 6.0.
To view this administrative console page, select: Resources > Scheduler > scheduler_name.
Draft comment:
Is this path still correct or relevant?

Configuration Tab

Name
The name of the application scheduler.
Data Type
String
JDNI Name
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
Description
A description of the application scheduler.
Data Type
String
Category
A string that can be used to classify or group the application scheduler.
Data Type
String
Data source JNDI name
Data source where persistent tasks are stored.

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.

Data Type
String
Data source alias
Alias to a user name and password used to access the data source.
Data Type
String
Table prefix
The prefix to apply to all of the application scheduler tables and indices. This can optionally include a schema name if the database requires one.
Data Type
String
Poll Interval
The time interval the application 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 application scheduler.

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.

When a task runs, the task is run in the work manager associated with the application scheduler instance. You can control the number of actively running tasks at a given time by configuring application schedulers with a specific work manager. The number of tasks that can run concurrently is governed by the number of alarm threads parameter on the work manager.
Note: Although work managers and application scheduler instances can be configured at different scopes, application schedulers must reference a work manager in the same scope. For example, a application scheduler instance configured at the server1 scope must use a work manager also configured at the server1 scope.
Use administration roles
Specifies defined application scheduler roles to use.

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.

Data Type
check box
Default
30
Range
  • Operator--Calls any of the scheduler MBean or API methods and runs any of the scheduler administrative console functions.
  • Monitor--Calls the scheduler MBean or API methods, but cannot create tasks or modify the state of any tasks. Only read-only methods and properties are accepted.

Copyright IBM Corp. 2003, 2005 |