The SOAP consumer use case is based on a sales processing scenario. At the time of a sale, the customer’s name, the code for the product, a description of the product, its category, the unit price, and quantity purchased are recorded. Each customer might purchase several items. At the end of each day, the sales of each store are consolidated in a single list¬†that is sent to the company’s billing system. The billing system responds with any currency updates that should be applied per purchase order.
The SOAP consumer application receives a SOAP over HTTP request message, makes a synchronous call to an external service provider, and delivers a reply message. For the applications to successfully communicate, the message formats must be transformed for both the request and reply messages.
The messages used for input and output are self-defining XML messages.¬† Each message consists of three parts:
- A header, which contains a count of the number of repetitions of the repeating SaleList structure that follows.
- The body, which contains the repetitions of the repeating SaleList structure.
- The trailer, which contains the time the message was processed.
The transformation and calling to an the billing system (external service provider) is achieved with a single message flow.
Results per platform
Results for the SOAP consumer use case can be found for each platform here:
SOAP Consumer Message Flow
The message flow performs the following processing:
- Receives a SOAP over HTTP message.
- Transforms a message by using a message map prior to calling the external service provider.
- Calls synchronously an external service provider.
- Transforms the response from the service provider.
- Sends a SOAP message as a response to the initial call.