HTTP transaction monitor with capacity to replay in debuggings session

• US 7,072,951 B2
• Filed: 10/03/2001
• Issued: 07/04/2006
• Est. Priority Date: 10/03/2000
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: von Klopp, Ana H., Talmage, Elizabeth L., Finklang, George C.
• Primary Examiner(s): Cardone, Jason
• Assistant Examiner(s): Swearingen, Jeffrey R.
• Application Number:
  US09/970,114
• Publication Number:
  US 20020062359A1
• Time in Patent Office: 1,735 Days
• Field of Search: 717124-135, 717 15- 18, 717/25, 717/29, 717/31, 709/219, 709222-223, 709/232, 709/249
• US Class Current: 709/219
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system for monitoring HTTP transactions between a server and a client, including a data collector which runs on the server and collects data from HTTP requests sent by the client to the server and data from HTTP responses sent by the server to the client, a debugging controller which controls an execution mode of the server, a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server, a request player which runs on the server and modifies each replay request with a portion of the collected data associated with the prior HTTP request to be interpreted by the server.

Claims

1. A system for monitoring HTTP transactions between a server and a client, comprising:

a data collector which runs on the server and collects data from HTTP requests sent by the client to the server and data from HTTP responses sent by the server to the client;

a debugging controller which controls an execution mode of the server;

a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server; and

a request player which runs on the server and modifies each replay request with a portion of the collected data associated with the prior HTTP request to be interpreted by the server.

2. The system of claim 1, wherein the execution mode is debugging.

3. The system of claim 2, further comprising:

a debugger accessed by the server.

4. The system of claim 1, wherein the execution mode is normal.

5. The system of claim 1, wherein the debugging controller determines the execution mode using information gathered by a graphical user interface (GUI) and an integrated development environment (IDE).

6. The system of claim 1, wherein the request player modifies the replay requests prior to the server interpreting the replay requests.

7. The system of claim 6, wherein the request player comprises a process which uses a hook in the server to intercept the replay requests in order to modify the replay requests.

8. The system of claim 6, wherein the request player comprises a process which uses a hook in a server plug-in to intercept the replay requests in order to modify the replay requests.

9. The system of claim 1, wherein the collected data are stored in a directory on the server.

10. The system of claim 9, further comprising means for retrieving the collected data from the directory and serving the data to the request player and the graphical display.

11. The system of claim 1, further comprising means for re-processing a selected number of HTTP requests in a predetermined sequence.

12. The system of claim 1, wherein an application which provides the graphical display manages the collected data.

13. The system of claim 11, wherein the application is an integrated development environment for a web application.

14. The system of claim 1, wherein the debugging controller runs on the client.

15. The system of claim 1, further comprising means for notifying the graphical display when new data is collected by the data collector.

16. A system for testing and debugging a web application, comprising:

a server which hosts the web application;

a client which accesses components of the web application by sending HTTP requests to the server and receiving HTTP responses from the server;

a data collector which runs on the server and collects data from the HTTP requests and the HTTP responses;

a debugging controller which runs on the client and controls an execution mode of the server;

a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server; and

a request player which runs on the server and modifies each replay request with a portion of the collected data associated with the prior HTTP request to be interpreted by the server.

17. The system of claim 16, wherein the execution mode is debugging.

18. The system of claim 17, further comprising:

a debugger accessed by the server.

19. The system of claim 16, wherein the execution mode is normal.

20. The system of claim 16, wherein the debugging controller determines the execution mode using information gathered by a graphical user interface (GUI) and an integrated development environment (IDE).

21. The system of claim 16, further comprising:

an application which starts the server in a separate process and through which the graphical display can be accessed.

22. The system of claim 21, wherein the application is an integrated development environment for a web application.

23. The system of claim 22, wherein the client is accessible from within the integrated development environment.

24. The system of claim 21, wherein the application includes an internal server.

25. The system of claim 24, wherein the internal server updates the graphical display with the collected data.