This scenario invokes the Synch OrderStatus Service HTTP service.
Before running the scenario, review this step-by-step synopsis of its data
flow.
- A CLIENT_SYNCH_TLO_OrderStatus.Retrieve event originates
in the application SampleSAP running in one instance of the Test
Connector.
- The event is sent from SampleSAP to the collaboration named
CLIENT_SYNCH_OrderStatus_Collab.
- The event is then sent from the collaboration to the HTTP
connector.
- The HTTP connector finds the XML_OrderStatus object, which is a
request child of the CLIENT_SYNCH_TLO_OrderStatus object.
- The HTTP connector invokes the XML data handler to convert the
XML_OrderStatus business object into an XML message.
- 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.
- 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.
- 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.
- 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.
- After editing the values, and selecting Reply Success from the
SampleSiebel application, the event is sent back to the
SERVICE_SYNCH_OrderStatus_Collab collaboration.
- SERVICE_SYNCH_OrderStatus_Collab receives the
SERVICE_SYNCH_TLO_OrderStatus object. The collaboration then
sends the business object to HTTPConnector.
- 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.
- The XML response is sent back to the HTTP Client.
- 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.
- CLIENT_SYNCH_OrderStatus_TLO is returned to the
CLIENT_SYNCH_OrderStatus_Collab collaboration.
- 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:
- Start your ICS integration broker, if it is not already running.
- Start the HTTP connector.
- Start two instances of the Test Connector.
- Using the Test Connector, define a profile for the
SampleSAPConnector and the SampleSiebelConnector.
- Select FILE->CONNECT AGENT from each Test Connector menu to
begin simulating agents.
- 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_SYNCH_TLO_OrderStatus.bo
The Test Connector should show that the
CLIENT_SYNCH_TLO_OrderStatus is loaded.
- Verify the HTTP URL address:
- To run the HTTP sample:
- In your Test connector, make sure that the value of the Handler attribute
for the CLIENT_SYNCH_TLO_OrderStatus business object is set to
http.
- Expand the request attribute of
CLIENT_SYNCH_TLO_OrderStatus. This attribute is of type
XML_OrderStatus business object.
- Expand the HTTPCfgMO attribute of XML_OrderStatus. This
attribute is of type XML_Order_HTTP_CfgMO.
- Make sure the value of the Destination attribute of
XML_Order_HTTP_CfgMO is set to
http://localhost:8080/wbia/http/samples.
- To run the HTTPS sample:
- In your Test Connector, make sure that the value of the Handler attribute
for the CLIENT_SYNCH_TLO_OrderStatus business object is set to http
even though this is an https invocation.
- Expand the Request attribute of
CLIENT_SYNCH_TLO_OrderStatus. This attribute is of type
XML_OrderStatus business object
- Expand the HTTPCfgMO attribute of XML_OrderStatus. This
attribute is of type XML_Order_HTTP_CfgMO.
- Make sure the value of the Destination attribute of
XML_Order_HTTP_CfgMO is set to
https://localhost:443/wbia/http/samples.
- 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.
- 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.
- Expand the Request attribute of the business object. Inspect the
values of the request to ensure that that the values sent across from the
SampleSAPConnector are intact.
- Populate the response attribute of this business object by selecting
LOAD BO. Load the following file:
- WBI_folder\connectors\HTTP\samples\WebSphereICS\
SERVICE_SYNCH_TLO_OrderStatus.bo
The Test Connector should show that the SERVICE_SYNCH_TLO_OrderStatus is
loaded.
- 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.
- Double-click the
SERVICE_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.
- Once you have inspected the business object, close the window.
Select REQUEST->REPLY->SUCCESS.
This completes the execution of synchronous scenario.
