Operating Systems: i5/OS
Personalize the table of contents and search results
Configure timer managers
A timer manager acts as a thread pool for application components
that use asynchronous beans. Use the administrative console to configure timer
managers. The timer manager service is enabled by default.
If you are not familiar with timer managers, review the conceptual
section, Timer managers, in the Asynchronous beans topic.
Overview
You can define multiple timer managers for each cell. Each timer
manager is bound to a unique place in Java Naming and Directory Interface
(JNDI).
Note: The timer manager service is only supported from
within the Enterprise Java Beans (EJB) container or Web container. Looking
up and using a configured timer manager from a J2EE application client container
is not supported.
Procedure
- Start the administrative console.
- Select Resources > Asynchronous beans > Timer managers.
- Specify a Scope value and click New.
- Specify the following required properties:
- Scope
-
The scope of the configured resource. This value indicates the location
for the configuration file.
- Name
-
The display name for the timer manager.
- JNDI Name
-
The Java Naming and Directory Interface (JNDI) name for the timer manager.
This name is used by asynchronous beans that need to look up the timer manager.
Each timer manager must have a unique JNDI name within the cell.
- Number of Timer Threads
-
The maximum number of threads that are used for timers.
- [Optional] Specify a Description and a Category for
the timer manager.
- [Optional] Select the Service Names (J2EE contexts) on which
you want this timer manager to be made available. Any asynchronous beans that
use this timer manager then inherit the selected J2EE contexts from the component
that creates the bean. The list of selected services also is known as the
"sticky" context policy for the timer manager. Selecting more
services than are actually required might impede performance.
- Save your configuration.
Results
The timer manager is now configured and ready for access by application
components that need to manage the start of asynchronous code.
}
Timer manager collection
|