Use asynchronous messaging
These topics describe how enterprise applications can use asynchronous messaging as a method of communication based on the JMS. With the support provided by WAS, applications can make use of JMS resources and message-driven beans.
Overview
WAS support for JMS 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.
You can use the WebSphere administrative console to administer the WAS 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 topics:
Procedure
- Learning about messaging with WAS
- Installing and configuring a JMS provider
- Using the default messaging provider
- Maintaining V5 default messaging resources
- Use the JMS resources provided by WebSphere MQ
- Use JMS resources of a generic provider
- Defect 329145 (rolled into 367507) this topic retitled to make it clear exactly what MDB resources it relates to:
- Programming to use asynchronous messaging
- Troubleshooting WebSphere messaging
Learning about messaging with WAS
Installing and configuring a JMS provider
Maintaining V5 default messaging resources
Use the JMS resources provided by WebSphere MQ
Use JMS resources of a generic provider
Administering listener ports and activation specifications for message-driven beans
Troubleshooting WebSphere messaging
Related tasks
Programming to use asynchronous messaging
Use the default messaging provider
Configure JMS resources for the synchronous SOAP over JMS endpoint listener