WebSphere ESB supports
asynchronous messaging as a method of communication based on the Java Message
Service (JMS) programming interface. This JMS support is provided by one or
more JMS providers, and associated services and resources, that
you configure for use by enterprise applications. You can deploy EJB 2.1 applications
that use the JMS 1.1 interfaces and EJB 2.0 applications that use the JMS
1.0.2 interfaces. This support is provided by the WebSphere Application Server on
which WebSphere ESB is
built.
You can use the WebSphere administrative console to administer
the WebSphere ESB support
for asynchronous messaging. For example, you can configure messaging providers
and their resources, and can control the activity of messaging services.
For more information about implementing WebSphere
enterprise applications that use asynchronous messaging, see the following
sub-topics:
For more information about implementing
WebSphere enterprise applications that use asynchronous messaging, see the
following sub-topics in the infocenter. Alternatively, you can see Administering applications and their environment and
other PDF books available through theWebSphere Application Server Network Deployment library
Web page at http://www-306.ibm.com/software/webservers/appserv/was/library/.
- Learning about messaging with WebSphere Application
Server
Use this topic to learn about the use of asynchronous
messaging for enterprise applications with WebSphere ESB.
- Installing and configuring a JMS provider
This topic describes the different ways that you can use JMS providers
with WebSphere ESB.
A JMS provider enables use of the Java Message Service (JMS) and other message
resources in WebSphere ESB.
- Using the default messaging provider
This topic is the entry-point into a set of topics about enabling
WebSphere applications to use messaging resources provided by the default
messaging provider. The default messaging provider is installed and runs as
part of WebSphere Application Server, and is based on service integration
technologies.
- Maintaining Version 5 default messaging resources
This topic is the entry-point into a set of topics about maintaining
messaging resources provided for WebSphere Application Server, version 5 applications
by the default messaging provider.
- Using JMS resources of WebSphere MQ
This topic is the entry-point into a set of topics about enabling
WebSphere applications to use JMS resources provided by WebSphere MQ.
- Using JMS resources of a generic provider
This topic is the entry-point into a set of topics about enabling
WebSphere applications to use JMS resources provided by a generic messaging
provider (other than a WebSphere default messaging provider or WebSphere MQ).
- Administering support for message-driven beans
Use these tasks to manage resources used to support message-driven
beans. These tasks are in addition to the tasks for administering resource
adapters, JMS providers and the resources they provide.
- Troubleshooting WebSphere messaging
Use this overview task to help resolve a problem that you think is
related to the WebSphere Messaging. To identify and resolve problems that
you think are related to WebSphere Messaging, you can use the standard WebSphere ESB troubleshooting
facilities.