I have webMethods Integration Server v6.0.1 installed.
Need to implement webservices using document/literal format.
From the wsdl I have created the web services connector.
When I invoke the web service connector, I get a SOAP-FAULT.
faultcode is SOAP-ENV:Client
faultstring [ISS.0088.9119] SOAP Processor did NOT return a valid SOAP Response
On the service provider side when we run the same service from pipeline, SoapResponseData which is being created looks to be fine. Here it is:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:SOAP-ENC=“http://schemas.xmlsoap.org/soap/encoding/” xmlns:xsd=“http://www.w3.org/1999/XMLSchema” xmlns:xsi=“http://www.w3.org/1999/XMLSchema-instance” SOAP-ENV:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/”>
I have put logs in the webservice provider flow and it gets called but the SoapResponseData is not being sent to the webservice client or the client is not recognising the soap response.
Could any of you please guide what may be wrong.
What is the soap endpoint url listed in your WSDL? Is “hostname:port” just used for your posted message or is that actually in your WSDL?
Not sure how you are testing your web service operation “from pipeline” or how that differs from the web service connector. Trace through the web service connector to confirm that the soapRequestData contains the soap request message needed to invoke your web service operation.
Read the many posts here about shortcomings of web service connector-generated Flow services.
This is the endpoint and is same as in the wsdl file
Reg testing in the flowservice,will put savepipeline after converting into document.From that pointonwards will debug and genarate the soapresponseData.The soapresponse data is forming and able to see in the result panel.
Below is the message always getting after invoking webservice.
[ISS.0088.9119] SOAP Processor did NOT return a
valid SOAP Response
Well, that’s nice.
How about sharing the resolution so that you might help someone with a similar problem in the future?
Thats was a simple mistake of me,with namespace and because of that some conflict has happend along with the outgoing outputput doc.
I made it correct and it works fine!!!