WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage message-driven beans > Manage message listener resources for message-driven beans > Administer listener ports

Configure a listener port

Use this task to browse or change the properties of an existing listener port, which is used by message-driven beans associated with the port to retrieve messages.

To use message-driven beans with a messaging provider that does not have a JCA v1.5 or 1.6 resource adapter, we 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. 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. For more information, see Message-driven beans - listener port components.

When you deploy an enterprise application to use message-driven beans with listener ports, we can browse or change the configuration of a listener port.

  1. Start the dmgr console.
  2. In the navigation pane, click Servers > Server Types > WebSphere application servers->server_name > [Communications] Messaging > Message listener service > [Additional Properties] Listener Ports > listener_port

    The Message listener port page panel is displayed.

  3. Select the name of the listener port to work with. This displays the properties of the listener port in the content pane.

  4. Optional: Change properties for the listener port, according to your needs.

  5. Click OK.

  6. Save your changes to the master configuration.
  7. To have a changed configuration take effect, stop then restart the application server.


Subtopics


Related concepts:

Message-driven beans - listener port components


Related


Create a new listener port
Start a listener port
Stopping a listener port
Delete a listener port
Migrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
Deploy an enterprise application to use message-driven beans with listener ports


Reference:

Message listener port page
Listener port settings


+

Search Tips   |   Advanced Search