EntireX Version 9.7
 —  Common Integration Scenarios  —

Calling COBOL DFHCOMMAREA (Zero Footprint using CICS ECI) from Integration Server

This scenario uses the EntireX Workbench tools IDL Extractor for COBOL and Integration Server Wrapper of the Software AG Designer.

This document covers the following topics:


Introduction

graphics/cob2is-zos-cics-dfh-solution.png

graphics/blue_1.gif Extract the interface of the COBOL server program.
graphics/blue_2.gif Generate connection and adapter services in Integration Server.
graphics/blue_3.gif Execute the call from Integration Server to the COBOL server program.

This scenario makes the following important assumptions:

For Task 1:

For Tasks 2 and 3:

Top of page

Task 1: Extract the Interface of a COBOL Server

Follow the instructions for extracting COBOL, see Using the IDL Extractor for COBOL - Overview and choose Scenario I: Create New IDL and Server Mapping Files if this is your first extraction.

If you have not yet set the type of COBOL mapping for the Workbench (Eclipse workspace), you are asked to set this first. We recommend using client-side mapping if you are new to EntireX.

graphics/cob2is_common_extract.png

Start of instruction setTo extract the COBOL server

  1. Set the correct interface type in Step 4: Define the Extraction Settings and Start Extraction in the IDL Extractor for COBOL documentation of Scenario I: Create New IDL and Server Mapping Files.

    graphics/cob2is-zos-dfh_extract.png

  2. Set the correct value for checkbox Input Message same as Output Message:

  3. Continue with specific information on this interface type, depending on whether the input and output parameters are the same or different (checkbox Input Message same as Output Message checked or cleared).

    This process creates the following EntireX metafiles:

Start of instruction setTo test the extraction results (optional)

  1. You can test the results of the extraction operation and the Natural Server back end, using the EntireX IDL Tester. From the context menu of the IDL file in the EntireX Workbench, choose Software AG IDL Tester.

    graphics/common_test-idlTester.png

    Note that the Broker and Server parameters contain the explicit route to call the server program, and you can optionally ping the connection from this client. See EntireX IDL Tester in the EntireX Workbench documentation.

  2. Check the Integration Server log, the EntireX Adapter log or the RPC logs. Applies to all connection methods.

Top of page

Task 2: Generate the Connection and Adapter Services in Integration Server

This step is described in more detail under Using the Integration Server Wrapper.

Select the IDL file, and from the context menu choose Integration Server > Generate Web Methods Connection. From the wizard, select an Integration Server instance and select the connection type.

graphics/cob2is-common-cics-dfhz_generate.png

Then select the namespace where you want to write the services to, and specify the connection properties.

graphics/common_generate-defineAdapterServices.png

Choose Finish. The connection service will be automatically enabled in the Integration Server.

Top of page

Task 3: Execute the Call from Integration Server to COBOL

From the Service Development perspective, refresh the package where the connection service was written, select the adapter service and use the service test to Run Service.

graphics/common_test-calc.png

This invokes the adapter service through the connector service.

In case of error or unexpected results:

Top of page