Need help on SOAP trace
-
Hello, anyone knows how to configure the Soap Trace Utility that comes along with the SOAP toolkit 3.0. I encounter difficulty in configuring it to trace .ASPX page. In the help file. it stated In the WSDL file, locate the element that corresponds to the service and change the location attribute for this element to port 8080. For example, if the location attribute specifies change this attribute to . But, there is not WSDL file for a .ASPX file. The WSDL document is generated runtime by the .NET when passing the query string as http://localhost/test.aspx?WSDL How to confgure it to the WSDL file? I need to trace the content of the SOAP communication between client and server. Any good trace tool will be great. Thank you.
-
Hello, anyone knows how to configure the Soap Trace Utility that comes along with the SOAP toolkit 3.0. I encounter difficulty in configuring it to trace .ASPX page. In the help file. it stated In the WSDL file, locate the element that corresponds to the service and change the location attribute for this element to port 8080. For example, if the location attribute specifies change this attribute to . But, there is not WSDL file for a .ASPX file. The WSDL document is generated runtime by the .NET when passing the query string as http://localhost/test.aspx?WSDL How to confgure it to the WSDL file? I need to trace the content of the SOAP communication between client and server. Any good trace tool will be great. Thank you.
Editing the location uri in the WSDL file would tell clients to connect to the web service using a different port if they parse the wsdl file (The COM Web Service client and the javascript client do parse this file). This allows the trace utility to intercept the SOAP messages. ASP.NET generates the wsdl document based on the port that the client is connecting on. Hence if you connect to your web service using http://server:8080/webservice/ws.asmx?wsdl, the wsdl document will have the same url in the location attribute. Are your web service clients developed using the "add web reference" in Visual Studio? If so the url (including the port) of the web service will be hard coded, unless you changed the "URL Behavior" of the reference to Dynamic. The clients will always try and connect on that url. If you chose Dynamic, then you can alter the [application].config files for the client to point to a different port ('8080' for the trace tool). If you can not control the url clients use to connect (if you are using the COM client for example) you could try pointing the clients at a copy of the wsdl file that has the location attribute updated to point to the relevant url and port as required by the trace utility. I hope this helps Regards Mark Smithson