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:
 |
Extract the interface of the COBOL server program. |
 |
Generate connection and adapter services in Integration Server. |
 |
Execute the call from Integration Server to the COBOL server program. |
This scenario makes the following important assumptions:
You have a working COBOL DFHCOMMAREA server. For illustration and examples on such a server, see CICS with DFHCOMMAREA Calling Convention.
You have access to the related COBOL sources and copybooks. The minimum requirement is the DATA DIVISION of the interface. The sources and copybooks must be local, that is, on the same machine where EntireX Workbench is running.
More info
You have an Integration Server with EntireX Adapter installed.
To call the COBOL server program at runtime using the EntireX CICS ECI connection method, you need to configure the CICS ECI TCP/IP service within your CICS region. See Preparing IBM CICS for ECI in the webMethods EntireX Adapter documentation.
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.
To extract the COBOL server
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.
Set the correct value for checkbox Input Message same as Output Message:
Check the checkbox if the COBOL data structure of the CICS input message is the same as the structure of the CICS output message. See the following COBOL server examples:
Clear the checkbox if the COBOL data structure of the CICS input message is different to the structure of the CICS output message, that is, the output overlays the input. See the following COBOL server examples:
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:
IDL file. A Software AG IDL file contains definitions of the interface between client and server. See Software AG IDL File.
Server mapping file (optional). The mapping file is an EntireX Workbench file with extension .svm or .cvm that contains COBOL-specific mapping information. See Server Mapping Files for COBOL in the EntireX Workbench documentation.
To test the extraction results (optional)
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 .
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.
Check the Integration Server log, the EntireX Adapter log or the RPC logs. Applies to all connection methods.
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.
Then select the namespace where you want to write the services to, and specify the connection properties.
Choose . The connection service will be automatically enabled in the Integration Server.
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.
This invokes the adapter service through the connector service.
In case of error or unexpected results:
Check the Integration Server log, the EntireX Adapter log or the RPC logs. Applies to all connection methods.
Use the IDL Tester as described under Step 1 above.
