Appendix C. Overview of XML adapter sample scenarios
Consider the situation in which a company wants to use
the WebSphere Business
Integration Adapter for XML to read XML documents from
and POST XML
documents to Web Servers. Below are two different sample
scenarios
designed to be simple and show the basic points of the
XML
Adapter's functionality.
- Installation of the XML sample scenario.
This fictitious scenario involves two integrations that represent
the two
directions of data exchange:
- The first integration starts with an "XML_REQUEST_Order" event
sent from
WebSphere MQ Integrator Broker to an WebSphere MQ queue.
The XML
Adapter accepts the event from the queue and invokes
the XML DataHandler
to convert the event to an XML Document. The XML document
is POSTed to
a Webserver. The Webserver will respond to the XML
Adapter with it's
own XML.
- In the second integration, the XML Adapter will poll a URL for
an XML
document. Once read, the XML Adapter will send the document
through
the XML DataHandler. The DataHandler will return a response
event that
will be sent to an WebSphere MQ queue for the WebSphere
MQ Integrator
Broker to read.
- Installation of the XML sample scenario with InterChange Server
Express connectivity.
This fictitious scenario involves two integrations that represent
the two directions
of data exchange:
- The first integration starts with an "XML_REQUEST_Order" object
sent
from the PortConnector to the XML Adapter via the "Port_To_XML"
collaboration object. The XML Adapter will invoke the
XML DataHandler
to convert the request business object to an XML Document.
The XML is
POSTed to a Webserver. The Webserver will respond to
the XML
Adapter, which converts the response XML to the response
business object sent back to InterChange Server Express.
- In the second integration, the XML Adapter will poll a URL for
an XML
document. Once read, the XML Adapter will send the document
through
the XML DataHandler to convert it to a response business
object that will be
sent to the InterChange Server Express.
Then, via one of two collaborations, "XML_To_Port_Customer" or "XML_To_Port_Manifest",
the events
will be sent to the Port Connector.
