About the tutorial
This tutorial is intended to demonstrate asynchronous
and synchronous event transmission for both the request and event
processing facets of the Adapter for Web Services with each of the
supported protocols: SOAP/HTTP, SOAP/HTTPS and SOAP/JMS. In each
scenario, the adapters act as:
- a web service client for collaborations that invoke a web service
- a proxy that exposes a WebSphere InterChange Server collaboration
as a web service
The tutorial is designed to show the basic functionality of the
adapter in sample scenarios:
- An asynchronous scenario that illustrates
an asynchronous (request-only) web service and its client with the
connector. There are two samples in this scenario--for configuration
simplicity, the same Web Services connector is used to expose a collaboration
as a Web Service and invoke a Web Service as a client.
- A collaboration that is exposed as a web service In
this sample, the web service is simply a collaboration SERVICE_ASYNCH_Order_Collab within WebSphere InterChange Server that is being exposed
as a web service by the connector. The web service is referred to
as Asynch Order Service. If the connector is properly configured,
this Web Service can be invoked using any (one) of the Web Services
protocols: SOAP/HTTP, SOAP/HTTPS or SOAP/JMS. 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 the Web Services connector. The service port (To) is bound to
SampleSiebelConnector.
- A collaboration that is invoked by a web services client In
this sample, the web service client is another collaboration CLIENT_ASYNCH_Order_Collab within WebSphere InterChange Server that will invoke the
Web Service Asynch Order Service using the Web Services connector.
If the connector is configured properly, this web service client
can invoke the Web Service over any (one) of the Web Services protocols:
SOAP/HTTP, SOAP/HTTPS or SOAP/JMS. 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 the Web
Services connector.
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) web service and its client with
the connector. There are two samples in this scenario--for
configuration simplicity, the same Web Services connector is used
to expose a collaboration as a Web Service and invoke a Web Service
as a client.
- A collaboration that is exposed as a web service In this sample,
the Web Service is simply a collaboration SERVICE_SYNCH_OrderStatus_Collab within WebSphere InterChange Server that is being exposed
as a web service by the connector. In this sample, this web service
is referred to as Synch OrderStatus Service. If the connector is
properly configured, the web service can be invoked using any of
the web services protocols: SOAP/HTTP, SOAP/HTTPS or SOAP/JMS. 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 the Web Services connector. The service port (To) is bound to
SampleSiebelConnector.
- A collaboration that is invoked by a web services client In
this sample, the web service client is another collaboration CLIENT_SYNCH_OrderStatus_Collab within WebSphere InterChange Server that will invoke the
web service Synch OrderStatus Service using the Web Services connector.
If the connector is properly configured, this web service client
can invoke the web service over any of the web services protocols:
SOAP/HTTP, SOAP/HTTPS or SOAP/JMS. 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 the Web
Services connector.
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.
