Tasks WebSphere MQ | Connecting WAS to WebSphere MQ WebSphere MQ integration with WebSphere Application Server
For the WebSphere MQ messaging provider, admin options include...
WebSphere MQ channel compression Data sent between WAS and WebSphere MQ can be compressed, reducing the amount of data that is transferred. MQ client channel definition table Simplifies effort required to configure a connection to a queue manager. Client channel exits Custom Java code executed in the appserver at key points during the life cycle of a WebSphere MQ channel that can change the runtime characteristics of the communications link between the WebSphere MQ messaging provider and the WebSphere MQ queue manager. Transport-level encryption using SSL Configure SSL for JMS resources associated with the WebSphere MQ messaging provider. The SSL configuration is associated with the communication link for the connection factory or activation specification. Automatic selection of the WebSphere MQ transport type Servers in a cluster can be configured automatically to select their transport. In WAS V7.0, we can use the following JMS providers:
- The default messaging provider
- WebSphere MQ
- Third-party JMS providers
- V5 default messaging provider (for migration purposes)
The default messaging provider is the JMS API implementation for messaging...
The concrete destinations (queues and topic spaces) behind the default messaging provider interface are implemented in a service integration bus, which consists of one or more bus members, which can be appservers or clusters.
Each bus member will have one messaging engine (more, in the case of clusters) that manages connections to the bus and messages. A service integration bus can connect to other service integration buses and to WebSphere MQ. Similarly, the WebSphere MQ JMS provider is the JMS API implementation with WebSphere MQ (with queue managers, for example) implementing the real destinations for the JMS interface. WebSphere MQ can coexist on the same host as a WAS messaging engine.
In general, the default messaging provider is a good choice for the following circumstances:
- You are currently using the WAS V5 embedded messaging provider for intra- messaging.
- You require messaging between WAS and an existing WebSphere MQ backbone and its apps.
The WebSphere MQ messaging provider is good choice for the following circumstances:
- You are currently using a WebSphere MQ messaging provider and simply want to continue using it.
- You require access to heterogeneous, non-JMS Enterprise Information Systems (EIS).
- You require access to WebSphere MQ clustering.
Using a topology that combines WebSphere MQ and the default messaging provider gives we the benefit of the tight integration between WebSphere and the default messaging provider (clustering), and the flexibility of WebSphere MQ.