Enabling SOA Using WebSphere Messaging

Chapter 2. Product selection 37

For more information

You can find more information about IBM WebSphere Message Broker at the

WebSphere Message Broker home page:

http://www.ibm.com/software/integration/wbimessagebroker/

2.6 ESB product comparison

The product you select to implement an ESB depends on the requirements of

your solution. We have introduced two strategic products and described them.

Now we provide a quick comparison of the two.

WebSphere ESB is designed to provide the core functionality of an enterprise

service bus for a predominantly Web services based environment. It is built on

WebSphere Application Server, which provides the foundation for the transport

layer. WebSphere ESB adds a mediation layer based on the SCA programming

model on top of this foundation to provide intelligent connectivity. If the client has

a lot of Web services in their environment, WebSphere ESB is likely to be the

better product to use.

WebSphere Message Broker provides a more advanced ESB solution with

advanced integration capabilities such as universal connectivity and any-to-any

transformation for data-centric deployments. It can handle services integration as

well as integration with non-services applications. WebSphere MQ provides the

transport backbone for messaging applications. Typically, clients who need a

higher performance and throughput product in a message-centric environment

would use Message Broker.

For a quick comparison of WebSphere MQ and WebSphere Message Broker

see Table 2-1 on page 38.

38 Enabling SOA Using WebSphere Messaging

Table 2-1 WebSphere ESB versus WebSphere Message Broker

WebSphere ESB WebSphere Message Broker

Connectivity 򐂰 MQ/JMS (via MQLINK

configuration) JMS 1.1

(point-to-point, pub/sub)

򐂰 TCP/IP, SSL, HTTP(S), IIOP

򐂰 Native MQ, JMS 1.1

(point-to-point, pub/sub)

򐂰 Supports input handling for

virtually all third-party JMS

systems

򐂰 TCP/IP, SSL, HTTP(S), CICS®,

VSAM, flat-files

򐂰 Supports MQ Enterprise

Transport, MQ Mobile Transport,

MQ Multicast Transport, MQ

Realtime Transport, MQ

Telemetry Transport, MQ Web

Services Transport, JMS

Transport

Web services support 򐂰 SOAP/HTTP(S), SOAP/JMS,

WSDL 1.1

򐂰 Supports WS-I Basic Profile 1.1

򐂰 UDDI 3.0 Service Registry

򐂰 WS-Security, WS-Atomic

Transactions

򐂰 Comprehensive client support by

Message Service Client for

C/C++ and .NET, Web Services

Client, and J2EE Client

򐂰 SOAP/HTTP(S), SOAP/JMS,

WSDL 1.1

򐂰 Supports WS-I Basic Profile 1.0

Chapter 2. Product selection 39

Adapter support (JCA and WBI adapters 򐂰 WBI adapters

򐂰 WebLogic JMS

򐂰 Biztalk

򐂰 TIBCO Rendezvous

򐂰 MQe

򐂰 Multicast

򐂰 Tuxe do

򐂰 FTP

򐂰 TIBCO EMS JMS

򐂰 COBOL Copybook

򐂰 HIPAA

򐂰 EDI-FACT

򐂰 ACORD

򐂰 Real-time IP

򐂰 SonicMQ JMS

򐂰 SWIFT

򐂰 FIX

򐂰 ebXML

򐂰 EDI-X.12

򐂰 MQTT

򐂰 AL3

򐂰 Word/Excel/PDF

򐂰 Custom Formats

򐂰 HL7

Message logging 򐂰 Provides prebuilt mediations for

message logging

򐂰 Supports message logging

Message transformation 򐂰 Protocol transformation between

HTTP, JMS, and IIOP

򐂰 Supports transformation of XML,

SOAP JMS message data format

(many more if used with

adapters)

򐂰 Provides prebuilt mediations for

XML transformation

򐂰 Protocol transformation between

HTTP and JMS

򐂰 Custom transformation logic can

be implemented in Java, ESQL,

or XSLT

򐂰 Supports transformation between

any protocols available as input

our output nodes (see Table 7-1

on page 218)

Message routing 򐂰 Content and

transport/protocol-based routing

򐂰 Supports through custom-built

mediations using Java and the

IBM SOA programming model

(SCA and SDO)

򐂰 Provides prebuilt mediations for

message routing

򐂰 Content and transport/protocol

based routing

򐂰 Custom routing logic can be

implemented in Java or ESQL

WebSphere ESB WebSphere Message Broker