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.
- JSON request
- The fully qualified name of the JSON schema file that contains the input data area. Click
Browse to select a schema file.
- JSON response
- The fully qualified name of the JSON schema file that contains the output data area. Click
Browse to select a schema file.
- 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, Additional Parameters and Output Artifacts
-
- Program name
- The name of the program from which to create the Web service.
- Request file prefix
- A file prefix for the generated copybook containing the request data structure.
- Response file prefix
- A file prefix for the generated copybook containing the response data structure.
- WSBIND file
- The fully qualified name of the Web service bind file.
Click
Browse to select a folder and/or WSBIND file.
- Default string length
- The maximum number of characters that can be processed in a COMMAREA or CHANNEL string.
- Default array size
- The maximum number of times a single array can be processed by a COMMAREA or CHANNEL string.
- Additional parameters
- Any additional parameters. See the
js2ls reference topic for a list of parameters.