Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources
Manage message-driven beans
We can manage the Java EE Connector Architecture (JCA) v1.5-compliant message-driven beans that you deploy as message endpoints, and you can manage the message listener resources for non-JCA message-driven beans that you deploy against listener ports.
For WAS v7 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 WAS v7. For example, if we have an application server cluster with some members at v6.1 and some at v7, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to v7.
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 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.
For more information about when to use listener ports rather than activation specifications, see Message-driven beans, activation specifications, and listener ports.
We can 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.
Procedure
- Manage JCA 1.5-compliant message-driven beans that are 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 that are 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. We can manage the resources used by the message listener service, including being able to start and stop specific listener ports manually.
Related
Manage message listener resources for message-driven beans
Manage messaging with the WebSphere MQ messaging provider
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Manage messages with message endpoints
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
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
Manage messaging with the default messaging provider
Choosing a messaging provider