Index Changes

HTTP Binding Component Example Scenario

The following purchase order example illustrates a basic scenario of how an HTTP Binding Component can be used in a composite application to . In this example scenario a single HTTP Binding Component acts as both a service provider and service consumer.

Figure 1: HTTP Binding Component Acting as Service Provider and Service Consumer

Purchase Order Example

A medical supply company provides a web site that contains a line of products for pre-approved customers only. One of these customers, a clinic, logs onto the web site and orders 1000 surgical masks and 2000 pairs of latex gloves. The purchase order is received and stored by the medical supply company's server, and a response is sent back to the clinic to confirm that the order has been received.

The purchase order handling system in this scenario is represented by a web service implemented using Sun Java Application Server with the JBI framework. The actors in this situation are as follows:

  • The Web Client: Packages up the purchase order as a SOAP request and sends it to the server.
  • The HTTP Binding Component: Sends and receives HTTP and SOAP messages.
  • The BPEL Service Engine: Responsible for implementing the core business logic of fulfilling the purchase order.
  • The Normalized Message Router (NMR): Routes normalized messages between JBI components. In this scenario, it routes normalized messages to and from the HTTP BC and the BPEL SE.

Scenario Message Flow

The steps of the Purchase Order scenario message flow follow the numbers displayed in figure 1.

  1. The web client, using some client-side scripting language like JavaScript, takes the purchase order information entered into the web form and packages it into a SOAP message. The format of the SOAP message is defined using a WSDL.
  2. The SOAP message is sent to a web service endpoint hosted by the HTTP Binding Component.
  3. The HTTP Binding Component transforms the SOAP message into a normalized message. The normalized message is sent to the Normalized Message Router.
  4. The Normalized Message Router routes the normalized message to the BPEL SE.
  5. The BPEL SE interprets the purchase order information and properly invokes other BPEL processes to fulfill the request.
  6. The BPEL SE creates a response message in the form of a Normalized Message. The normalized message is sent to the Normalized Message Router.
  7. The HTTP BC receives the response message and converts it to a SOAP message. The SOAP message is sent back to the web client as a proper response as defined by the WSDL.
  8. The web client takes the response and creates a human-readable HTML page for the user to understand that the purchase order was accepted or rejected.

Previous Next

JSPWiki v2.4.100
« Home Index Changes Prefs
This page (revision-4) was last changed on 05-Nov-07 09:57 AM, -0800 by rjacobus