Configure timer managers

 

Before you begin

If you are not familiar with timer managers, review the conceptual section, Timer managers, in the Asynchronous beans topic.

 

Overview

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.

We 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

1. Start the administrative console.

2. Select Resources > Asynchronous beans > Timer managers.

3. Click New.

4. Specify the following required properties:

   Name

   The display name for the timer manager.

   JNDI Name

   The 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.

5. [Optional] Specify a Description and a Category for the timer manager.

6. [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.

7. Save your configuration.

 

Result

The timer manager is now configured and ready for access by application components that need to manage the start of asynchronous code.

 

See also

Timer manager collection

 

---