This scenario invokes the Synch OrderStatus Service web 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 Web
Services connector.
- The Web Services connector finds the
CLIENT_SYNCH_OrderStatus_Request object, which is a child
of the CLIENT_SYNCH_TLO_OrderStatus object.
- The Web Services connector invokes the SOAP data handler to
convert the CLIENT_SYNCH_OrderStatus_Request business
object into a SOAP message.
- 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).
- 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.
- 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.
- 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.
- 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.
- When you select 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_TLO_OrderStatus object. The collaboration then
sends the business object to Web Services connector.
- 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.
- The Web Services connector returns the SOAP response message
(or SOAP fault message) to the web service client.
- 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.
- 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:
- Start your ICS integration broker, if it is not already
running.
- Start the Web Services 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\WebServices\samples\WebSphereICS\OrderStatus
\CLIENT_SYNCH_TLO_OrderStatus.bo
The Test Connector should show that the
CLIENT_SYNCH_TLO_OrderStatus is loaded.
- Verify the web services end-point address:
- For SOAP/HTTP web service If you want to use SOAP/HTTP:
- Make sure you have configured the Web Services connector for
SOAP/HTTP. In your Test Connector, make sure that the value of the
Handler attribute for the CLIENT_SYNCH_TLO_OrderStatus
business object is set to soap/http. No quotes are allowed
in this value.
- Expand the Request attribute of
CLIENT_SYNCH_TLO_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus business object.
- Expand SOAPHTTPCfgMO attribute of
CLIENT_SYNCH_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus_SOAP_HTTP_CfgMO.
- Make sure the value of the Destination attribute of
CLIENT_SYNCH_OrderStatus_SOAP_HTTP_CfgMO is set to
http://localhost:8080/wbia/webservices/samples. No quotes
are allowed in this value.
- For SOAP/HTTPS web service If you want to use
SOAP/HTTPS:
- Make sure that you have configured the Web Services connector
for SOAP/HTTPS. In your Test Connector, make sure that the value of
the Handler attribute for the CLIENT_SYNCH_TLO_OrderStatus
business object is set to soap/https. No quotes are
allowed in this value.
- Expand the Request attribute of
CLIENT_SYNCH_TLO_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus business object.
- Expand the SOAPHTTPCfgMO attribute of
CLIENT_SYNCH_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus_SOAP_HTTP_CfgMO.
- Make sure value of Destination attribute of
CLIENT_SYNCH_OrderStatus_SOAP_HTTP_CfgMO is set to
https://localhost:8443/wbia/webservices/samples. No quotes
are allowed in this value.
- For SOAP/JMS web service If you want to use SOAP/JMS:
- Make sure you have configured the Web Services connector for
SOAP/JMS. In your Test Connector, make sure that the value of the
Handler attribute of the CLIENT_SYNCH_TLO_OrderStatus
business object is set to soap/jms. No quotes are allowed
in this value.
- Expand the Request attribute of
CLIENT_SYNCH_TLO_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus business object.
- Expand the SOAPJMSCfgMO attribute of
CLIENT_SYNCH_OrderStatus. This attribute is of type
CLIENT_SYNCH_OrderStatus_SOAP_JMS_CfgMO.
- Make sure the value of the Destination attribute of
CLIENT_SYNCH_OrderStatus_SOAP_JMS_CfgMO is set to
ORDER_INPUT. No quotes are allowed in this value.
- 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. 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.
- If you know the status of the order:
- Click the Response attribute of
SERVICE_SYNCH_TLO_OrderStatus. The Response attribute is
of type CLIENT_SYNCH_OrderStatus_Response.
- Right-click the Response attribute.
- Click the Add Instance option. A new instance for the
CLIENT_SYNCH_OrderStatus_Response business object is
created.
- Enter values for OrderId, CustomerId and all
other details you know about this order. Once you have entered all
the details for this order, close this window.
- If you do not know the status of the order:
- Click the Fault attribute of
SERVICE_SYNCH_TLO_OrderStatus. The Fault attribute is of
type CLIENT_SYNCH_OrderStatus_Fault.
- Right-click the Fault attribute.
- Click the Add Instance option. A new instance of
CLIENT_SYNCH_OrderStatus_Fault is created.
- Enter values for faultcode, faultstring and all other details
you want to send in the SOAP fault message. Once you have entered
all the values for this fault, close this window.
- 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.
- If your SampleSiebelConnector returned a fault, you
should see the Fault attribute of the business object populated.
Expand the Fault attribute to determine the fault.
- Once you have inspected the business object, close the window.
Select REQUEST"REPLY"SUCCESS.
This completes the execution of synchronous scenario.
