IMS TM Resource Adapter and asynchronous callout requests

If you are using the asynchronous callout function with the IMS TM Resource Adapter, your WebSphere® Application Server administrator must configure a shareable connection factory to be used by the EJB bean or message-driven bean to retrieve the callout requests from IMS through IMS Connect.

The bean uses the IMS TM Resource Adapter to listen to the OTMA asynchronous hold queue by issuing a looping RESUME TPIPE call with a long timeout value. If no messages are on the queue when a RESUME TPIPE call is issued, the IMS TM Resource Adapter remains in a wait state. If the RESUME TPIPE call times out before a callout request arrives on the asynchronous hold queue, control is returned to the bean, which can then issue another RESUME TPIPE call to continue listening or break the loop to perform error checking.

Also, your Java™ application programmers must modify the bean to specify an alternate client ID that identifies the OTMA tpipe on which the callout request is queued.

Optionally, you can have your bean process the callout request itself, or you can have the bean pass the callout request on to a web service.

If you are using the IMS TM Resource Adapter 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.

For information about coding the IMS TM Resource Adapter and EJB applications, including sample application code, see and Callout programming models.