I came across the link below describing how to re-construct a proper WSDL from web-service proxy.
As explained in the documentation, This article is written for WebSphere DataPower SOA Appliances administrators and developers who have had interoperability issues with web services consumers that require the schema to be embedded in the WSDL, instead of a reference to the XSD schema file.
I need this behavior in my use case, where a flex application would want to invoke a data-power proxy, using 'Web service' tag in actionscript/MXML syntax. However, when I try to implement this, I come across a blank screen instead of the well constructed web service WSDL showing up. I have attached the log from data power for reference and further analysis. Please do provide your valuable feedback in this regard. Do let me know if any other details are needed.
15:15:37 network error 10112927 request 22.214.171.124 0x80e00041 mpgw (TestAMFMPGW): url-open: Error parsing response from 'http://10.235.26.51:82/EAWebService/services/EaMalwareScannerIPort?wsdl'
15:15:37 xmlparse error 10112927 request 126.96.36.199 0x80e003aa mpgw (TestAMFMPGW): Incomplete markup or missing document element at offset 0 of http://10.235.26.51:82/EAWebService/services/EaMalwareScannerIPort?wsdl
thanks and have a good day!
This topic has been locked.
6 replies Latest Post - 2013-02-27T19:19:53Z by ShubhaPandit
Pinned topic WSDL from web service proxy
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-27T19:19:53Z at 2013-02-27T19:19:53Z by ShubhaPandit
SystemAdmin 110000D4XK6772 PostsACCEPTED ANSWER
Re: WSDL from web service proxy2012-11-13T09:31:50Z in response to mdindagurHi Manesh,
It would be very useful if you could attach the full trace of your logs or an export of your configuration.
However, it seems that the MPG can not retrieve the wsdl file:
I am assuming that his URL is right and your WSP have at least one Front Side Handler listening to connections in http://10.235.26.51:82. If that is the case, I would check if the GET method is enabled as well.
Re: WSDL from web service proxy2012-11-13T14:27:50Z in response to SystemAdminHi Jaime,
Appreciate your quick response in this regard. Please find attached the MPGW as well as WSP configuration exports for your reference(i bundled up two exports into a zip file). I found it easier to send these configurations instead of the complete trace.
Also, http://10.235.26.51:3097/EAWebService/services/EaMalwareScannerIPort?wsdl contains the readable WSDL from WSP. Port 82 is configured for FSH for MPGW, as you can see from the configuration.
Do let me know if you need more details in this regard. Again, appreciate your speedy response.
Re: WSDL from web service proxy2012-11-13T16:34:12Z in response to mdindagurHi,
I also came across the following forum-post related to the subject.
Here is an attachment of export capture after going through the following instructions..
(1) Chain all WSP's with an MPG. This is something we were doing already because it provides a certain amount of flexibility.
(2) In the chained MPG, enable GET on a processing rule and use a URL Match regex for WSDL's -- (.)*((\?|\.)(wsdl|WSDL))$
(3) Set the backend URL in the MPG to either:
(a) The ?WSDL URL to the WSP for interfaces that have consumers with no issues consuming external schema references
(b) A directory and path on the local appliance to a static WSDL.
I am curious to know why the single invocation of ?wsdl on the MPGW captures 3 requests on the probe, eventually resulting in the error as mentioned earlier
mpgw (TestAMFMPGW): Incomplete markup or missing document element at offset 0 of http://10.235.26.51:82/EAWebService/services/EaMalwareScannerIPort?wsdl.
Hope this information will provide you with all details needed to analyze and point out the issue.
JJH 060000C7KJ1 PostACCEPTED ANSWER
Re: WSDL from web service proxy2013-01-03T19:09:11Z in response to mdindagurMahesh,
Did you ever get an answer to this? I have the same issue with the tech article --> http://www.ibm.com/developerworks/websphere/library/techarticles/1209_talavera/1209_talavera.html#download
Any help from you or Mr Talavera would be much appreciated.