Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage message-driven beans > Manage message listener resources for message-driven beans > Administer listener ports
Create 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.
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.
If we have existing message-driven beans that use the WebSphere MQ messaging provider (or a compliant third-party JMS provider) with listener ports, and instead to use EJB 3 message-driven beans with listener ports, these new beans can continue to use the same messaging provider.
For more information about when to use listener ports rather than activation specifications, see Message-driven beans, activation specifications, and listener ports.
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. See Message-driven beans - listener port components.
Procedure
- Start the admin console.
- In the navigation pane, click...
> Server Types > WebSphere application servers ->server_name
> [Communications] Messaging > Message listener service > [Additional Properties] Listener Ports . The Message listener port collection panel is displayed.
- Click New.
- Specify the following required properties:
- Name
- The name by which the listener port is known for administrative purposes.
- Connection factory JNDI name
- The JNDI name for the JMS connection factory to be used by the listener port; for example, jms/connFactory1.
- Destination JNDI name
- The JNDI name for the destination to be used by the listener port; for example, jms/destn1.
- Optional: Change other properties for the listener port, as required.
- Click OK.
- Save your changes to the master configuration.
- To have the changed configuration take effect, stop then restart the application server.
Results
If you set the initial state of a listener port to Started, the listener port is started automatically when a message-driven bean associated with that port is installed.
Message-driven beans - listener port components
Configure a listener port
Start a listener port
Stop a listener port
Delete a listener port
Deploy an enterprise application to use message-driven beans with listener ports
Administer listener ports
Manage message listener resources for message-driven beans
Related
Listener port settings