These topics provide information about implementing WebSphere enterprise applications that use extended messaging.
Why and when to perform this task
WebSphere Application Server supports asynchronous messaging as a method of communication based on the Java Message Service (JMS) programming interface. Extended messaging extends the base JMS support, support for EJB 2.0 message-driven beans, and the Enterprise Java Bean (EJB) component model, to use the existing container-managed persistence and transactional behavior.
Using extended messaging, you can build enterprise beans that can provide messaging services along with methods that implement business logic. The enterprise beans can use the standard JMS styles of messaging (point-to-point and publish/subscribe). However, with extended messaging, the JMS usage is simplified, because JMS support is managed by the extended messaging service. This helps to effectively separate business logic from the messaging infrastructure. The use of data mapping enables messages to drive existing or new enterprise beans as though they were invoked from any EJB client.
You can use WebSphere Studio Application Developer Integration Edition to develop applications that use extended messaging. You can use the WebSphere Application Server runtime tools, like the administrative console, to deploy and administer applications that use extended messaging.
For more information about implementing WebSphere enterprise applications that use extended messaging, see the following topics: