Configuring work managers

Before you begin

If you are not familiar with work managers, review the conceptual topic Work managers.

Why and when to perform this task

A work manager acts as a thread pool for application components that use asynchronous beans. Use the administrative console to configure work managers. You can define multiple work managers for each cell. Each work manager is bound to a unique place in Java Naming and Directory Interface (JNDI).

Note: The work manager service is only supported from within the Enterprise Java Beans (EJB) Container or Web Container. Looking up and using a configured work manager from a J2EE application client container is not supported.

Steps for this task

  1. Start the administrative console.
  2. Select Resources > Work Managers.
  3. Click New.
  4. Specify the following required properties:
    Name
    The display name for the work manager.
    JNDI Name
    The JNDI name for the work manager. This name is used by asynchronous beans that need to look up the work manager. Each work manager must have a unique JNDI name within the cell.
    Number of Alarm Threads
    The maximum number of threads to use for processing alarms. A single thread is used to monitor pending alarms and dispatch them. An additional pool of threads is used for dispatching the threads. All alarm managers on the asynchronous beans associated with this work manager share this set of threads. A single alarm thread pool exists for each work manager, and all of the asynchronous beans associated with the work manager share this pool of threads.
    Minimum Number Of Threads
    The initial number of threads to be created in the thread pool.
    Maximum Number Of Threads
    The maximum number of threads to be created in the thread pool. The maximum number of threads can be exceeded temporarily if the Growable check box is selected. These additional threads are discarded when the work on the thread completes.
    Thread Priority
    The order of the priority for threads available in the thread pool.
  5. [Optional] Specify a Description and a Category for the work manager.
  6. [Optional] Select the Service Names (J2EE contexts) on which you want this work manager to be made available. Any asynchronous beans that use this work 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 work manager.
    Selecting more services than are actually required might impede performance.
  7. Save your configuration.

Results

The work manager is now configured and ready for access by application components that need to manage asynchronous code execution.

Related concepts
Work managers
Related tasks
Using asynchronous beans
Related reference
Work manager collection
Work manager service settings



Searchable topic ID:   tasb_workmanager
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/asyncbns/tasks/tasb_workmanager.html

Library | Support | Terms of Use | Feedback