Programming to use message-driven beans
Applications can use message-driven beans as asynchronous message consumers. You deploy a message-driven bean as a message listener for a destination. When a message arrives at the destination, the EJB container invokes the message-driven bean automatically without an application having to explicitly poll the destination.
We can use a tool such as Rational Application Developer to develop applications that use message-driven beans. We can use the WAS runtime tools, such as the console, to deploy and administer applications that use message-driven beans.
For more information about implementing enterprise applications that use message-drive beans, see the following topics:
- Develop message-driven beans.
- Design an enterprise application to use message-driven beans.
- Develop an enterprise application to use message-driven beans.
- Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources.
- Deploy an enterprise application to use message-driven beans with listener ports.
Subtopics
- Develop message-driven beans
We can develop a bean implementation class for a message-driven bean as introduced by the Enterprise JavaBeans specification. A message-driven bean (MDB) is a message consumer that implements business logic and runs on the server.
- Design an enterprise application to use message-driven beans
To help you design the enterprise application, consider a generic enterprise application that uses one message-driven bean to retrieve messages from a JMS queue destination, and passes the messages on to another enterprise bean that implements the business logic.
- Develop an enterprise application to use message-driven beans
Applications can use message-driven beans as asynchronous message consumers. You deploy a message-driven bean as a message listener for a destination. The message-driven bean is invoked by an activation specification or a JMS listener when a message arrives on the input destination that is being monitored.