WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

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

Use this task to deploy an enterprise application to use EJB 2.1 or EJB 2.0 message-driven beans for use with a JCA 1.5-compliant resource adapter.

Why and when to perform this task

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

You deploy EJB 2.1 message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor properties. Although you can continue to deploy an EJB 2.0 message-driven bean against a listener port (as in WebSphere Application Server version 5), you are recommended to deploy such beans against 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 message-driven beans, that can be deployed to use the default messaging provider in WebSphere Application Server.

To deploy an enterprise application to use message-driven beans against JCA 1.5-compliant resources, complete the following steps:

Steps for this task

  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.
  2. For each message-driven bean in the application, configure the J2C deployment attributes, as described in Configuring deployment attributes.
  3. Use the WebSphere administrative console to install the application.

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




Sub-topics
Configuring deployment properties for a JCA 1.5-compliant message-driven bean
Configuring security for EJB 2.1 message-driven beans
Throttling of inbound message flow for JCA 1.5 message-driven beans

Related concepts
Using message-driven beans to automatically retrieve messages

Related tasks
Developing an enterprise application to use message-driven beans
Deploying and administering applications

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tmb_depap.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)