Use the following tasks to configure resources needed by the message listener service to support message-driven beans for use with a JMS provider that does not have a JCA 1.5 resource adapter.
Before configuring message listener
resources for a message-driven bean, consider the Message Listener Service
implementation on the z/OS platform, which affects how you should configure
a listener port. For more information about the considerations, see Message Listener Service on z/OS.
For JMS messaging, message-driven beans can use a JMS provider that has a JCA 1.5 resource adapter, such as the default messaging provider that is part of WebSphere Application Server Version 6. With a JCA 1.5 resource adapter, you deploy EJB 2.1 message-driven beans as JCA resources to use a J2C activation specification. If the JMS provider does not have a JCA 1.5 resource adapter, such as the V5 Default Messaging and WebSphere MQ, you must configure JMS message-driven beans against a listener port (as in WebSphere Application Server Version 5).
If the message-driven
bean uses a queue hosted by WebSphere MQ as a JMS provider, you should optimize
performance by configuring the queue destination properties to best fit your
message-driven bean. For more information about performance considerations,
see Performance considerations for WebSphere MQ queue destinations.
If you want to deploy an enterprise application to use JMS message-driven beans with a JMS provider that does not have a JCA 1.5 resource adapter, refer to the following subtopics:
In this information ...Subtopics
| IBM Redbooks, demos, education, and more |