Administering extended messaging resources: Overview

Extended messaging enables container-managed messaging. It extends the base Java™ Message Service (JMS) support, the Enterprise Java Bean (EJB) component model, and support for EJB 2.0 message-driven beans to allow use of the existing container-managed persistence and transactional behavior.

Extended messaging uses the bean-managed messaging implementation to provide the JMS interfaces, which ensures that both bean-managed and extended messaging use consistent JMS support. JMS usage is simplified since its support is managed by the extended messaging service.

The administrative console interface enables you to configure the resources needed by the extended messaging service and by the applications that use the service.

For a complete description of extended messaging, see the following articles in the WebSphere® Business Integration Server Foundation information center:
Note: The Extended Messaging Service feature is being deprecated in WebSphere Process Server 6.0. Although you can continue to use extended messaging with new and existing applications in this release, you will need to replace these applications with ones that use standard JMS APIs, or replace them with equivalent messaging technologies.
Related tasks
Enabling the extended messaging service
Configuring listener port extensions to handle late responses
Managing extended messaging providers
Adding a new input port
Adding a new output port

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)