Set message listener resources for message-driven beans
Set the resources needed 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.
For WAS V7 and later, listener ports are deprecated. Therefore you should plan to migrate the WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, you should not begin this migration until we are sure the application does not have to work on appservers earlier than WAS V7. For example, if we have an appserver 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 appservers in the cluster to V7.
See about when to use listener ports rather than activation specifications, see Administer activation specifications and listener ports for message-driven beans.
To use message-driven beans with a messaging provider that does not have a JCA 1.5 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, we might still choose to use listener ports.
The message listener service is an extension to the JMS functions of the JMS provider and provides a listener manager, which controls and monitors one or more JMS listeners. Each listener monitors either a JMS queue destination (for point-to-point messaging) or a JMS topic destination (for publish/subscribe messaging). 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.
See Message-driven beans - listener port components.
- Set the message listener service.
- Administer listener ports. We can perform any of the following administrative tasks:
- Create or configure a listener port.
- Start or stop a listener port.
- Delete a listener port.
Set the message listener service
Administer listener ports
Related concepts
Message-driven beans - listener port components
Related tasks
Migrate a listener port to an activation spec for use with the WebSphere MQ messaging provider
Administer activation specifications and listener ports for message-driven beans
Related
manageWMQ