Deploying an enterprise application to use message-driven beans with JCA 1.5-compliant resources

Message-driven beans can be configured as listeners on a Java™ EE Connector Architecture (JCA) 1.5 resource adapter, such as the default messaging provider or the WebSphere® MQ messaging provider in WebSphere Application Server.

Before you begin

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

Note: You can continue to deploy message-driven beans against a listener port. You might want to do this for compatability with existing message-driven bean applications. However, listener ports are stabilized, and you should plan to migrate all your message-driven beans to use JCA 1.5-compliant resources.

About this task

You deploy message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor attributes and (for EJB 3) as annotations.

Procedure

  1. For each message-driven bean in the application, create a J2C activation specification.

    For more information, see Configuring an activation specification for the default messaging provider or Creating an activation specification for the WebSphere MQ messaging provider by using the Create Activation Specification wizard.

  2. For each message-driven bean in the application, configure the J2C deployment attributes, as described in Configuring deployment attributes for a message-driven bean against JCA 1.5-compliant resources.
  3. Use the WebSphere Application Server administrative console to install the application.



In this information ...


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    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tmb_depap
File name: tmb_depap.html