Creating a new listener port
You create a new listener port for the message listener service to define the association between a connection factory, a destination, and a deployed message-driven bean. This association enables the message-driven bean to retrieve messages from the associated destination.
Before you begin
If you want to use message-driven beans with a messaging provider that does not have a JCA Version 1.5 or 1.6 resource adapter, 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 compatibility with existing message-driven bean applications.
If you have existing message-driven beans that use the WebSphere® MQ messaging provider (or a compliant third-party JMS provider) with listener ports, and instead you want to use EJB 3 message-driven beans with listener ports, these new beans can continue to use the same messaging provider.
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.
About this task
A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. This association 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.