Deploying an enterprise application to use message-driven beans with listener ports

Define the listener ports for your application. For each message-driven bean in the application, configure the deployment attributes to match the listener port definitions. Install the application, specifying the name of the listener port to use for late responses.

Before you begin

Listener ports are stabilized. For more information, read the topic about stabilized features. You should only deploy your application against a listener port for compatability with existing message-driven bean applications. Otherwise, you should deploy your application against JCA 1.5-compliant resources.

If you have existing message-driven beans that use the WebSphere® MQ messaging provider (or a compliant third-party JMS provider) with listener ports, and instead you want to use EJB 3 message-driven beans with listener ports, these new beans can continue to use the same messaging provider.

This task assumes that you have an EAR file, which contains an enterprise application developed as a message-driven bean, that can be deployed in WebSphere Application Server.

Procedure

  1. Define the listener ports for your application, by using the WebSphere Application Server administrative console as described in Creating a new listener port.
  2. For each message-driven bean in the application, configure the deployment attributes to match the listener port definitions, as described in Configuring deployment attributes for a message-driven bean against a listener port.
  3. Install the application with the console.

    When you install the application, you are prompted to specify the name of the listener port that the application is to use for late responses. Select the listener port, then click OK.