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


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 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. 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.

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


Procedure

  1. Start the admin console.

  2. 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.

  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.


Related


Message listener port collection
Listener port settings
Message-driven beans - listener port components
Create a new listener port
Start a listener port
Stop a listener port
Delete a listener port
Migrate 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
Administer listener ports

+

Search Tips   |   Advanced Search