WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Configuring message listener resources for message-driven beans

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 you begin [z/OS]

[z/OS] 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.

About this task

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).

[z/OS] 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.

Here are some guidelines on which scenarios use listener ports or activation specifications:
  • If you are using J2EE 1.2 and EJB 1.1 with WebSphere Application Server v4, MDBs are not used, so you do not used listener ports or activation specifications because WebSphere Application Server v4 uses message beans, but these are not MDbs or EJBs.
  • If you are using J2EE 1.3 and EJB 2.0 with WebSphere Application Server v5, you must use listener ports. The MDBs are JMS MDBs that implement MessageListener, and there is no JCA support. WebSphere Application Server v5 uses listener ;ports to associate MDB classes with their JMS destinations.
  • If you are using J2EE 1.4 and EJB 2.1 with WebSphere® Application Server v6, the decision depends on whether your JMS provider API is implemented with JCA. In J2EE 1.4, the JMS 1.1 API can be implemented with the JCA 1.5 API.
    • If your JMS provider API is implemented with JCA, your MDB is a JMS MDB that is implemented as a connector MDB. A connector MDB uses JCA to access its resources, and so the connector must be configured with an activation specification. This is for new bean development, and does not affect the conversion of MDBs from EJB 2.0 to EJB 2.1.
    • If your JMS provider API is not implemented with JCA, you have the same JMS situation as for Java™ EE 1.3, and you must configure this EJB 2.1 MDB in the same way as you would configure an EJB 2.0 MDB, which in WebSphere Application Server is to use a listener port.

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:

Procedure




In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tmb_admin.html