SOAP Gateway and asynchronous callout requests

IMS Enterprise Suite SOAP Gateway includes support for the asynchronous callout function, which enables IMS application programs to make asynchronous callout requests to web services through the SOAP Gateway.

When enabled for asynchronous callout requests, the SOAP Gateway listens for new callout requests by continuously issuing the RESUME TPIPE call to IMS Connect. If a callout request message is on the tpipe queue, OTMA sends the callout request to IMS Connect, IMS Connect processes the message, converting the message to XML if necessary, and then sends the message to the SOAP Gateway.

If you are using the SOAP Gateway with a z/OS® Sysplex Distributor that distributes input to IMS through multiple instances of IMS Connect, the callout requests must be made using a TMEMBER for which the OTMA super member function is enabled.

If the callout request message requires conversion to XML, XML conversion support must be enabled in IMS Connect and the callout request message must specify the XML adapter and the converter in its OTMA header of the callout request message. If the callout request message does not specify an XML adapter and a converter, IMS Connect does not convert the message to XML.

D DESCNAME TYPE=IMSCON TMEMBER=HWS1 TPIPE=PIPENAME
D DESCNAME ADAPTER=HWSXMLA0 CONVRTR=CNVNAMED

In the example, if an IMS application program inserts a message to the ALT IOPCB using the descriptor name DESCNAME, OTMA adds the adapter and converter names to the OTMA header of the callout request message and then queues the message to the tpipe PIPENAME.

IMS Connect support for XML conversion with the asynchronous callout function requires a callout XML converter for each web service that you want your IMS application program to call. Generate the callout XML converters by using Rational® Developer for System z® Version 7.1.1 or later.

For more information about the SOAP Gateway, see the SOAP Gateway documentation in the IBM® Documentation.