Note: All
FileName variables indicate the default name of the file. This can change if you override the default settings by providing specific
file names on the
Generate Web Service dialog box.
- Provider (service), WSDL Top-down
-
- Input File
- A WSDL file that describes a CICS COBOL application.
- Output Files
- When you generate a CICS Web service provider from a WSDL file
using the top-down method,
Enterprise Developer generates the following CICS Web service components in the current project folder:
- WSDLFileName.cbl
- A skeleton CICS COBOL provider program.
- WSDLFileNameI01.cpy
- A copybook containing the COBOL data structures required to send a SOAP request as input. This file is generated but does
not appear in the Solution Explorer.
- WSDLFileNameO01.cpy
- A copybook containing the COBOL data structures required to receive a SOAP response message as output. This file is generated
but does not appear in the Solution Explorer.
- WSDLFileName.svi
- A service interface file.
- Requester (client), WSDL Top-down
-
- Input File
- A WSDL file that describes a CICS COBOL application.
- Output Files
- When you generate a CICS Web service requester from a WSDL file
in a Visual Studio project
using the top-down method,
Enterprise Developer generates
a new project named
WSDLFileNameCICSClientApp that contains
the following CICS Web service components:
- First8CharsWSDLFileName.cbl
- A skeleton CICS program.
- First5CharsWSDLFileNameI01.cpy
- A copybook containing the COBOL data structures required to send a SOAP request as input.
- First5CharsWSDLFileNameO01.cpy
- A copybook containing the COBOL data structures required to receive a SOAP response message as output.
- WSDLFileName.wsbind
- A bind file that maps the SOAP request to the data structure in the input copybook, and maps the data structure in the output
copybook to the SOAP response message.
- Provider (service), WSDL Bottom-up
-
- Input Files
- CICS COBOL application that minimally consists of a main program (.cbl) file, and two copybook (.cpy) files - one containing input data structures, and one containing output data structures.
- Output Files
-
- SVIFileName.svi
- A service interface that you name and generate from the CICS COBOL application using the
Interface Mapper.
Note: This service interface must use the SOAP transport type and be defined with one operation that uses default mappings only.
- SVIFileName.wsbind
- A bind file, generated from the
.svi file, that maps the SOAP request to the data structure in the input copybook, and maps the data structure in output copybook
to the SOAP response message.
- SVIFileName.wsdl
- The Web service definition file that describes the CICS COBOL application.
- Provider (service), JSON Top-down
-
- Input Files
- A set of request and response JSON files that describe a CICS COBOL application.
- Output Files
- When you generate a CICS Web service provider from request and response JSON files in a Visual Studio project using the top-down
method,
Enterprise Developer generates the following CICS Web service components in the current project folder:
- RequestJSONFileName\First5CharsRequestJSONFileName.cbl
- A skeleton CICS COBOL provider program.
- RequestJSONFileName\First5CharsRequestJSONFileNameI01.cpy
- A copybook containing the COBOL data structures required to send a JSON request as input. This file is generated but does
not appear in the Solution Explorer.
- RequestJSONFileName\First5CharsResponseJSONFileNameO01.cpy
- A copybook containing the COBOL data structures required to receive a JSON response as output. This file is generated but
does not appear in the Solution Explorer.
- RequestJSONFileName.svi
- A service interface file that contains default mappings between the generated CICS COBOL skeleton application and the CICS
Web service described in the JSON.
- RequestJSONFileName\RequestJSONFileName.wsbind
- A bind file, generated from the
.svi file, that maps the JSON request to the data structure in the generated input copybook, and maps the data structure in the
generated output copybook to the JSON response message.
- Provider (service), RESTful JSON Top-down
-
- Input File
- One RESTful JSON file that describes a CICS COBOL application.
- Output Files
- When you generate a CICS Web service provider from RESTful JSON in a Visual Studio project using the top-down method,
Enterprise Developer generates the following CICS Web service components in the current project folder:
- JSONFileName\First8CharsJSONFileName.cbl
- A skeleton CICS program.
- JSONFileName\First5CharsJSONFileName01.cpy
- A copybook containing both input and output data structures. This file appear in the Solution Explorer as a subentry under
the generated
.cbl file.
- JSONFileName\JSONFileName.svi
- A service interface file that contains default mappings between the generated CICS COBOL skeleton application and the CICS
Web service described in the JSON.
- JSONFileName\JSONFileName.wsbind
- A bind file, generated from the
.svi file, that maps the JSON request to the input structure in the generated copybook, and maps the output data structure in
the generated copybook to the JSON response message.
- Requester (client), JSON Top-down
-
- Input File
- A set of request and response JSON files that describe a CICS COBOL application.
- Output Files
- When you generate a CICS Web service requester from set of request and response JSON files
in a Visual Studio project
using the top-down method,
Enterprise Developer generates
a new project named
RequestJSONFileNameCICSClientApp that contains
the following CICS Web service components:
- ProgramName.cbl
- A skeleton CICS program where
ProgramName is the name specified in the Generate Web Service dialog box.
- ProgramNameInBundle
- A folder that contains generated input files.
- jsbinds\First7CharsProgramNameI.json
- A JSBIND file for converting between input JSON messages and COBOL data structures.
- jsbinds\RequestJSONFilename.json
- A copy of the input JSON that corresponds to the generated skeleton CICS program.
- META-INF\cics.xml
- A reference file used by
Enterprise Server to establish the structure of the input bundle directory.
- ProgramNameOutBundle
- A folder that contains generated output files.
- jsbinds\First7CharsProgramNameO.json
- A JSBIND file for converting between output JSON messages and COBOL data structures.
- jsbinds\ResponseJSONFilename.json
- A copy of the output JSON that corresponds to the generated skeleton CICS program.
- META-INF\cics.xml
- A reference file used by
Enterprise Server to establish the structure of the output bundle directory.
- Provider (service), JSON Bottom-up
-
- Input Files
- CICS COBOL application files that minimally consists of a main program (.cbl) file, and two copybook (.cpy) files - one containing input data structures, and one containing output data structures.
- Output Files
-
- SVIFileName.svi
- A service interface that you name and generate from the CICS COBOL application using the
Interface Mapper.
Note: This service interface must use the JSON transport type and be defined with one operation that uses default mappings only.
- SVIFileName.wsbind
- A bind file, generated from the
.svi file, that maps the JSON request to the data structure in the input copybook, and maps the data structure in output copybook
to the SOAP response message.
- SVIFileNameI.json
- A JSON file that describes the input structures of the CICS COBOL application.
- SVIFileNameO.json
- A JSON file that describes the output structures of the CICS COBOL application.