Configuring message listener resources for message-driven beans > Operating Systems: i5/OS
             Personalize the table of contents and search results

 

Start a listener port

 

Use this task to start a listener port on an application server, to enable the listeners for message-driven beans associated with the port to retrieve messages.

 

Overview

A listener is active, that is able to receive messages from a destination, if the deployed message-driven bean, listener port, and message listener service are all started. Although you can start these components in any order, they must all be in a started state before the listener can retrieve messages.

If configured as enabled, a listener port is started automatically when a message-driven bean associated with that port is installed. However, you can start a listener port manually, as described in this topic.

When a listener port is started, the listener manager tries to start the listeners for each message-driven bean associated with the port. If a message-driven bean is stopped, the port is started but the listener is not started, and remains stopped. If you start a message-driven bean, the related listener is started.

To start a listener port on an application server, use the administrative console to complete the following steps:

 

Procedure

  1. If you want the listener for a deployed message-driven bean to be able to receive messages at the port, check that the message-driven bean has been started.

  2. Display the collection list of listener ports:

    1. In the navigation pane, select Servers > Application Servers.

    2. In the content pane, click the name of the application server.

    3. Under Communications, click Messaging > Message Listener Service.

    4. Click Listener Ports.

  3. Select the check box for the listener port that you want to start.

  4. Click Start.

  5. Save your changes to the master configuration.




}

 

Related tasks


Administering listener ports