About the Multiple WebService Requests sample
This sample demonstrates how you can use an HTTPHeader node in a flow that has
multiple Web service requests.
The first HTTPHeader node is used to configure a SOAPAction for the
first request. The response to the first request is used as the input to the
second request. The second HTTPHeader node is used to reset the
SOAPAction header to send a new request to second Web service.
The following message flow is imported by the sample:
How the flow works:
- A request is sent to http://localhost:7080/getMiles.WS
- The flow receives the request on an HTTPInput node (GetMilesWS).
- The message is passed to an HTTPHeader node (AddSOAPAction)
to set the SOAPAction header value to http://localhost:7080/ConvertToMeters
in the HTTPRequest header.
- The modified message is passed to an HTTPRequest node (GetMeters), which calls the first
Web service flow to convert yards to meters.
- The first Web service flow receives the request on an HTTPInput node (ConvertToMetersWS).
- The request is passed to a JavaCompute node (ConvertToMeters), which converts yards to meters.
- An HTTPReply node (ReplyMetersResult) sends back the result.
- The output message from the first Web service is passed to an HTTPHeader node (ResetSOAPAction)
to reset the SOAPAction header value to
http://localhost:7080/ConvertToMiles in the HTTPRequest header.
- The message is then passed to an HTTPRequest node (GetMiles), which calls the
second Web service flow to convert meters to miles.
- The second Web service flow receives the request on an HTTPInput node (ConvertToMilesWS).
- The request is passed to a JavaCompute node (ConvertToMiles), which converts meters to miles.
- An HTTPReply node (ReplyMilesResult) sends back the result.
- The output from the second Web service is sent back to you by using an HTTPReply node (ReplyResult).
Back to Read about the HTTPHeader node sample
Back to sample home