I am looking for a tool or technique to look at an incoming XML packets posted from a vendor’s server to an ASMX web service hosted on my IIS6 server.
Something like Fiddler but on the server side. Will Fiddler work that way?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am looking for a tool or technique to look at an incoming XML packets posted from a vendor’s server to an ASMX web service hosted on my IIS6 server.
Something like Fiddler but on the server side. Will Fiddler work that way?
Yes, fiddler will work on the server side. It will work better if you filter it by the w3wp.exe process that is hosting the web service.
But the better way of doing it is turning tracing on for the web service itself. Depending on the version of the framework, you can enable traces through the web.config: Enabling Tracing in ASP.NET Web Services, or in worse case scenarios you can write or find a SOAP hook to log out the connections. The last option works really well, but it’s not a fast fix.
For an example of using SOAP extensions to hook into the messaging and do logging for you, check out the example provided here, SoapExtension Class. Then you just add the extension to your web.config’s soapExtensionTypes Element.