You create a new listener port for the message listener service so that message-driven beans can be associated with the port to retrieve messages.
If you want to use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter (for example the WebSphere MQ messaging provider or the V5 Default Messaging provider), 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 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.
Before configuring message listener resources, consider the message listener service implementation on the z/OS® platform, which affects how you should configure your listener port. For more information, see Message Listener Service on z/OS.
A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. This enables deployed message-driven beans associated with the port to retrieve messages from the destination. For more information, see Message-driven beans - listener port components.
In this information ...Related concepts
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |