Message-driven beans in applications

WAS supports asynchronous messaging as a method of communication based on the Java Message Service (JMS) programming interface.

Message-driven beans (a type of enterprise bean defined in the EJB 2.0 specification) extend the base JMS support and the Enterprise JavaBean component model to provide automatic asynchronous messaging. When a message arrives on a destination, a listener passes the message to a new instance of a user-developed message-driven bean for processing.

Use WebSphere Studio Application Developer to develop applications that use message-driven beans. You can use the WAS runtime tools, like the administrative console, to deploy and administer applications that use message-driven beans.

For more information on how to implement enterprise applications that use message-drive beans, see these topics:

An overview of message-driven beans
This topic provides an overview of message-driven beans, including their components and transaction support.

Design an enterprise application to use message-driven beans
This topic describes things to consider when designing an enterprise application to use message-driven beans.

Develop an enterprise application to use message-driven beans
This topic describes how to develop an enterprise application to use a message-driven bean.

Deploy an enterprise application to use message-driven beans
This topic describes how to deploy an enterprise application to use message-driven beans.

Important files for message-driven beans and extended messaging
This topic describes the files that are important for the operation of the WAS messaging service and should not be deleted.

Configure security for message-driven beans
This topic describes security considerations for message-driven beans.

Configure the message listener service
This topic describes how to configure message-driven beans using the administrative console.