WebSphere® ESB supports
a number of messaging bindings, which allow interoperability with
various messaging systems.
WebSphere ESB supports
the following messaging binding types:
- Java™ Message Service (JMS) 1.1 bindings
- JMS bindings allow interoperation with JMS providers that have
JCA 1.5 compliant resource adapters, such as the WebSphere Application
Server default messaging provider. JMS bindings provide connectivity
between the Service Component Architecture (SCA) environment and external Java messaging systems.
- Generic JMS bindings
- Non-JCA 1.5 compliant JMS providers that support the JMS 1.1 specification
and implement the JMS Application Server Facility are integrated by
generic JMS data bindings. The generic binding does not include custom
behavior for any providers.
- WebSphere MQ JMS bindings
- When WebSphere MQ is acting as a JMS provider, WebSphere MQ JMS bindings allow interoperation
with JMS applications that are using WebSphere MQ. WebSphere MQ JMS bindings provide a framework
for J2EE and service-oriented architecture (SOA) applications communicating
through WebSphere MQ. WebSphere MQ
JMS bindings expose the same model as other JMS bindings.
- WebSphere MQ bindings
- WebSphere MQ bindings expose a model that
is more familiar to a WebSphere MQ audience. WebSphere MQ bindings allow interoperation
with native WebSphere MQ or WebSphere Message
Broker applications, bringing these applications into the SOA framework
by providing mediation between, and communication with, them.
- HTTP bindings
- The HTTP binding is designed to provide SCA connectivity to HTTP.
This allows existing or newly-developed HTTP applications to participate
in the SOA environment.
Note: When you install an SCA module containing either WebSphere MQ JMS bindings or WebSphere MQ
bindings, the runtime is automatically configured to allow connectivity
with WebSphere MQ. However, the MQ systems administrator
must configure the WebSphere MQ queue managers,
because these are not automatically configured.