Creating work managers for custom thread groups

To create work managers, use the WebSphere Application Server Administration Console. If you expect many scheduler jobs of the same application type, create a separate work manager to limit the number of threads that handle these scheduler jobs. Otherwise, the existence of many scheduler jobs of the same type can create a bottleneck for other scheduler jobs.


  1. Open the WebSphere Integrated Solutions Console.
  2. Expand Resources > Asynchronous beans and click Work Managers.
  3. Select your scope from the list. 
    Node=localhost, Server=server1
  4. Click New.
  5. Create your custom work manager.
    1. Note the following default work managers:
      Work Manager name JNDI name Description Usage
      reserved wm/commerce/reserved Reserved Work Manager for IBM WebSphere Commerce Store publishing, Listener for WebSphere MQ, Scheduler monitoring, WebSphere Commerce audit.
      broadcast wm/commerce/scheduler/broadcast broadcast - Work Manager for IBM WebSphere Commerce Broadcast-related scheduler jobs.
      default wm/commerce/scheduler/default default - Work Manager for IBM WebSphere Commerce General scheduler jobs.
      inventory wm/commerce/scheduler/inventory inventory - Work Manager for IBM WebSphere Commerce Inventory-related scheduler jobs.
      auction wm/commerce/scheduler/auction auction - Work Manager for IBM WebSphere Commerce Auction-related scheduler jobs.
      search wm/commerce/scheduler/search search - Work Manager for IBM WebSphere Commerce Search-related scheduler jobs
      statistics wm/commerce/scheduler/statistics statistics - Work Manager for IBM WebSphere Commerce Statistics-related scheduler jobs
      At a minimum, you must use the default and broadcast thread groups, both of which must have nonzero maximum number of threads.
    2. Follow these guidelines to create your work managers:
      • Your work manager name must match your JNDI name.
      • You must use the wm/commerce/scheduler/ JNDI prefix. New work managers that use this JNDI prefix are automatically recognized by the scheduler.

        For customization, you can also use the following form for your JNDI prefix: wm/commerce/scheduler/mycompany, where mycompany is your company name for your custom assets.

    3. Set Work request queue full action to Fail.
    4. Select the following Service names:
      • WorkArea
      • Security
      • Globalization
    5. Provide the Thread pool properties values according to the recommended configuration:
      Property Value
      Number of alarm threads 2
      Minimum number of threads 0
      Maximum number of threads The extra number of database connections to add. This value varies, depending on the maximum number of jobs you anticipate are run in parallel during peak hours.
      Note: If the number is high, the number of database connections are also high.

      For more information, see WebSphere Application Server considerations.

      Thread priority 5
    6. Clear Growable for scheduler work managers. This parameter limits the number of scheduler threads that run parallel jobs of the same thread group.
    7. Click OK and then Save.
  6. When prompted, click Save again to apply the changes to the master configuration.
  7. Start the WebSphere Application Server administration server for the changes to take effect.
  8. The newly defined application type, that is, the work manager name, is available to be selected in the WebSphere Commerce Administration console. For more information, see Scheduling a site-level job.