Manage message-driven beans
We can manage the Java EE Connector Architecture (JCA) Version 1.5-compliant message-driven beans that we deploy as message endpoints, and we can manage the message listener resources for non-JCA message-driven beans that we deploy against listener ports.
For WebSphere Application Server v7 and later, listener port are stabilized. We should plan to migrate the IBM MQ message-driven bean deployment configurations from using listener ports to using activation specifications. See Configure activation specifications for non-ASF mode. However, we should not begin this migration until we 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 a later version, we should not migrate applications on that cluster to use activation specifications until after we 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 beans against a listener port. There are also a few scenarios in which, although we could use activation specifications, we might still choose to use listener port. For example, for compatibility with existing message-driven bean applications.
For more information about when to use listener port 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 we deploy as message endpoints, and the associated activation specifications.
- The message listener service, listener port, and listeners for non-JCA message-driven beans that we deploy against listener port.
Tasks
- Manage JCA 1.5-compliant message-driven beans used as message endpoints.
- Manage message listener resources for message-driven beans.
Choose a messaging provider IBM 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