Message-driven beans, activation specifications, and listener ports

Guidelines, related to versions of WebSphere® Application Server, to help you choose when to configure your message-driven beans to work with listener ports rather than activation specifications.

You can configure the following resources for message-driven beans:

If you want to use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter (for example the WebSphere MQ messaging provider or the V5 Default Messaging provider), you cannot use activation specifications and therefore you must configure your beans against a listener port. There are also a few scenarios in which, although you could use activation specifications, you might still choose to use listener ports. For example, for compatability with existing message-driven bean applications. Here are some guidelines, related to versions of WebSphere Application Server, to help you choose when to use listener ports rather than activation specifications:




Related concepts
Message-driven beans - automatic message retrieval
Message-driven beans - JCA components
J2C activation specification configuration and use
Message-driven beans - listener port components
Related tasks
Configuring an activation specification for a third-party JCA resource adapter
Configuring an administered object for a third-party JCA resource adapter
Configuring message listener resources for message-driven beans
Configuring a JMS activation specification for MDBs used by the default messaging provider
Deploying an enterprise application to use message-driven beans against JCA 1.5-compliant resources
Deploying an enterprise application to use message-driven beans with listener ports
Concept topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=cmb_aslp
File name: cmb_aslp.html