| Which protocol to use? |
|
|
|
| Written by TnT Admin |
| Monday, 21 April 2008 00:00 |
|
The fact is that it doesn’t really matter the type of language that was used to developed the application, but rather the type of communication method or protocol that the application is talking to the server. Previously, in "What's LoadRunner?", we mentioned that the tool captures network traffic while recording which is the core understanding that we must align when using this tool.
For example, an application can be developed using .NET 2.0 framework, is window-based (Win32). This application can be part of a N-Tier architecture that utilizes HTTP or HTTPS to communicate to the middle-tiers or a 2-Tier architecture that talks to the database directly using ODBC, ADO or JDBC-ODBC.
Similarly, an application can be developed using Java, but it talks to the middle-tier using RMI-Java or HTTP, or to its database using JDBC.
To understand the protocol used by the application (client to server), you can do the following.
1. The easiest way, check with the application team or vendor, particularly the software architects and the developers. They should be able to provide such information. If they don’t, it ’s time to doubt the experiences of the application team.
2. Use WireShark Network Analyzer to sniff the traffic communication when the application is running. More details of the usage can be found in the provider’s site. You should be able to see the protocols under the protocol column after you start capturing the traffic.
3. Use netstat -a to determine the protocol and port number. For example, the protocol is TCP and port number is 80, it could signifies HTTP. The caveat for this is that netstat -a only display protocol in IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6 (/? help for more information), which means you may need to guess the protocol according to the protocol (TCP) and port number.
4. Use Winsock protocol to determine the protocol via the data files. Winsock captures all traffic of any type at the socket level and writes it to the data file. From the data file, you will then find signatures of the protocol such as HTTP requests and responses in the context of HTTP.
Hopefully this methods are sufficient for you to determine the protocol used. Feel free to comment if you have a better method.
|
| Last Updated ( Tuesday, 16 September 2008 10:54 ) |







Javascripts are not recorded. There is no functional aspect that is being recorded. Javascript will be recorded as pure text in the HTML page. Vugen will not render the javascript but treats it as text. Can you provide more details of the problem? Can't really make out on the "When I try to play back my test, it fails to the link & my members can not be invited."