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

Service Component Architecture and WebSphere Enterprise Service Bus

Application integration infrastructure such as WebSphere Enterprise Service Bus is very powerful; however, powerful infrastructure does not usually imply easy to use. Developers may find themselves spending more time to learn or use an infrastructure rather than focus on developing business logic. To help companies reduce learning costs and to help developers pick up ESB development faster, IBM established Service Component Architecture (SCA).

Service Component Architecture is one way of implementing SOA architecture. It provides a technology-independent model that specifies interface, reference, and implementation. Such a model is known as a SCA component. The advantage of using SCA is that infrastructure logic is separated from business logic, which enables developers to focus on resolving the business side of technical issues. Currently, SCA components can be implemented in the following ways with WebSphere Integration Developer:

  • Java
  • BPEL
  • State Machine
  • Business Rule
  • Human Task
  • Selector
  • Mediation Flow

6 of 10 | Previous | Next


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