About the tutorial
This tutorial is intended to demonstrate the asynchronous
and synchronous event transmission for both the request and event
processing facets of the Adapter for HTTP with both of the supported
protocols: HTTP and HTTPS. In each scenario, the adapters act as:
- an HTTP client that invokes an external URL
- a proxy that listens for HTTP requests on a URL and routes them
to a WebSphere ICS collaboration.
The tutorial is designed to show the basic functionality of the
adapter in sample scenarios:
- An asynchronous scenario that illustrates
an asynchronous (request-only) HTTP POST. There are two samples
in this scenario--for configuration simplicity, the same
HTTP adapter is used to used to listen for HTTP requests and invoke
a URL as an HTTP client.
- A proxy that listens for HTTP requests on a URL In
this sample, the incoming request is routed to the collaboration SERVICE_ASYNCH_Order_Collab within WebSphere ICS. The collaboration is referred to as
Asynch Order. If the adapter is properly configured, this collaboration
can be invoked using either one of the protocols: HTTP or HTTPS. SERVICE_ASYNCH_Order_Collab is a simple pass-through collaboration that takes SERVICE_ASYNCH_TLO_Order. The triggering port (From) of this collaboration is bound
to HTTPConnector. The service port (To) is bound to SampleSiebelConnector.
- An HTTP client that invokes an external URL In
this sample, the HTTP client is another collaboration CLIENT_ASYNCH_Order_Collab within WebSphere ICS that will invoke an external URL asynchronously
using the HTTP adapter. If the adapter is configured properly, this
HTTP client can invoke the external URL over either one of the protocols:
HTTP or HTTPS. CLIENT_ASYNCH_Order_Collab is a simple pass-through collaboration which takes CLIENT_ASYNCH_TLO_Order. The triggering port (From) of this collaboration is bound
to SampleSAPConnector. The service port (To) is bound to HTTPConnector.
Both samples in the asynchronous scenario involve two applications:
- SampleSiebel: Creates an order for its clients.
- SampleSAP: Creates an order
- A synchronous scenario that illustrates
a synchronous (request-response) HTTP Post. There are two samples
in this scenario--for configuration simplicity, the same
HTTP adapter is used to listen for HTTP requests and invoke a URL
as an HTTP client.
- A proxy that listens for HTTP requests on a URL In
this sample, the incoming request is routed to the collaboration SERVICE_SYNCH_OrderStatus_Collab within WebSphere ICS. The collaboration is referred to as
Synch OrderStatus. If the adapter is properly configured, this collaboration
can be invoked using either one of the protocols: HTTP or HTTPS. SERVICE_SYNCH_OrderStatus_Collab is a simple pass-through collaboration which takes SERVICE_SYNCH_TLO_OrderStatus. The triggering port (From) of this collaboration is bound
to HTTPConnector. The service port (To) is bound to SampleSiebelConnector.
- An HTTP client that invokes an external URL In
this sample, the HTTP client is another collaboration CLIENT_SYNCH_OrderStatus_Collab within WebSphere ICS that will invoke an external URL using
the HTTP adapter. If the adapter is properly configured, this HTTP
client can invoke the external URL over either one of the protocols:
HTTP or HTTPS. CLIENT_SYNCH_OrderStatus_Collab is a simple pass-through collaboration which takes CLIENT_SYNCH_TLO_OrderStatus. The triggering port (From) of this collaboration is bound
to SampleSAPConnector. The service port (To) is bound to HTTPConnector.
Both samples in the synchronous scenario involve two applications:
- SampleSiebel: Retrieves the status of orders for its clients.
- SampleSAP: Requests the status of the order
Both scenarios involve simulating the SampleSiebelConnector and SampleSAPConnector
using two Test Connectors.
