About the Web Service Aggregation sample

This sample shows how to use a message flow to request a number of web services and amalgamate the replies from them.

Web services are common IT applications and typically use the SOAP protocol. HTTP is a common transport mechanism for web services.

This sample addresses the following functional requirements:

Aggregation - the fan-out of web service requests and the fan-in of responses
Transport - the web services are called by using HTTP, therefore web service requests and responses are converted to and from this protocol
Business - the target web services

This sample addresses the following non-functional requirements:

Monitoring - IBM Integration Bus must provide proof that it has processed a particular piece of business data

These requirements are implemented in a number of message flows that have the following behavior:

Message flow name	Description
WSAggregationFanOut.msgflow	Calls (fan-out) a number of web services SOAP requests through WebSphere MQ
WSAggregationMQtoSOAP.msgflow	Converts the WebSphere MQ SOAP messages to HTTP
WSAggregationTargetWS.msgflow	Runs the web services and produces responses
WSAggregationSOAPtoMQ.msgflow	Converts the HTTP responses to WebSphere MQ
WSAggregationFanIn.msgflow	Receives (fan-in) the replies from the web services and produces a consolidated SOAP reply
WSAggregationReadMonitordata.msgflow	Processes the messages that are produced by monitoring

SOAP nodes are used extensively in this sample. The original input to the sample is received through a SOAPInput node, and the final reply is sent through a SOAPReply node.

The fan-out of requests and fan-in of replies for called web services is implemented by using Aggregation nodes. By using WebSphere MQ, the fan-out is transactional.

Each web service that is called by the sample is called by using SOAPAsyncRequest and SOAPAsyncResponse nodes.

The target web services are implemented as message flows. Each flow receives the request by using a SOAPInput node, and replies by using a SOAPReply node.

The sample also has a message set that contains WSDL definitions. These definitions are reused from other web service samples in IBM Integration Bus.

For more information about what you must set up so that you can run the sample, see Setting up the Web Service Aggregation sample.

For more information about how to run the sample, see Running the Web Service Aggregation sample.

For more information about the key points of each message flow model, see Exploring the Web Service Aggregation sample.

For more information about the key points of monitoring, see Monitoring.

For suggestions about how you can extend the sample, see Extending the sample.

Back to sample home