HTTP bindings for imports and exports

© Copyright IBM Corporation 2008. All rights reserved
What you should be able to do
At the end of this lab you should be able to:
• Create and configure HTTP import and export bindings in the WebSphere Integration Developer V6.1.
Understand how to set use the different data binding and the function selector options
• Run the application and navigate through the Administration console to see the HTTP binding
configurations. Use TCP/IP monitor view in WebSphere Integration Developer to view the HTTP traffic
between the client and the provider.
Introduction to the lab example
In this lab, you will import a skeleton of a service provider Stock Quote application and a Stock Quote
service client application, into the WebSphere Integration Developer workspace. You will then add HTTP
bindings so that the client can send request and receive response from the service provider using HTTP
application. The complete application looks like the one shown below abstractly.
You will then work through the different configuration options of the HTTP bindings.
The picture below depicts the structure of the application you work with in this lab:
The Stock quote client module, called SQuoteClient shown on the left side of the picture above, is a simple
SCA module that has a SCA POJO component being called from a JSP page through the stand-alone
reference. The SCA POJO is wired to a HTTP import, called SQuoteHTTP.
The HTTP request from the client contains the customer ID and the stock symbol.
The Stock Quote service provider module, called SQuote, shown on the right side of the picture above is a
simple SCA module receiving HTTP request through the HTTP export, called SQuoteHTTP. The service is
provided by a SCA POJO component, called SQuote. The SCA POJO implementation contains some hard
coded values to return as a response. It has been intentionally kept simple to keep the focus on the HTTP
bindings.
2008 August, 19 IBM WebSphere V 6.1 – Lab exercise Page 3 of 52
SCA HTTP binding