Deploying an enterprise application to use message-driven beans against 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 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.

About this task

You deploy message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor attributes.

Procedure

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

    For example, for a message-driven bean to listen on a JMS destination of the default messaging provider, see Configuring a JMS activation specification for MDBs used by the default messaging provider.

  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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=tmb_depap
File name: tmb_depap.html