The Web Service Aggregation sample includes an example of an input test message and a corresponding expected output message, so that you can confirm that the sample has worked.
The sample is designed to fan out to two web services by using two AggregateRequest nodes. For simplicity, the sample has one target web service, so that both objects in the fan out target the same web service.
The target web service is a message flow in the sample.
Input to this sample is a SOAP message; the entire sample is a web service. The SOAP message is found in the SampleInputMessage1.xml file in the WebServiceAggregationMFP Integration project.
You can vary the number of web services that are called. In the message data field <Quantity> determines how many pairs of web services are run.
A second test message is provided with this sample in the SampleInputMessage2.xml file. For this message, the <PartNumber> field is set to ABC1235 and the <Quantity> field is set to 2. The message results in different values for the overall response message.
The web service that comprises this sample uses five message flows:
These message flows are described in more detail in Exploring the Web Service Aggregation sample.
If all the steps are successful, the sample is complete.
To look at the message flows and message set project in more detail, see Exploring the Web Service Aggregation sample.
The following message is the expected output XML message for the SampleInputMessage1.xml input message:
The <AMT> field is a cumulative total of the number of web services called since the broker was restarted, or since the last deployment. Therefore, if you use the sample more than once, the value of this field increases in any subsequent iterations.
The following message is the expected output XML message for the SampleInputMessage2.xml input message:
If you encounter any problems when you run the sample, see Resolving problems when running samples in the IBM Integration Bus information center.
For details about how to set up flow monitoring in this sample, see Monitoring the Web Service Aggregation sample.