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 batch server. For illustration and examples on such a server, see Batch with Standard Linkage 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 stored either
locally, that is, on the same machine where the EntireX Workbench is running 
More info
or remotely in a PDS or CA Librarian data set and accessed via the Batch RPC Server, and either EntireX Broker or Integration Server More info
You have an Integration Server with EntireX Adapter installed.
You can call the COBOL server program at runtime using different methods:
For the EntireX RPC connection method you need
an EntireX Broker on one of the supported platforms: z/OS | UNIX | Windows | BS2000/OSD | z/VSE
The Batch RPC Server
For the EntireX Direct RPC connection method you need the Batch RPC Server. See also Direct RPC 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 SVM if this is your first extraction.
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.
SVM file (optional). The server-side mapping file (SVM) contains COBOL-specific mapping information. If used, this file must
be deployed to the Batch RPC Server.
See Deploying a Server Mapping File and Handling SVM Files.
Optionally, you can test the results of the extraction operation, using the EntireX IDL Tester.
Test the COBOL Server backend using Test Software AG IDL from the Workbench:
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 IS 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 Generate webMethods Connection from IDL file.... 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 connection service.
In case of error or unexpected results, use the IDL Tester as described under Step 1.
