Network Deployment (Distributed operating systems), v8.0 > Applications
Messaging resources
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WAS.
WAS supports asynchronous messaging based on the JMS and the Java EE Connector Architecture (JCA) specifications, which provide a common way for Java programs (clients and Java EE applications) to create, send, receive, and read asynchronous requests, as messages.
JMS support enables applications to exchange messages asynchronously with other JMS clients by using JMS destinations (queues or topics). Some messaging providers also allow WAS applications to use JMS support to exchange messages asynchronously with non-JMS applications; for example, WAS applications often need to exchange messages with traditional WebSphere MQ applications. Applications can explicitly poll for messages from JMS destinations, or they can use message-driven beans to automatically retrieve messages from JMS destinations without explicitly polling for messages.
WAS supports the following messaging providers:
- The WAS default messaging provider (which uses service integration as the provider).
- The WebSphere MQ messaging provider (which uses your WebSphere MQ system as the provider).
- Third-party messaging providers that implement either a JCA v1.5 resource adapter or the ASF component of the JMS v1.0.2 specification.
- Styles of messaging in applications
Applications can use point-to-point and publish/subscribe messaging. These styles of messaging can be used in the following ways: one-way; request and response; one-way and forward.
- Types of messaging providers
We can configure any of three main types of JMS providers in WAS: The WAS default messaging provider (which uses service integration as the provider), the WebSphere MQ messaging provider (which uses your WebSphere MQ system as the provider) and third-party messaging providers (which use another company's product as the provider).
- Default messaging
Use these topics to learn about using the default messaging provider to support the use of the JMS by enterprise applications deployed on WAS.
- Interoperation with WebSphere MQ
We can enable JMS interaction with a WebSphere MQ network by using the WebSphere MQ messaging provider. Service integration can also provide interoperation through a WebSphere MQ link or a WebSphere MQ server. Each type of connectivity is designed for different situations, and provides different advantages.
- Message-driven beans - automatic message retrieval
WAS supports the use of message-driven beans as asynchronous message consumers.
- JMS interfaces - explicit polling for messages
Applications can use JMS to explicitly poll for messages on a destination, then retrieve messages for processing by business logic beans (enterprise beans).
- JMS components on v5 nodes
To provide messaging support on a WAS v5 node, there is at most one JMS server and some number of JMS resources configured for the default messaging JMS provider on that node.
End-to-end paths for Messaging resources
Migrate Messaging resources
Administer Messaging resources
Scripting for Messaging resources
Secure Messaging resources
Develop Messaging resources
Tune Messaging resources
Troubleshoot Messaging resources