Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability; however, this feature is not intended for production use and it is not supported as such. Furthermore, Micro Focus does not guarantee that this feature will be delivered at a GA level and if it is, then the functionality provided might differ considerably from this technology preview.
The following components are either used as input or are generated as output, depending on the type of CICS Web Service:
- Existing CICS COBOL Application files
- You can expose functionality from an existing CICS COBOL application as a CICS Web service by providing its source code, including copybooks, as input files. From these,
Enterprise Developer generates a WSDL file and a WSBIND file.
- Web Service Definition Language (WSDL) file
- When generating a CICS Web service provider or requester using the top-down method, you must provide an existing WSDL file as input.
When generating a bottom-up Web service provider,
Enterprise Developer generates a WSDL file as output.
- Web Service Bind (WSBIND) file
- This file is generated for all CICS Web service types, and is required to bind appropriate CICS COBOL applications to generated Web services.
- CICS COBOL Provider skeleton program
- As part of CICS Web Service provider generation,
Enterprise Developer generates a skeleton CICS COBOL program that can be used as the basis for a new CICS Web service provider application.
- CICS COBOL Requester skeleton program
- As part of CICS Web Service requester generation,
Enterprise Developer generates a skeleton CICS COBOL requester program that can be used as the basis for a new CICS Web service requester application.
- Request copybook
- Contains generated request data structures used by either a generated provider or requester CICS COBOL program.
- Response copybook
- Contains generated response data structures used by a CICS COBOL generated provider or requester program.
- Messages copybook
- Contains generated message data structures used by a generated CICS COBOL provider or requester program.
The following table shows the required input and generated output files for each type of CICS Web service:
| Web Service Type
|
Input
|
Output
|
|
Bottom-up provider
|
- CICS COBOL program (.cbl) file
- Copybooks included by the program
|
|
|
Top-down provider
|
|
- CICS COBOL provider program
- Request copybook file
- Response copybook file
- Messages copybook file
- WSBIND file
|
|
Top-down requester
|
|
- CICS COBOL requester program
- Request copybook file
- Response copybook file
- Messages copybook file
- WSBIND file
|
