Manage message-driven beans
Manage the Java EE Connector Architecture (JCA) Version 1.5-compliant message-driven beans that you deploy as message endpoints, and we can manage the message listener resources for non-JCA message-driven beans that you deploy against 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 the WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. For more information about how to configure activation specifications for non-ASF mode, see Configure activation specifications for non-ASF mode. 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 we have an application server cluster with some members at Version 6.1 and some at a later version, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to the later version.
To use message-driven beans with a messaging provider that does not have a JCA Version 1.5 or 1.6 resource adapter, we cannot use activation specifications and therefore configure the 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.
For more information about when to use listener ports rather than activation specifications, see Message-driven beans, activation specifications, and listener ports.
Manage the following resources for message-driven beans:
- JCA 1.5-compliant message-driven beans that you deploy as message endpoints, and the associated activation specifications.
- The message listener service, listener ports, and listeners for non-JCA message-driven beans that you deploy against listener ports.
- Manage JCA 1.5-compliant message-driven beans used as message endpoints.
JCA 1.5-compliant message-driven beans, deployed by using activation specifications, can be used as message endpoints. We can start and stop specific endpoints within the applications to ensure that messages are delivered only to listening message-driven beans that are interacting with healthy resources.
- Manage message listener resources for message-driven beans.
The message listener service supports message-driven beans used with a non-JCA messaging provider. A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. When you deploy a message-driven bean, you associate the bean with a listener port. When a message arrives on the destination, the listener passes the message to a new instance of a message-driven bean for processing. Manage the resources used by the message listener service, including being able to start and stop specific listener ports manually.
Subtopics
- Manage messages with message endpoints
Manage message delivery for message-driven beans (MDB) that are deployed as message endpoints. The message endpoints are managed beans (MBeans) for inbound resource adapters that are compliant with Java EE Connector Architecture (JCA) Version 1.5.
- Manage message listener resources for message-driven beans
Manage the resources used by the message listener service to support message-driven beans, typically for use with a messaging provider that does not have a Java EE Connector Architecture (JCA) 1.5 resource adapter.
Related tasks
Choose a messaging provider Manage messaging with the WebSphere MQ messaging provider Manage messaging with a third-party messaging provider Configure an activation specification for a third-party JCA resource adapter Configure an administered object for a third-party JCA resource adapter Configure an activation specification for the default messaging provider Manage messaging with the default messaging provider Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources Deploy an enterprise application to use message-driven beans with listener ports