Creating a new listener port

You create a new listener port for the message listener service so that message-driven beans can be associated with the port to retrieve messages.

Before you begin

If you want to use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter (for example the WebSphere MQ messaging provider or the default messaging provider), 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 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.

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. For more information, see Message Listener Service on z/OS.

About this task

A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. This 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.

Procedure

  1. Start the administrative console.
  2. In the navigation pane, click

    The Message listener port collection panel is displayed.

  3. 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.
    The Message listener port collection panel is displayed.
  4. Click New.
  5. 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.
  6. Optional: Change other properties for the listener port, according to your needs.
  7. Click OK.
  8. Save your changes to the master configuration.
  9. 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.



In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=tmb_adm11
File name: tmb_adm11.html