Aggregation nodes using SOAPAsyncRequest nodes with back-end services


Learn how to use the Aggregation nodes to fan-out and fan-in messages using asynchronous SOAP nodes.
OVERVIEW

This tutorial demonstrates a simple Integration Service that receives a SOAP/HTTP message, and fans-out two separate asynchronous SOAP/HTTP request messages (after simple transformations using a Mapping node). Two separate example back-end Integration Services are provided which receive these requests, do a trivial transformation to upper-case the data, and reply. The fan-in part of the Integration Service aggregates values from the two response messages together.

This tutorial requires an IIB node which is associated with a local queue manager.

In IBM Integration Bus, an application is a container for all the resources that are required to create a solution. An Integration Service is a specialized form of an application with a defined interface and structure that acts as a container for a web services solution. This tutorial provides an Integration Service which holds the fan-out / fan-in aggregation flow, and two other back-end Integration Services. A shared library is used to hold the associated WSDL and XSD files describing the back-end services which is required by the main Integration Service.

This tutorial takes approximately 5 minutes.
Tutorial Topics
  • Aggregation nodes
  • Asynchronous SOAP/HTTP
Learning outcomes
  • Use IBM Integration Bus to fan-out requests over SOAP/HTTP and aggregate their responses.