Administer > Overview of administering a WebSphere Commerce site > Administration Console > Scheduler > Jobs > Scheduler configuration parameters


Create work managers for custom thread groups

Work managers can be created manually for customization using the WAS Administration Console. If you expect many scheduler jobs of the same application type, you should create a separate work manager to limit the number of threads handling these scheduler jobs. Otherwise, having many scheduler jobs of the same type can create bottleneck for other scheduler jobs.


Procedure

  1. Launch the WAS Administration Console.

  2. Expand...

    Resources | Asynchronous beans | Work Managers

  3. Select the scope from the list. For example,...

    Node=localhost, Server=server1

  4. Click New.

  5. Create the custom work manager.

    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.

  6. Create the new work managers following these guidelines:

    • Your work manager name must match the JNDI name.

    • You must use the wm/commerce/scheduler/ JNDI prefix. New work managers using this JNDI prefix are automatically recognized by the scheduler.

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

  7. Set Work request queue full action to Fail.

  8. Select the following Service names:

    • WorkArea
    • Security
    • Internationalization

  9. Fill in the Thread pool properties 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 executed in parallel during peak hours.

    If the number is high, the number of database connections will also be high.

    Thread priority 5

  10. Clear Growable for scheduler work managers. This limits the number of scheduler threads executing parallel jobs of the same thread group.

  11. Click OK and then Save.

  12. When prompted, click Save again to apply the changes to the master configuration.

  13. Restart the WAS administration server for the changes to take effect.

  14. The newly defined application type, that is, the work manager name, will be available to be selected in the WebSphere Commerce Administration console.


Related concepts

Scheduler configuration parameters


+

Search Tips   |   Advanced Search