Default messaging provider activation specifications and workload management on WebSphere Application Server for z/OS

Workload management (WLM) enables messages to be processed in a certain order based upon transaction class. With default messaging provider (service integration) activation specifications, workload management is always active.

When there is a backlog of messages on the IBM MQ queue for your message-driven bean (MDB), you want some messages to be processed before other message based on transaction class.

The workload management (WLM) feature of WebSphere® Application Server for z/OS® enables messages to be processed in a certain order based on transaction class. Workload management prioritization occurs when message IDs have been placed on the WLM queue.

Workload management is always active when you are using service integration as the messaging provider. However, for optimal workload management you can configure Maximum concurrent MDB invocations per endpoint on the activation specification to be the value of how many concurrent MDB invocations you want to run across all of the servant regions for the activation specification. It is important to note that each servant region is limited to 10 MDB invocations at any one time.