WAS v8.5 > Deploy applications > Deploy messaging resources > Deploy enterprise applications > Deploy enterprise applications developed as message-driven beans

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

Define the listener ports for the 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.

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

If we have existing message-driven beans that use the WebSphere MQ messaging provider (or a compliant third-party JMS provider) with listener ports, and instead 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 we have an EAR file, which contains an enterprise application developed as a message-driven bean, that can be deployed in WAS.

1. Define the listener ports for the application, using the dmgr console as described in Create 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 for a message-driven bean against a listener port.
3. Install the application, as described in Install enterprise application files with the console.

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

Subtopics

• Configure deployment attributes for a message-driven bean against a listener port
  We can configure the message-driven beans deployment attributes for an enterprise bean, to override the deployment attributes defined within the application EAR file.

Related concepts:

Message-driven beans - automatic message retrieval

Related

Designing an enterprise application to use message-driven beans
Develop an enterprise application to use message-driven beans
Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources
Migrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
Deploy enterprise applications

+

Search Tips   |   Advanced Search