BEA AquaLogic Service Bus and WebSphere MQ in Service-Oriented Architectures

by Irene Rusman
11/15/2006

Service-Oriented Architecture (SOA) has become a widely accepted paradigm in the industry. The increased demand for asynchronous exchange of business data has driven the need for SOAs. Different messaging middleware employed by enterprises means that BEA needs to provide a way to integrate this middleware with the BEA family of products. In particular, customers should be able to use the integrated BEA AquaLogic Service Bus/WebSphere MQ system to provide support for messaging interoperability, load balancing, high availability, high performance, failover, and exactly-once quality-of-messaging service (with regard to 'request message').

This paper discusses the setup and configuration of clustered BEA AquaLogic Service Bus 2.1 and WebSphere MQ (version 5.3 and higher) with Extended Transactional Client. It focuses on distributed transactional request/response messaging communication between these products. The example provided allows customers to achieve load balancing and failover in a clustered BEA AquaLogic Service Bus domain, as well as load balancing in an IBM WebSphere MQ cluster.

Download

Download the white paper (PDF).

Resources

• Dev2Dev's AquaLogic Service Bus product center.
• Visit Arch2Arch for related articles.

Irene Rusman is a Senior Software Engineer with BEA. She works on AquaLogic Service Bus system integration.

Return to dev2dev.