Deploy 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 Java EE Connector Architecture (JCA) 1.5-compliant resource adapter.
Message-driven beans can be configured as listeners on a JCA 1.5 resource adapter, such as the default messaging provider in WAS.
You deploy EJB 2.1 message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor properties. Although we can continue to deploy an EJB 2.0 message-driven bean against a listener port (as in WAS Version 5), we are recommended to deploy EJB 2.0 message-driven beans against JCA 1.5-compliant resources and to upgrade them to be EJB 2.1 message-driven beans.
This task description assumes that we 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 WAS.
To deploy an enterprise application to use message-driven beans against JCA 1.5-compliant resources...
- 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 Set an activation spec for the default messaging provider.
- For each message-driven bean in the application, configure the J2C deployment attributes
- Use the WAS admin console to install the application.
Set deployment properties for a JCA 1.5-compliant message-driven bean
Related concepts
Message-driven beans - automatic message retrieval
Related tasks
Designing an enterprise application to use message-driven beans
Develop an enterprise application to use message-driven beans
Deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports
Set security for EJB 2.1 message-driven beans
Deploy enterprise apps
Throttling inbound message flow for JCA 1.5 message-driven beans
Programming to use message-driven beans