Debugging BizTalk SOAP messages ... with WireShark or what?

I am trying to figure out what is causing the BizTalk call to the web service and see what the actual content of the post is. I found Elton Stoneman's blog while using WireShark which got me going and now I can at least see the POST and SOAP response packets, but getting the actual content is very time consuming ... copy and paste into notepad ...

Is there a better way to see the message?
- I tried using Fiddler but it didn't see any messages
- while at least WireShark can see things

And if you have any suggestions please post them as this is a new area for me :-)

+1
debugging soap biztalk


a source to share


6 answers


I see two options here. In Wireshark, you can select a packet from the connection of interest, and in the Analyze menu, select "Follow TCP Stream". This will bring up a new window displaying the correctly ordered TCP data for this connection.



However, it may be more convenient to collect data using the tcpflow program , which will write this to text files that you can use for later analysis.

+4


a source to share


There are two really good SOAP debugging utilities ...

** Fiddler2

http://www.fiddler2.com/fiddler2/

It's a relatively simple utility - you can capture requests and responses. If you're lucky, you can force it to act as a proxy, so you don't need to reconfigure anything. I've had a lot of experience with this, so I usually just reconfigure my ports to grab it.

The downside to Fiddler is that it matches a response request, so it won't display messages that don't receive responses. If you are debugging something that may not respond or want more, try soapUI.



** soapUI

http://www.soapui.org/

This is similar to Fiiddler2 but goes further. You can capture requests and responses and then you can modify the request yourself and send it to the endpoint. You can also use the captured responses to make soapUI act as a mock server for you. These two capabilities are really useful when it takes a long time to create a request or you want to see how your systems handle certain types of responses.

(I am not an affiliate, just a happy customer!)

+2


a source to share


Windows Network Monitor has always been my tool of choice:

Windows Network Monitor 3.3

Requires knowledge of multiple network protocols but is very easy to use. I have debugged HTTP, SOAP and FTP with this.

+1


a source to share


I was pleased with Simon Fell YATT, "Yet Another Trace Tool" from PocketSoap.com. You can view all traffic on a given network connection, or you can filter it.

Like all tracers, letting it run open and unfiltered will scare you when you find out how many of your benign applications are "calling home" every once in a while.

Beware, however, that if you are using SSL (HTTPS) it will be difficult for you to track the contents of the packages.

+1


a source to share


To use Fiddler2 with a BizTalk application pointing to a local service, you will need to replace the hostname "localhost" with "ipv4.fiddler"

Eg. Http: // ipv4.fiddler : 8080 / UrlToYourService

+1


a source to share


You can use Microsoft SOAP Toolkit , then if you are using WCF adapter use clientVia .

If you are interested in the message itself (not the complete SOAP stuff), you can set up a send port group and send each message to both the WebService and a local folder. This way you can easily see the content of all sent messages.

0


a source to share







All Articles