Non-managed (client-managed) callout programming model

You can use the non-managed callout programming model to retrieve IMS™ application callout requests from any external Java™ applications that do not use a message-driven bean.

For any response data to a callout request, the Java application can send the response data either synchronously to the same IMS application in the same transaction or asynchronously in a different transaction.

For a synchronous callout request, unlike in the managed callout programming model where the callout protocol and response correlation are handled for you through the message-driven bean, you must handle the following issues in your Java application:

Because you must handle the synchronous callout protocol and the correlation of response messages to the request, this programming model is also called client-managed callout programming model.

In general, the following tasks are required when you use the client-managed callout programming model:

  1. Your WebSphere® Application Server administrator must configure a shareable connection factory to be used by the Java application to retrieve the callout requests.
  2. Retrieve the callout messages from the IMS OTMA hold queue (tpipe).