Deploy an enterprise application to use message-driven beans against JCA 1.5-compliant resources
Overview
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.
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 one 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 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:
Procedure
- 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 each message-driven bean in the application, configure the J2C deployment attributes.
- Use the administrative console to install the application.
See also
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
See Also
Using message-driven beans to automatically retrieve messages
Related Tasks
Developing an enterprise application to use message-driven beans
Deploying and administering applications