You can build enterprise applications that use Java™ Message Service (JMS) APIs directly to provide asynchronous messaging services. You can also use message-driven beans as asynchronous message consumers. If you are writing messaging programs that interoperate between WebSphere® Application Server and WebSphere MQ, there are some environmental differences that you need to take into account.
Enterprise applications can use JMS APIs directly to explicitly poll for messages on a JMS destination, then retrieve messages for processing by business logic beans (enterprise beans).
Message-driven beans can also be used as asynchronous message consumers. When a message arrives at the destination, the EJB container invokes the message-driven bean automatically without an application having to explicitly poll the destination.
In this information ...Related information
| IBM Redbooks, demos, education, and more(Index) |