IBM Professional Papers

• Japanese

Designing Messaging Infrastructure for Asynchronous Web Services
- High Availability and Scalability for WAS-MB Integration Using SOAP/JMS -

Asynchronous messaging using SOAP/JMS (Java Message Service) transport protocol is an effective approach that enables Web services to transmit messages without being affected by the status of the system being connected to. In this paper, we discuss the advantages of using Messaging Engines (MEs) in WebSphere® Application Server when WebSphere Message Broker is used for an Enterprise Service Bus. In addition, we describe how to design highly available and scalable messaging infrastructures using Messaging Engines.
Especially with regard to scalability, messaging workload should be properly balanced in MEs both on the Web services requester side and on the provider side. We present configuration tips and considerations together with our test results.

Words & Phrases：
SOAP/JMS, Messaging Engine, MDB, MQ Link, Web Services

1. Introduction
   
   
2. Transport Protocols for Web Services Integration
   
   
3. SOAP/JMS protocol Transportation Mechanism and Message Routing Implementation
   3.1  SOAP/JMS protocol Transportation Mechanism
   3.2  Message Routing Implementation
   
   
4. WAS-MB Connectting Patterns using SOAP/JMS protocol
   
   
5. Implementation of High Availability of WAS-MB configurations
   5.1  High Availability of WAS(ME)
   5.2  High Availability of MQ Link that provides ME-MQ connectivity
   
   
6. Implementation of ME Scalability
   6.1  Messaging Load Balancing
   6.2  ME Scalability using MDB
   
   
7. Epilogue

[ PROVISION | No.59 ]