Timer manager settings

Timer manager settings

Use this page to modify timer manager settings.
A timer manager contains a pool of threads bound into JNDI.
To view this administrative console page, click Resources > Asynchronous beans > Timer managers timermanager_name.

Configuration tab

Scope

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

Name

The name by which the timer manager is known for administrative purposes.

Data type String

JNDI Name

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

Data type String

Description

A description of this timer manager for administrative purposes.

Data type String

Category

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

Data type String

Service Names

A list of service names on which this timer manager is made available.
Asynchronous beans can inherit J2EE context information by enabling one or more J2EE service contexts on the timer manager resource in the WebSphere administration 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 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.
Security Use the administrative console or the security service name to enable the JAAS subject. When this feature and global 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 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.

Number of Timer Threads

The maximum number of threads that are used for timers.

Data type Integer

See Also

Java Authentication and Authorization Service
Work area partition service

Related Tasks

Configuring timer managers

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