JMS support in the Intelligent Management environment

Intelligent Management extends the dynamic operations environment to Java Message Service (JMS) by providing the capability to categorize and prioritize JMS messages. JMS messages can be classified by destination, that is, topic or queue. Service policies can be defined to prioritize messages differently based on the destination name.

While JMS messages can be consumed by standalone clients or enterprise applications in a client container or enterprise applications running in an application server, Intelligent Management only supports classification and flow control of messages for enterprise applications inside application server. For JMS, autonomic request flow manager gateways runs in the application server hosting the application, which means that JMS traffic is not handled by the ODR server.

For Message Driven Beans, service policy goals are based on the service times of the onMessage method. For synchronous JMS message consumers, service time is the interval between time of message delivery to the application and the application returning for the next message on the same consumer session.

Restriction: Routing policies including application edition based routing are not supported for JMS. Classification and flow control of JMS messages are only supported only when using the default message provider of WebSphere Application Server. A given destination is allowed to be part of only one JMS work class.

Related:

Overview of IIOP and JMS request flow prioritization

Deploy applications with defined service levels