WebSphere Business Integration Pub/Sub Solutions
An IBM Redbooks publication
Note: This is publication is now archived. For reference only.
Published 14 May 2004
IBM Form #: SG24-6088-00
Authors: Saida Davies, Suresh Amujuri, Rudyanto Linggar, Kishore Muthyala, Ramesh Surisetty, Ewan Withers
This IBM Redbooks publication provides both technical background and implementation best practise recommendations for WebSphere Business Integration Pub/Sub solutions, with emphasis on the use of JMS API. It shows the differences between tuning for performance (high message rate) and robustness (high availability), and how to balance these to provide the correct solution for a set of business requirements.
The first part of this publication provides an overview of the technology behind the Pub/Sub messaging paradigm, leading to how best to use the WebSphere Business Integration product family to provide a Pub/Sub solution.
The second part introduces a sample set of applications and shows how to develop the Pub/Sub infrastructure to meet different sets of business requirements. The scenarios cover configurations involving multicast, cloned brokers, persistence and stream-crossing.
Table of contents
Part 1 Introduction
Chapter 1. Project overview
Chapter 2. Transport and messaging technologies
Chapter 3. The WebSphere Business Integration product family
Chapter 4. Choosing the right Pub/Sub solution
Chapter 5. Configuration and tuning of WBI Event Broker
Part 2 Rationale of WBI Event Broker
Chapter 6. Installation
Chapter 7. Configuration and administration of WBI Event Broker
Chapter 8. Overview of basic scenario
Chapter 9. Real-time transport for single broker performance
Chapter 10. Multicast transport for single broker performance
Chapter 11. Real-time transport for broker collective performance
Chapter 12. Persistent messages for single broker reliability
Chapter 13. Stream-crossing for single broker flexibility
Chapter 14. Cloned brokers for high availability
Chapter 15. Using multicast in a broker collective
Appendix A. Code used in the business case scenario
Others who read this publication also read
Follow IBM Redbooks
Follow IBM Redbooks