+

Search Tips   |   Advanced Search

Programming to use message-driven beans


Applications can use message-driven beans (a type of enterprise bean defined in the EJB specification) 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. The message-driven bean implements some business logic to process incoming messages on the destination.

EJB 2.0 message-driven beans support only JMS messaging. EJB 2.1 message-driven beans can handle other messaging types in addition to JMS. The message-driven bean class must implement the message listener interface for the messaging type that the message-driven bean handles. For example, an EJB 2.1 message-driven bean class used for JMS messaging must implement the javax.jms.MessageListener interface.

Use Rational Application Developer to develop applications that use message-driven beans. Use the WAS runtime tools, like the admin console, to deploy and administer applications that use message-driven beans.

See about implementing WebSphere enterprise applications that use message-drive beans, see the following topics:

 


Designing 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 against JCA 1.5-compliant resources
Deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports

 

Related tasks


Programming to use asynchronous messaging