WEBSERVICE resources
A WEBSERVICE resource defines aspects of the run time environment for a CICS® application program deployed in a Web services setting, where the mapping between application data structure and SOAP messages has been generated using the CICS Web services assistant. Although CICS provides the usual resource definition mechanisms for WEBSERVICE resources, they are typically installed dynamically, using the output produced by the assistant.
- A pipeline
- Defines the set of message handlers that operate on Web service requests and responses. The WEBSERVICE resource specifies a separate PIPELINE resource which, in turn, specifies the pipeline configuration file.
- A Web service binding file
- Contains information that is used at run time to perform the mapping between application data structures and SOAP messages. The Web service binding file is generated by the CICS-supplied tools.
- A Web service description
- The Web services description is used only when runtime validation of SOAP messages is required. Validation of each message is performed against its schema, which is imbedded within the Web service description.
An inbound Web service request (that is, a request by which a client invokes a Web service in CICS) is associated with a WEBSERVICE resource by the URIMAP resource. The URIMAP identifies the WEBSERVICE resource that applies to the URI in the inbound message; the WEBSERVICE specifies the processing that is to be performed on the message.
Although CICS provides the usual resource definition mechanisms for creating WEBSERVICE resources, and installing them in your CICS region, you can instead use the scanning mechanism to dynamically install WEBSERVICE resources in your running CICS system. The advantages of this approach are that it reduces the amount of resource definition required, and that CICS can make direct use of information provided at development time.
To invoke the scanning mechanism, use the PERFORM PIPELINE command.
The name of a dynamically-installed WEBSERVICE is derived from
the name of the Web service binding file from which the WEBSERVICE
definition is generated, and has a maximum length of 32 characters;
the names of WEBSERVICE definitions installed from the CSD or with
the EXEC CICS CREATE WEBSERVICE are limited to
eight characters. For example, a Webservice binding file whose zFS
name is /samples/Webservices/WSDir/InquireSingle.wsbind generates
a WEBSERVICE definition named InquireSingle
WEBSERVICE resources in CICS bundles
You can use a CICS bundle to create, edit, and install a WEBSERVICE resource definition. If you create a WEBSERVICE resource in this way, you must use the CICS bundle to manage the lifecycle of that resource, and you cannot manage the resource independently.
You can inquire on a WEBSERVICE resource that is dynamically generated by a CICS bundle, by using the EXEC CICS INQUIRE WEBSERVICE or CEMT INQUIRE WEBSERVICE command. However, you cannot issue a DISCARD command against a dynamically generated WEBSERVICE resource. You must issue the command against the BUNDLE resource, and CICS applies it to the WEBSERVICE resource. For more information about defining resources in CICS bundles, see Defining CICS bundles.
