Timer manager settings
Use this page to modify timer manager settings. Timer managers enable applications to schedule future timer notifications and to receive timer notification callbacks to application-specified listeners within a Java Platform, Enterprise Edition (Java EE) environment. The timer manager binds to the Java Naming and Directory Interface (JNDI) name space.
A timer manager contains a pool of threads bound into JNDI.
To view this administrative console page, click
.Scope
Specifies the scope of the configured resource. This value indicates the location for the configuration file.
Name
Specifies the name by which the timer manager is known for administrative purposes.
JNDI name
Specifies the JNDI name used to look up the timer manager in the namespace.
Description
Specifies a description of this timer manager for administrative purposes.
Category
Specifies a string that can be used to classify or group this timer manager.
![[z/OS]](../../images/ngzos.gif)
Default transaction class
Specifies the transaction class that is used for WLM workload classification of non-daemon work that is not already associated with a service class.
Information | Value |
---|---|
Data type | String |
Range | 0-8 characters |
Service names
Specifies a list of services to make available to this timer manager.
Asynchronous beans can inherit Java EE context information by enabling one or more Java EE service contexts on the timer manager resource in the product administrative console or by setting the serviceNames attribute of the TimerManagerInfo configuration object. When specifying the serviceNames attribute each enabled service should be separated by a semicolon, for example, security;UserWorkArea;com.ibm.ws.i18n. When a Java EE service context is enabled, it propagates the context from the scheduling thread to the target thread. If not enabled, the target thread does not inherit the context of the scheduling thread and a default context is applied. Any related Java EE context that is already present on the thread is suspended before any new Java EE context is applied.
The context information of each selected service is propagated to each timer that is created using this timer manager. Selecting services that are not needed can negatively impact performance.
Service name | Description |
---|---|
Internationalization | Use the administrative console or the com.ibm.ws.i18n service name to enable the internationalization context information. When the internationalization context and the Internationalization service is enabled, the internationalization context that exists on the scheduling thread is available on the target thread. This feature is optional. |
Security | Use the administrative console or the security service name to enable the Java Authentication and Authorization Service (JAAS) subject. When this feature and 管理安全 are enabled, the JAAS subject that is present on the scheduling thread is applied to the target thread. If not enabled, the target thread is run anonymously without a JAAS subject on the thread. This feature is optional. |
Work area | Use the administrative console or the UserWorkArea service name to enable work area partitions. When enabled, the work area context for every work area partition that exists on the scheduling thread is available on the target thread. This feature is optional. |
Number of timer threads
Specifies the maximum number of threads that are used for timers.
Information | Value |
---|---|
Data type | Integer |