CICS Web Service Provider (Bottom-Up, Request-Response)

Important: Before attempting to run a CICS Web Service on Enterprise Server, review the information in the Configuration Requirements for CICS Web Services topic.
Page 1, New CICS JSON Web Service
Project
Shows the name of the project in which the CICS Web service is created. The default is the current project. Click Browse to specify a different project.
Program location
The location of the program from which to create the Web service. Click Browse to select a location.
Program name
The name of the program from which to create the Web service.
Service location
The endpoint URL used to invoke the Web service, consisting of the server, port, and a URI used to identify the Web service in Enterprise Server.
Program interface
Lists the types of interfaces you can select for this Web service: COMMAREA or CHANNEL.
Container name
Shows the name of the container associated with the selected interface. The default name for the COMMAREA interface is DFHWS-DATA, which cannot be changed. For a CHANNEL interface, this field is enabled so you can type in the name of the container.
Page 2, Interface Mapping and Output Artifacts
Request structure
The path or virtual path to and name of a program or copybook that contains the data structures required to request data. Click Browse to select a file.
Response structure
The path or virtual path to and name of a program or copybook that contains the data structures required to send data. Click Browse to select a file.
JSON request
The name of a request JSON schema file that defines input data structure. Click Browse to select a folder and/or schema file.
JSON response
The name of a response JSON schema file that defines output data structure. Click Browse to select a folder and/or schema file.
WSBIND file
The fully qualified name of the Web service bind file. Click Browse to select a folder and/or WSBIND file.
Additional parameters
Any additional parameters. See the ls2js reference topic for a list of parameters.