Running the asynchronous scenario

This scenario invokes the Asynch Order Service HTTP service. Before running the scenario, review this step-by-step synopsis of its data flow.

  1. A CLIENT_ASYNCH_TLO_Order.Create event originates in the application SampleSAP running in one instance of the Test Connector.
  2. The event is sent from SampleSAP to the collaboration CLIENT_ASYNCH_Order_Collab.
  3. The event is then sent from the collaboration to HTTPConnector.
  4. HTTPconnector then finds the XML_Order object that is a child of the CLIENT_ASYNCH_TLO_Order object.
  5. The Request business object is converted into an XML message using the XML data handler. HTTPconnector sends the XML message to the URL provided by the Destination attribute of the Protocol Config Meta-Object (MO). The Protocol Config MO used by the connector depends on the value of the Handler attribute of CLIENT_ASYNCH_TLO_Order. This value should be set to http or https.
  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 converts the XML message into XML_Order and then creates a SERVICE_ASYNCH_TLO_Order object. The XML_Order object is set as a child of the SERVICE__ASYNCH_TLO_Order object.
  8. HTTPConnector now asynchronously posts the SERVICE_TLO_Order object to ICS. This completes the asynchronous URL invocation.

Because this is an asynchronous invocation (request-only), no response is sent back to the HTTP client. When SERVICE_ASYNCH_Order_Collab receives this object, the collaboration then sends the business object to the application namedSampleSiebel, which is running as the second instance of Test Connector. The object is displayed in the Test Connector. When Reply Success is selected from theSampleSiebel application, the event will be sent back to SERVICE_ASYNCH_Order_Collab.

To run the asynchronous 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. 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\HTTP\samples\WebSphereICS\OrderStatus
    \CLIENT_ASYNCH_TLO_Order.bo
    

    The Test Connector should show that the CLIENT_ASYNCH_TLO_Order is loaded.

  7. Verify the HTTP URL 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 flow of the event.
  9. While simulating the SampleSiebelConnector with the Test Connector, select REQUEST->ACCEPT REQUEST. An Event Labeled SERVICE_ASYNCH_TLO_Order.Create is displayed in the right panel of the Test Connector.
  10. Double-click the business object. The business object opens up in a window.
  11. Expand the Request attribute of the business object. The Request attribute is of type SERVICE_ASYNCH_Order. Inspect the OrderId, CustomarId and other attributes of SERVICE_ASYNCH_Order to verify the Order received. This completes the execution of asynchronous scenario.
  12. Once you have inspected the business object, close the window. Select REQUEST ->REPLY-> SUCCESS.

Copyright IBM Corp. 1997, 2004