WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

For WebSphere Application Server Version 7.0, the WebSphere MQ messaging
provider has enhanced administrative options supporting the following functions:
► WebSphere MQ channel compression
Data sent between WebSphere Application Server and WebSphere MQ can
be compressed, reducing the amount of data that is transferred.
► WebSphere MQ client channel definition table
The client channel definition table reduces the effort required to configure a
connection to a queue manager.
► Client channel exits
Client channel exits are pieces of Java code that you develop, and that are
executed in the application server at key points during the life cycle of a
WebSphere MQ channel. Your code 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
Transport-level encryption using SSL is the supported way to 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 WebSphere Application Server V7.0, you 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
(connection factories, JMS destinations, and so on). The concrete destinations
(queues and topic spaces) behind the default messaging provider interface are
implemented in a service integration bus. A service integration bus consists of
one or more bus members, which can be application servers 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
WebSphere Application Server messaging engine.
36 WebSphere Application Server V7.0: Concepts, Planning, and Design