Running the synchronous scenario

This scenario invokes the Synch OrderStatus Service web service. Before running the scenario, review this step-by-step synopsis of its data flow.

  1. A CLIENT_SYNCH_TLO_OrderStatus.Retrieve event originates in the application SampleSAP running in one instance of the Test Connector.
  2. The event is sent from SampleSAP to the collaboration named CLIENT_SYNCH_OrderStatus_Collab.
  3. The event is then sent from the collaboration to the Web Services connector.
  4. The Web Services connector finds the CLIENT_SYNCH_OrderStatus_Request object, which is a child of the CLIENT_SYNCH_TLO_OrderStatus object.
  5. The Web Services connector invokes the SOAP data handler to convert the CLIENT_SYNCH_OrderStatus_Request business object into a SOAP message.
  6. The Web Services connector sends the SOAP message to the end-point (Destination) of the web service Synch OrderStatus Service. The end-point is provided by the Destination attribute of the Protocol Config MO. The Protocol Config MO used by the connector depends on the value of the Handler attribute of CLIENT_SYNCH_TLO_OrderStatus. If it is set to soap/http or soap/https, the Destination attribute of CLIENT_SYNCH_OrderStatus_Request_SOAP_HTTP_CfgMO will give the end-point as the URL of a web service. Otherwise, if the Handler attribute is set to soap/jms, the Destination attribute of CLIENT_SYNCH_OrderStatus_Request_SOAP_JMS_CfgMO will give the end-point as the destination queue name of the web service).
  7. The Web Service Synch OrderStatus Service receives the SOAP request. As mentioned earlier, the Web Services connector is the target end-point. The connector's protocol listener, listening on the end-point (to which request was sent), receive the SOAP message.
  8. The connector invokes the SOAP data handler with the SOAP message. The SOAP message is converted into a SERVICE_SYNCH_OrderStatus_Request object by the SOAP data handler. The Web Services connector then creates a SERVICE_TLO_OrderStatus object. The SERVICE_SYNCH_OrderStatus_Request object is set as the child of the SERVICE_TLO_OrderStatus object.
  9. The Web Services connector now synchronously posts the SERVICE_TLO_OrderStatus object to the SERVICE_SYNCH_OrderStatus_Collab collaboration running in WebSphere ICS. Since this is a synchronous execution, the Web Services connector remains blocked until the collaboration executes and returns the response.
  10. SERVICE_SYNCH_OrderStatus_Collab receives the SERVICE_TLO_OrderStatus object. The collaboration then sends the business object to the application SampleSiebel, which is running as the second instance of the Test Connector.
  11. When you select Reply Success from the SampleSiebel application, the event is sent back to the SERVICE_SYNCH_OrderStatus_Collab collaboration.
  12. SERVICE_SYNCH_OrderStatus_Collab receives the SERVICE_TLO_OrderStatus object. The collaboration then sends the business object to Web Services connector.
  13. The Web Services connector finds the SERVICE_SYNCH_OrderStatus_Response business object (or SERVICE_SYNCH_OrderStatus_Fault, if it is populated) that is a child of the SERVICE_SYNCH_OrderStatus_TLO. This business object will be converted into a SOAP response message (or SOAP fault message) by the SOAP data handler.
  14. The Web Services connector returns the SOAP response message (or SOAP fault message) to the web service client.
  15. The web service client, which in this case is the connector, receives the response. The connector invokes the SOAP data handler with the response message.
  16. The SOAP data handler converts the response message into either a CLIENT_SYNCH_OrderStatus_Response or CLIENT_SYNCH_OrderStatus_Fault business object, depending on what was returned by the Order Synch Service. The Web Services connector sets this object as the child of CLIENT_SYNCH_OrderStatus_TLO. CLIENT_SYNCH_OrderStatus_TLO is returned to the CLIENT_SYNCH_OrderStatus_Collab collaboration.

17) CLIENT_SYNCH_OrderStatus_Collab then sends CLIENT_SYNCH_OrderStatus_TLO to the SampleSAP application, which is running as the first instance of the Test Connector. The Test Connector displays this object.

To run the synchronous scenario:

  1. Start your ICS integration broker, if it is not already running.
  2. Start the Web Services connector.
  3. Start two instances of the Test Connector.
  4. Using the Test Connector, define a profile for the SampleSAPConnector and the SampleSiebelConnector.
  5. Select FILE"CONNECT AGENT from each Test Connector menu to begin simulating agents.
  6. While simulating the SampleSAPConnector using the Test Connector, select EDIT"LOAD BO from the menu. Load the following file:
    WBI_folder\connectors\WebServices\samples\WebSphereICS\OrderStatus
     \CLIENT_SYNCH_TLO_OrderStatus.bo
     
    

    The Test Connector should show that the CLIENT_SYNCH_TLO_OrderStatus is loaded.

  7. Verify the web services end-point address:
  8. While simulating the SampleSAPConnector with the Test Connector, click on the loaded Test BO. Select REQUEST"SEND from the menu. See the step-by-step synopsis earlier in this section for more details regarding the data flow.
  9. An event labeled SERVICE_SYNCH_TLO_OrderStatus.Retrieve is displayed in the right panel of the Test Connector instance that is simulating SampleSiebelConnector. Double-click the business object to display it in a window.
  10. Expand the Request attribute of the business object. The Request attribute is of type SERVICE_SYNCH_OrderStatus_Request. Inspect the OrderId, attribute of SERVICE_ASYNCH_Order to verify that this is the order for which status is required.
  11. Select REQUEST"REPLY"SUCCESS.An event labeled SERVICE_SYNCH_TLO_OrderStatus.Retrieve is displayed in the right panel of the Test Connector that is simulating SampleSAPConnector.
  12. Double-click the SERVICE_SYNCH_TLO_OrderStatus.Retrieve business object, which is then displayed in a window.
  13. Once you have inspected the business object, close the window. Select REQUEST"REPLY"SUCCESS.

This completes the execution of synchronous scenario.

Copyright IBM Corp. 1997, 2003