Programming to use asynchronous messaging
This topic describes things to consider when designing an enterprise application to use the JMS API directly for asynchronous messaging.
Overview
You can build enterprise beans that use the JMS API directly to provide messaging services along with methods that implement business logic. An enterprise application can explicitly poll for messages on a JMS destination then retrieve messages for processing by business logic beans (enterprise beans).
You can also use message-driven beans (a type of enterprise bean defined in the EJB specification) as asynchronous message consumers. A message-driven bean is invoked by the EJB container when a message arrives at the destination that it is configured to use, without an application having to explicitly poll the destination.
Procedure
- Programming to use JMS and messaging directly This topic provides information about using the JMS (JMS) programming interfaces directly to exchange messages asynchronously.
- Programming to use message-driven beans This topic provides information about using message-driven beans as asynchronous message consumers.
Programming to use JMS and messaging directly
Programming to use message-driven beans
JMS interfaces
JMS and WebSphere MQ message structures