Each function exposed as a Web service requires a WEBSERVICE resource to map between the incoming XML of the SOAP BODY and the COMMAREA interface of the program, and a URIMAP resource that routes incoming requests to the correct PIPELINE and WEBSERVICE. Although you can use RDO to define and install your WEBSERVICE and URIMAP resources, you can also have CICS® create them dynamically when you install a PIPELINE resource.
When the PIPELINE is later disabled and discarded all associated WEBSERVICE and URIMAP resources will also be discarded.
If you have already installed the PIPELINE, use the PERFORM PIPELINE SCAN command to initiate the scan of the PIPELINE's pickup directory.
I WEBS STATUS: RESULTS - OVERTYPE TO MODIFY Webs(dispatchOrder ) Pip(EXPIPE02) Ins Dat(20041203) Webs(dispatchOrderEndpoint ) Pip(EXPIPE01) Ins Uri(£539140 ) Pro(DFH0XODE) Com Dat(20041203) Webs(inquireCatalog ) Pip(EXPIPE01) Ins Uri(£539141 ) Pro(DFH0XCMN) Com Dat(20041203) Webs(inquireSingle ) Pip(EXPIPE01) Ins Uri(£539142 ) Pro(DFH0XCMN) Com Dat(20041203) Webs(placeOrder ) Pip(EXPIPE01) Ins Uri(£539150 ) Pro(DFH0XCMN) Com Dat(20041203)The display shows the names of the PIPELINE, the URIMAP, and the target program that is associated with each WEBSERVICE. Note that in this example, there is no URIMAP or target program displayed for WEBSERVICE(dispatchOrder) because the WEBSERVICE is for an outbound request.
WEBSERVICE(dispatchOrderEndpoint) represents the local CICS implementation of the dispatch order service.