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:
Activation specifications supersede the use of listener ports, which became a stabilized function in WebSphere Application Server version 7.0 (for more information, see Stabilized features). There are several advantages to using activation specifications over listener ports:

For WebSphere Application Server Version 7 and later, listener ports are stabilized. For more information, read the article on stabilized features. You should plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, you should not begin this migration until you are sure the application does not have to work on application servers earlier than WebSphere Application Server Version 7. For example, if you have an application server cluster with some members at Version 6.1 and some at Version 7, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to Version 7. Also, when you migrate to activation specifications on the z/OS® platform, you must enable the Control Region Adjunct (CRA) process of the application server (by using either the WebSphere MQ CRA settings panel or the manageWMQ command to include starting the CRA process as part of starting an application server).

If you want to use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter, 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 compatibility 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:

To assist in migrating listener ports to activation specifications, the WebSphere Application Server administrative console provides a Convert listener port to activation specification wizard on the Message listener port collection panel. This allows you to convert existing listener ports into activation specifications. However, this function only creates a new activation specification with the same configuration used by the listener port. It does not modify application deployments to use the newly created activation specification.




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
Migrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
Configuring an activation specification for a third-party JCA resource adapter
Configuring an administered object for a third-party JCA resource adapter
Managing message listener resources for message-driven beans
Configuring an activation specification for the default messaging provider
Deploying an enterprise application to use message-driven beans with JCA 1.5-compliant resources
Deploying an enterprise application to use message-driven beans with listener ports
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=cmb_aslp
File name: cmb_aslp.html