(zos)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 WebSphere MQ queue for the message-driven bean (MDB), we want some messages to be processed before other message based on transaction class.
The workload management (WLM) feature of WAS 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 we are using service integration as the messaging provider. However, for optimal workload management we can configure Maximum concurrent MDB invocations per endpoint on the activation specification to be the value of how many concurrent MDB invocations 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.
Related concepts
(zos) The message-driven bean throttling mechanism on z/OS
(zos) MDB throttle settings for message-driven beans on z/OS
(zos) Messaging flow for ASF message-driven beans with WebSphere MQ as the messaging provider
(zos) Tune listener ports for workload management on WebSphere Application Server for z/OS