Topic
1 reply Latest Post - ‏2012-11-09T17:01:10Z by PaulCooper(CICS)
SystemAdmin
SystemAdmin
270 Posts
ACCEPTED ANSWER

Pinned topic Resource not found ??

‏2012-10-25T17:59:15Z |
Hello,

I have been able to successfully generate WSDL and BIND files, my CICS resource definitions are also good. When I perform a pipeline scan the URIMAP and web service gets generated. There are no errors in MSGUSR but there is a problem :)
When I try to test the web service using RDz this is what comes up.

(Screen Shots also attached)

SOAP REQUEST ENVELOPE

  • <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:q0="http://www.xmlenablI.com/schemas/xmlenablIInterface" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  • <soapenv:Body>
  • <q0:DFHMADPLOperation>
  • <q0:service_input_area>
  • <q0:dfhmahr_requestv1>
<q0:dfhmahr_requestname />
</q0:dfhmahr_requestv1>
  • <q0:input_data_container>
  • <q0:i_nkflow>
<q0:input_account>1000</q0:input_account>
</q0:i_nkflow>
</q0:input_data_container>
</q0:service_input_area>
</q0:DFHMADPLOperation>
</soapenv:Body>
</soapenv:Envelope>

SOAP RESPONSE ENVELOPE

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  • <s:Body>
  • <s:Fault>
<faultcode>s:Server</faultcode>
<faultstring>Resource http://192.168.32.126:3081/var/cicsts/nkflowp not found</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>

Updated on 2012-11-09T17:01:10Z at 2012-11-09T17:01:10Z by PaulCooper(CICS)
  • PaulCooper(CICS)
    PaulCooper(CICS)
    1 Post
    ACCEPTED ANSWER

    Re: Resource not found ??

    ‏2012-11-09T17:01:10Z  in response to SystemAdmin
    It sounds like there's a problem with the URI for the Web Service. This is likely to mean either:

    the URIMAP has the wrong URI specified within it;
    or, the application is using the wrong URI.
    Take a look at the URIMAP in CICS. Does the 'Path' attribute match the path that your client is using? The Path is case sensitive, so that's something to be careful about. The client is trying to use access a Service published at "/var/cicsts/nkflowp". Is it possible that the client is mistaken? That URI looks like the address of a file in the Unix file system, and not the location of a Web Service on the network. My guess is that the client is using the wrong URI.

    Paul.