WebSphere Extended Deployment V6.0.x     操作系统: AIX, HP-UX, Linux, Solaris, Windows, z/OS

Overview of JMS support in Extended Deployment

WebSphere Extended Deployment 6.0.1 extends the dynamic operations environment to 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 J2EE applications in a client container or J2EE applications running in an application server, Extended Deployment 6.0.1 only supports classification and flow control of messages for J2EE 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.

限制: 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.



相關概念
Overview of IIOP/JMS request flow prioritization
相關工作
Deploying an enterprise application with defined service levels
概念主题    

使用条款 | 反馈

最近更新日期: Aug 14, 2006 2:01:54 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/codoeiiopover.html

© Copyright IBM Corp. 2006. All Rights Reserved.
本信息中心基于 Eclipse 技术。(http://www.eclipse.org)