+

Search Tips   |   Advanced Search

 

Deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports

 

Use this task to deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports.

 

Overview

Although you can continue to deploy an EJB 2.0 message-driven bean against a listener port (as in WAS V5), you are recommended to deploy such beans as JCA 1.5-compliant resources and to upgrade them to be EJB 2.1 message-driven beans.

This task description assumes that you have an .EAR file, which contains an application enterprise bean with code for EJB 2.0 message-driven beans, that can be deployed in WebSphere Application Server.

To deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports...

 

Procedure

  1. Use the console to define the listener ports for the application, as described in Adding 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 Configure deployment attributes.

  3. Use the console to install the application.

    This stage is a standard WebSphere Application Server task, as described in Installing a new application.

    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.



Configure deployment attributes for an EJB 2.0 message-driven bean against a listener port

 

Related concepts


Message-driven beans - automatic message retrieval

 

Related tasks


Developing an enterprise application to use message-driven beans
Deploying and administering J2EE applications
Programming to use message-driven beans