Setting up the Web Service Aggregation sample

HTTP port setup

The execution group that hosts the message flows for the Web Service Aggregation sample is configured to use port number 7800 for SOAP and HTTP transport. If your execution group uses a different port, you must amend the Call backend web service - 1 and Call backend web service - 2 nodes in the WSAggregationMQtoSOAP message flow, and specify the different port value in the Web service URL field.

Publish/subscribe setup

This sample uses WebSphere MQ Explorer to define publish/subscribe objects. For further information, see Monitoring the Web Service Aggregation sample.

Message flow monitoring setup

This sample can use WebSphere Message Broker monitoring. For further information about how to enable monitoring, see Monitoring the Web Service Aggregation sample.

File nodes setup

The WSAggregationReadmonitor.msgflow message flow produces files by using FileOutput nodes. These files contain flow monitoring information.

On the operating system that is being used, you must set an environment variable to specify the root directory that is used by the FileOutput nodes.

  1. Follow the instructions at Setting up a command environment to create a command environment and a command file that contains the following line (ensuring that there is no white space around the equal (=) sign):
  2. Stop and restart your broker. See Starting and stopping a broker.

Monitoring

For details about how to set up flow monitoring, see Monitoring the Web Service Aggregation sample.

Back to About the Web Service Aggregation sample

Back to Running the sample

Back to sample home