Running the synchronous scenario

This scenario invokes the Synch OrderStatus Service HTTP 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 HTTP connector.
  4. The HTTP connector finds the XML_OrderStatus object, which is a request child of the CLIENT_SYNCH_TLO_OrderStatus object.
  5. The HTTP connector invokes the XML data handler to convert the XML_OrderStatus business object into an XML message.
  6. The XML Request is POSTed to the URL. As mentioned earlier, the same HTTPConnector is listening for the XML request on the same URL. The connector's protocol listener receives the XML message.
  7. The connector's protocol listener converts the XML message into XML_OrderStatus and then creates a SERVICE_SYNCH_TLO_Order object. The XML_OrderStatus object is set as a child of the SERVICE_SYNCH_TLO_Order object.
  8. The HTTP connector now synchronously posts the SERVICE_SYNCH_TLO_OrderStatus object to the SERVICE_SYNCH_OrderStatus_Collab collaboration running in WebSphere ICS. Since this is a synchronous execution, the HTTP connector remains blocked until the collaboration executes and returns the response.
  9. The HTTP 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 HTTP connector remains blocked until the collaboration executes and returns the response.
  10. After editing the values, and selecting Reply Success from the SampleSiebel application, the event is sent back to the SERVICE_SYNCH_OrderStatus_Collab collaboration.
  11. SERVICE_SYNCH_OrderStatus_Collab receives the SERVICE_SYNCH_TLO_OrderStatus object. The collaboration then sends the business object to HTTPConnector.
  12. HTTPConnector finds the XML_OrderStatus business object that is a child of the SERVICE_SYNCH_OrderStatus_TLO. This business object is converted into an XML response message by the XML data handler.
  13. The XML response is sent back to the HTTP Client.
  14. The HTTP client, which in this case is the HTTP connector's protocol handler, receives the response. The connector invokes the XML data handler with the response message. The XML data handler converts the response message into an XML_OrderStatus business object. HTTPConnector sets this object as the child of CLIENT_SYNCH_OrderStatus_TLO.
  15. CLIENT_SYNCH_OrderStatus_TLO is returned to the CLIENT_SYNCH_OrderStatus_Collab collaboration.
  16. 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 HTTP connector.
  3. Start two instances of the Test Connector.
  4. Using the Test Connector, define a profile for the SampleSAPConnector and the SampleSiebelConnector.
  5. You must save the connector definition to a file to emulate a connector using Test Connector. Do the following to save a connector definition to a file:
    1. Open the connector definition in Connector Configurator.
    2. Select File > Save As > To File from the menu bar.
    3. Navigate to the directory in which you want the file saved, type a name in the File name field, ensure that the value Configuration (*.cfg) is displayed in the Save as type drop-down menu, and click Save.
  6. Select FILE->CONNECT AGENT from each Test Connector menu to begin simulating agents.
  7. While simulating the SampleSAPConnector using the Test Connector, select EDIT->LOAD BO from the menu. Load the following file:
    WBI_folder\connectors\HTTP\samples\WebSphereICS\CLIENT_SYNCH_TLO_OrderStatus.bo
    The Test Connector should show that the CLIENT_SYNCH_TLO_OrderStatus is loaded.
  8. Verify the HTTP URL address:
  9. 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.
  10. 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.
  11. Expand the Request attribute of the business object. Inspect the values of the request to ensure that the values sent across from the SampleSAPConnector are intact.
  12. In the same window opened in step 10 above, populate the response attribute of this business object by selecting LOAD BO. Load the following file: The Test Connector should show that the SERVICE_SYNCH_TLO_OrderStatus is loaded.
  13. Select REQUEST->REPLY->SUCCESS.
  14. An event labeled CLIENT_SYNCH_TLO_OrderStatus.Retrieve is displayed in the right panel of the Test Connector that is simulating SampleSAPConnector.
  15. Double-click the CLIENT_SYNCH_TLO_OrderStatus.Retrieve business object, which is then displayed in a window. If your SampleSiebelConnector returned an order status, you should see the Response attribute of the business object populated. Expand the Response attribute to verify the order status.
  16. Once you have inspected the business object, close the window. Select REQUEST->REPLY->SUCCESS.

This completes the execution of synchronous scenario.

Copyright IBM Corporation 2003, 2005. All Rights Reserved.