Skip to main content

Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server

An IBM Redbooks publication

Note: This is publication is now archived. For reference only.


Published on 15 January 2008

  1. .PDF (5.9 MB)

Share this page:   

ISBN-10: 0738485543
ISBN-13: 9780738485546
IBM Form #: SG24-7527-00

Authors: Carla Sadtler, John Adegbile, Erik Kirk, Joao Lopes, Rosaline Makar and Raghunath Nair

    menu icon


    IBM® WebSphere® Process Server is a business integration server that was built to support solutions that are based on the service-oriented architecture (SOA). It plays a key role in the architecture of the IBM SOA Foundation by providing functionality for process services. Another key component of the architecture is the enterprise service bus (ESB). IBM provides three key ESB products: IBM WebSphere Enterprise Service Bus, WebSphere Message Broker, and the WebSphere DataPower Integration Appliance XI50.

    This IBM Redbooks® publication has been written for architects who are planning an SOA solution and application designers who are implementing an SOA solution with WebSphere Process Server and WebSphere Message Broker. In this book, we highlight the ESB capabilities of WebSphere Message Broker and explain how you can leverage them with WebSphere Process Server. In addition, we discuss interoperability and provide examples to illustrate the integration of the two products.

    Table of Contents

    Part 1. WebSphere Message Broker as an ESB

    Chapter 1. The IBM SOA Foundation and products in this book

    Chapter 2. Business processes with WebSphere Process Server

    Chapter 3. Mediation with WebSphere Message Broker

    Chapter 4. Connectivity options for interoperability

    Part 2. Scenarios

    Chapter 5. Scenario: Message splitting and routing

    Chapter 6. Scenario: WebSphere Message Broker acting as a transaction manager

    Chapter 7. Scenario: Data transformation and security

    Chapter 8. Scenario: Aggregation

    Chapter 9. Scenario: Asynchronous callback

    Chapter 10. Scenario: Connectivity to third-party JMS providers


    Others who read this also read