Author: Robert Sample
Posted: Sat Mar 11, 2017 1:15 am (GMT 5.5)
The Implementing CICS Web Services Redbook (SG24-7657) has this starting on page 46 (emphasis added by me):
So the answer to your question is that you need to look wherever YOU set up the WSDL file; we don't know this because YOU did it. If you didn't set up the WSDL file, you should find out who did it and get the location from them. If there is no WSDL file, then that could be a clue as to why your process isn't working.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Sat Mar 11, 2017 1:15 am (GMT 5.5)
The Implementing CICS Web Services Redbook (SG24-7657) has this starting on page 46 (emphasis added by me):
| Quote: |
| We go through the following steps: 1. We generate the wsbind and WSDL files (application developer). a. We first create an HFS directory in which to store the generated files. For example, we might create a directory named /u/SharedProjectDirectory/MyFirstWebServiceProvider. b. We next run the DFHLS2WS program. The input we provide to the program includes the following information: ⢠The names of the partitioned data set members that contain the high level language structures that the application program uses to describe the Web service request and the Web service response. ⢠The fully qualified HFS names of the wsbind file and of the file into which the Web service description is to be written (the WSDL file). ⢠The relative URI that a client uses to access the Web service. ⢠How CICS should pass data to the target application program (COMMAREA or container). Typically, an application developer would perform this step. 2. Create a TCPIPSERVICE resource definition (system programmer). The resource definition should specify PROTOCOL(HTTP) and supply information about the port on which inbound requests are received. Typically, a system programmer would perform this step. 3. Create a PIPELINE resource definition (system programmer). a. Create a service provider pipeline configuration file. A pipeline configuration file is an XML file that describes, among other things, the message handler programs and the SOAP header processing programs that CICS invokes when it processes the pipeline. b. Create an HFS directory in which to store installable wsbind and WSDL files. We call this directory the âpickupâ directory since CICS picks up the wsbind and WSDL files from this directory and store them on a âshelfâ directory. c. Create an HFS directory for CICS in which to store installed wsbind files. We call this directory the âshelfâ directory. d. Create a PIPELINE resource definition to handle the Web service request. ⢠Specify the CONFIGFILE attribute to point to the file created in step 3a. ⢠Specify the WSDIR attribute to point to the directory created in step 3b. ⢠Specify the SHELF attribute to point to the directory created in step 3c. e. Copy the wsbind and WSDL files created in step 1 to the pickup directory created in step 3b. 4. Install the TCPIPSERVICE and PIPELINE resource definitions (system programmer). When the CICS system programmer installs the PIPELINE definition, CICS scans the pickup directory for wsbind files. When CICS finds the wsbind file created in step 1, CICS dynamically creates and installs a WEBSERVICE resource definition for it. CICS derives the name of the WEBSERVICE definition from the name of the wsbind file. The WEBSERVICE definition identifies the name of the associated PIPELINE definition and points to the location of the wsbind file in the HFS. During the installation of the WEBSERVICE resource: â CICS dynamically creates and installs a URIMAP resource definition. CICS bases the definition on the URI specified in the input to DFHLS2WS (see step 1) and stored by DFHLS2WS in the wsbind file. â CICS uses the wsbind file to create main storage control blocks to map the inbound service request (XML) to a COMMAREA or a container and to map to XML the outbound COMMAREA or container that contains the response data. 5. Publish WSDL to clients. a. Customize the location attribute on the <address> element in the WSDL file so that its value specifies the TCP/IP server name of the machine hosting the service and the port number defined in step 2. b. Publish the WSDL to any parties wishing to create clients to this Web service. |
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth