This topic provides an overview of the
architecture for a Web service provider using IMS™ Enterprise Suite SOAP Gateway and created
through the bottom-up development scenario.
The following steps describe how a message is processed at runtime:
- The Web service client application sends a SOAP message to the IMS Enterprise Suite SOAP Gateway
containing input to the IMS application
in an XML format.
- The SOAP Gateway processes the SOAP header and retrieves the appropriate
correlation and connection information for the input request.
- The SOAP Gateway creates an IMS Connect
message, consisting of an IMS Connect
header followed by the input XML data, to IMS Connect
using TCP/IP.
- IMS Connect calls its XML
adapter, which in turn calls the XML converter to transform the XML
data to IMS application format.
- IMS Connect sends the message
for further processing. For the remainder of this step the processing
is the same as for a normal transaction flow. The transaction returns
its output and the output is queued to IMS Connect.
- IMS Connect calls the XML
adapter to transform the IMS application
data to XML format.
- IMS Connect sends the output
XML message back to the SOAP Gateway using TCP/IP.
- The SOAP Gateway wraps a SOAP header around the output message.
- The IMS Enterprise Suite
SOAP Gateway sends the SOAP output message back to the client application.
In this service provider architecture, IMS Message
Processing Programs (MPPs) s are not aware that they are being invoked
as Web services and therefore do not have access to the service invocation
context.