Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Hello World: WebSphere Enterprise Service Bus

Develop message flow for protocol transformation

Abelard Chow (, Advisory Software Developer, IBM
Abelard Chow
Abelard Chow is an Advisory Software Engineer with the IBM Scenario Analysis Lab, where he works on improving the cross-brand integration capability of IBM Software Group products. In the last few years, he served IBM customers as a Solution Architect in IBM Financial Industry Solution.
Bill Zhu (, Software Developer, IBM
Bill Zhu is a software developer in the Scenario Analysis Lab team at the IBM Toronto Lab. His areas of expertise include solution design and implementation, e-commerce software, and messaging systems.

Summary:  Learn how to build message flow for protocol transformation. This tutorial demonstrates protocol transformation characteristics of WebSphere® Enterprise Service Bus. This is the fifth tutorial in the "Hello, World" series, which provides high-level overviews of various IBM® software products. WebSphere Enterprise Service Bus is designed to meet the connectivity and integration needs of Web Services applications and data. Customers who are interested improving their competitive edge with business transformation should consider an Enterprise Service Bus solution leveraging one of IBM's ESB products, such as WebSphere Enterprise Service Bus.

View more content in this series

Date:  07 Nov 2006
Level:  Intermediate PDF:  A4 and Letter (1193 KB | 27 pages)Get Adobe® Reader®

Activity:  45830 views

What is Enterprise Service Bus?

The concept of Enterprise Service Bus was first introduced in 2002. Since then, it has been widely adapted in the software industry. Enterprise Service Bus provides an integration platform that combines Message Oriented Middleware (MOM) integration strategy, Web Services, Message Transformation, and Intelligence Message Routing into an event-driven Service Oriented Architecture (SOA).

Message Oriented Middleware

Message Oriented Middleware allows applications running on different servers to connect in a loosely coupled, asynchronous fashion through messages communication. It is a flexible approach to architect distributed systems.

Web Services

It is widely acknowledged that Web Services is the cornerstone of Service Oriented Architecture. Web Services provides an architecture and standard for the industry to implement applications as reusable services. These reusable services are accessible by any potential service requester.

Message Transformation

The ability of data mapping and data transformation is essential in any application integration strategy. An Enterprise Service Bus must be able to transform the message sent from a service requester into a format receivable by the service provider, and vice versa.

Intelligence Message Routing

Message Routing, an essential ability in Enterprise Service Bus, allows service requesters truly decoupled from the service providers. Messages sent from a service requester may be routed to one or more service providers based on the routing logic.

Enterprise Service Bus is an SOA application integration architecture; however, how does it differ from conventional integration approaches? The following diagram illustrates how conventional integration approaches compare to Enterprise Service Bus:

Figure 2. Conventional integration approaches vs. ESB
Conventional integration approaches vs. ESB

Conventionally, applications can be integrated in certain ways: Peer-to-peer integration, Hub and Adaptor integration and Message-based integration. Peer-to-peer integration resulted from an ad hoc approach. It is infamous for non-scaling and difficult to maintain. The Hub and Adaptor integration approach connects applications to hubs using various adaptors. It is more maintainable than Peer-to-peer, but is not a good solution for distributed systems. In Message-based integration, applications are loosely coupled through message exchange. This approach makes a system more distributable; however, existing applications that do not support messaging require massive modification to be integrated.

Enterprise Service Bus combines the benefit of Hub and Adaptor integration and Message-based integration to provide maximum maintainability and distributing ability.

3 of 10 | Previous | Next


Zone=Business process management, WebSphere, SOA and web services
TutorialTitle=Hello World: WebSphere Enterprise Service Bus