Timer manager settings

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 2 Platform, Enterprise Edition (J2EE) environment. The timer manager binds to the JNDI name space.
A timer manager contains a pool of threads bound into JNDI.
To view this console page, click Resources > Asynchronous beans > Timer managers timermanager_name.

Related concepts

Java Authentication and Authorization Service

Related tasks

Configure timer managers

Related Reference
Administrative console scope settings Timer manager collection

Scope

Scope of the configured resource. This value indicates the location for the configuration file.

Name
Name by which the timer manager is known for administrative purposes.

Data type String

JNDI Name

Specify the JNDI name used to look up the timer manager in the namespace.

Data type String

Description

Specify adescription of this timer manager for administrative purposes.

Data type String

Category

Specify a string that can be used to classify or group this timer manager.

Data type String

Service Names

Specify a list of services to make available to this timer manager.
Asynchronous beans can inherit J2EE context information by enabling one or more J2EE service contexts on the timer manager resource in the WebSphere 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 J2EE 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 J2EE context that is already present on the thread is suspended before any new J2EE 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.

Work area Use the 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.
Security Use the console or the security service name to enable the JAAS subject. When this feature and administrative security 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.
Internationalization Use the 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.

Number of Timer Threads

Specify the maximum number of threads that are used for timers.

Data type Integer

Work area	Use the 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.
Security	Use the console or the security service name to enable the JAAS subject. When this feature and administrative security 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.
Internationalization	Use the 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.