Running the IMS TM resource adapter callout IVP sample

The callout IVP sample contains a message-driven bean that is designed to process both synchronous and asynchronous callout requests from sample IMS™ applications. The callout IVP sample also includes sample IMS applications and associated setup files on the IMS host system to enable the sample IMS applications to issue a callout request for the message-driven bean to process.

Before you begin

Prerequisite: A set of jobs and tasks in the installation verification program (IVP) is provided that you can modify to set up the IMS OTMA destination descriptors and the transaction pipes (tpipes). The OTMA destination descriptors, one for synchronous and the other for asynchronous callout requests, describe where the callout requests are queued (tpipe name). For IMS Version 11, the IVP jobs and tasks are supplied in the following APARs:
Table 1. APAR requirements for IMS Version 11
APAR PTF Description
PK97597 UK61338 IMS IVP support for the callout function
PK85023 UK48124 Java™ support for the DL/I ICAL call
PM29392 UK64387 Synchronous and asynchronous callout IVP sample for IMS TM resource adapter

About this task

Two jobs are provided for you to run the provided IMS applications to issue callout requests.

Table 2. The IVP jobs, TPIPE name, OTMA destination descriptor, and COBOL application part name for the asynchronous and synchronous callout samples
Type of callout requests Job TPIPE OTMA destination descriptor Part name for the COBOL application
Asynchronous IV_S227J IVPPIPE3 IVPDTOR3 DFSASCBL
Synchronous IV_S228J IVPPIPE4 IVPDTOR4 DFSSSCBL
Two simple IMS BMP applications are provided.
  • One application uses the IMS DL/I testing program, DFSDDLT0, to issue a DL/I ICAL call for sending a synchronous callout request. This ICAL call specifies the tpipe for holding the callout request, the OTMA destination descriptor for routing of the callout message, and the request and response areas in the callout message.
  • The other application uses the IMS DL/I testing program, DFSDDLT0, to issue an insert (ISRT) to an alternate PCB (program communication bolck) call to place the asynchronous callout request on the IVPPIPE3 tpipe.

The IMS TM resource adapter callout IVP sample is a simple message-driven bean that is installed with the IMS TM Resource Adapter runtime installation. The bean can be deployed to your WebSphere® Application Server environment to verify that the bean can receive either an asynchronous or synchronous callout request from an IMS application, and, in the case of a synchronous callout request, send a response. This sample is designed to work with the IMS callout IVP samples, with the pre-defined tpipes and OTMA destination descriptors.

The general tasks involved to implement a callout solution for an IMS application are as follows:

Table 3. Steps to implementing a callout solution for an IMS application
Step Description Environment in which the task is performed How the tasks are handled by the callout sample
1 Create or modify an IMS application to issue a callout request by using the DL/I ICAL call (synchronous) or ISRT altpcb call (asynchronous) IMS host system The IMS callout sample IVP provides an IMS application.
See the related IVP jobs in the IMS installation information. Run the IVP jobs to compile and bind the samples:
2 Define an OTMA destination descriptor
3 Restart IMS for the newly defined OTMA destination descriptor
4 Create a message-driven bean or J2C application to process the IMS inbound transaction. IBM® Rational® Application Developer for WebSphere Software. or other application development environments The IMS TM resource adapter callout IVP sample provides this message-driven bean.
5 Deploy the IMS TM resource adapter runtime in the Java EE application server. Your Java EE application server. See:
6 Configure a J2C activation specification in the Java EE application server and specify the connection information, such as the IMS host name, port number, data store name, and queue name (tpipe name) for the IMS TM resource adapter to pull callout messages. See Configuring a J2C activation specification for the callout IVP.

For WebSphere Application Server Community Edition, the J2C activation specification information is specified in the deployment plan XML file. See Deploying the sample application on WebSphere Application Server Community Edition to process callout requests.

.
7 Deploy the message-driven bean or J2C application in the Java EE application server, and start the application. See: .
8 Run the IMS application to issue the synchronous callout request or asynchronous callout request IMS host system See Running the IMS host callout IVP application.

Feedback