"WebService" Debugging method chapter (i)

Develop WebService, encounter problems to know the importance of the message. Seven-layer computer network, only understand the top layer, will always be just a rookie.

Fat to the chase. In the development process, I used the test software: tcpTrace, SoapUI 5.0.0, Wireshark.

1, TcpTrace, lean and easy to use message cutting tools. Ultra lightweight, the entire tool 300k (remember correctly). Double-click Open is set interface, listening port set to 8811, the forwarding server is set to localhost, the forwarding port is set to 8086, meaning is listening to the 8081 port of the machine, this is a message forwarding tool, is to send to my native 8081 port of the message will be transferred to the setting server (I here is localhost) 8086 port, while the request message content, return message display. Suppose I am the tomcat of the machine is 8086, but tell others is 8081, others visit, you can intercept the message, the process must be opened tcptrace.

2, SoapUI, see the name will know, specifically used to do WebService debugging tools. I don't use a lot of time, but I still recommend this test software. Although the e-text, but get hands can be used immediately, open source, operation is very simple. Because I only used to do webservice test, for already deployed WebService, want to get its WSDL. The steps are probably, new SOAPUI project, fill in your project name,initial wsdl/wadl This column fill in the WSDL URL address or directly import the WSDL file, similar operation using the tutorial, online can easily find, here is no longer swim.

3, Wireshark, message analysis Tools, formerly known as Ethereal, familiar with it. When you use N multi-method also did not fix, and the manufacturers there is just nothing to understand the support, what is worse, this support has not contacted the developer Programmer's ability, that all can rely on their own. Of course, the best way to do this is to grab packet analysis. At that time I was responsible for the development of the server, but the client's code is written well, the specification document is also a lever, the server must follow the client's request to get, feel the world has turned over. Because the code is put on the Linux server running above, then I am on the Linux grab command is like this: Tcpdump-i eth1 host 10.234.153.81 and Port 8811-s1000-w/USR/LOCAL/TMP/PRC _.cap, is to listen to my local IP 8811 port of the message, let the other side to visit my side, the last received message saved to/usr/local/tmp/Prc_.cap, with the Wireshark open on it, it is easy to find the message content.

The message is a good thing, according to the message can easily know where the error, when you how to debug and unsuccessful, analysis of the message, you may find that is your "namespace" mistaken bird.

Reprint please indicate from whilejolly:http://blog.csdn.net/seedingly/article/details/39053327

"WebService" Debugging method chapter (i)