HTTP transaction monitor with sequence replay capacity

• US 20020062369A1
• Filed: 06/05/2001
• Published: 05/23/2002
• 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., Finklang, George C.
• Granted Patent: US 7,099,939 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method for monitoring data flow in a web application hosted on a server includes obtaining a list of HTTP requests processed on the server while interacting with the web application, selecting a number of HTTP requests from the list, and sending a request to the server to re-process the selected number of HTTP requests in a predetermined sequence.

Claims

1_9. ] A method for monitoring data flow in a web application hosted on a server, comprising:

obtaining a list of HTTP requests processed on the server while interacting with the web application;

selecting a number of HTTP requests from the list; and

sending a request to the server to re-process the selected number of HTTP requests in a predetermined sequence.

2_9. ] The method of claim 1, wherein the predetermined sequence corresponds to the order in which the selected number of HTTP requests were originally processed by the server.

3_9. ] The method of claim 1, wherein sending a request to the server comprises sending the selected number of HTTP requests to the server according to the predetermined sequence.

4_9. ] The method of claim 3, wherein each of the selected number of HTTP requests has a timeout period within which it should be completely processed by the server.

5_9. ] The method of claim 4, further comprising displaying a notification if the timeout period is exceeded before the HTTP request is completely processed by the server.

6_9. ] The method of claim 4, further comprising displaying an output of the server after processing each HTTP request.

7_9. ] The method of claim 4, further comprising displaying an output of the server after processing the last HTTP request in the predetermined sequence.

8_9. ] The method of claim 3, further comprising editing data associated with a selected one of the selected number of HTTP requests.

9_9. ] The method of claim 8, further comprising reconstructing the selected one of the selected number of HTTP requests with the edited data prior to the server re-processing the selected one of the selected number of HTTP requests.

10_9. ] The method of claim 1, further comprising collecting data passed between components of the web application before and after each HTTP request is processed.

11_9. ] The method of claim 10, wherein the collected data comprises one selected from the group consisting of data contained in the HTTP request, data contained in an HTTP response generated after processing the HTTP request, properties of dynamic component invoked by the server to process the HTTP request, data contained in a cookie associated with the HTTP request, data contained in a cookie associated with the HTTP response, and combinations thereof.

12_9. ] A method for monitoring data flow in a web application hosted on a server, comprising:

saving HTTP transactions executed on the server while interacting with the web application;

selecting a number of the saved HTTP transactions; and

sending a request to the server to re-execute the selected number of the saved HTTP transactions in a predetermined sequence.

13_9. ] The method of claim 12, wherein the predetermined sequence corresponds to the order in which the HTTP transactions were originally executed on the server.

14_9. ] The method of claim 12, wherein the saved HTTP transactions each comprise an HTTP request, and sending the request to the server comprises sending the HTTP requests for the selected number of the saved HTTP transactions to the server according to the predetermined sequence.

15_9. ] The method of claim 14, wherein each HTTP request has a timeout period within which it should be completely processed by the server.

16_9. ] The method of claim 15, further comprising displaying a notification if the timeout period is exceeded before the HTTP request is completely processed.

17_9. ] The method of claim 14, further comprising displaying an output of the server executing each HTTP transaction in the predetermined sequence.

18_9. ] The method of claim 14, further comprising displaying an output of the server after executing the last HTTP transaction in the predetermined sequence.

19_9. ] The method of claim 12, further comprising collecting data passed between components of the web application before and after each HTTP transaction is executed.

20_9. ] The method of claim 19, wherein the collected data comprises one selected from the group consisting of data contained in an HTTP request associated with each HTTP transaction, data contained in an HTTP response generated after processing of the HTTP request, properties of dynamic component invoked by the server to process the HTTP request, data contained in a cookie associated with the HTTP request, data contained in a cookie associated with the HTTP response, and combinations thereof.

21_9. ] A mechanism for monitoring data flow in a web application hosted on a server, comprising:

a directory for storing HTTP transactions executed on the server while interacting with the web application; and

a display through which a request can be sent to the server to re-execute a selected number of the HTTP transactions in the directory in a predetermined sequence.

22_9. ] The mechanism of claim 21, wherein the predetermined sequence corresponds to the order in which the selected number of the HTTP transactions were originally executed on the server.

23_9. ] The mechanism of claim 21, further comprising an editor through which data associated with the selected number of the HTTP transactions can be edited prior to sending the request to the server.

24_9. ] The mechanism of claim 23, further comprising a request player which reconstructs the request using the edited data prior to the server processing the request.

25_9. ] The mechanism of claim 24, wherein the request comprises individual HTTP requests, each of which corresponds to one of the selected number of HTTP transactions.

26_9. ] The mechanism of claim 21, further comprising a data collector which selectively intercepts the HTTP transactions executed on the server in order to collect data passed between components of the web application.

27_9. ] The mechanism of claim 26, further comprising means for storing the data collected by the data collector in the directory.

28_9. ] The mechanism of claim 26, further comprising means for notifying the display of data collected by the data collector.

29_9. ] A system for testing and debugging a web application, comprising:

a server hosting the web application;

a directory for storing HTTP transactions executed on the server while interacting with the web application; and

a client through which a request can be sent to the server to re-execute a selected number of the HTTP transactions in the directory in a predetermined sequence.

30_9. ] The system of claim 29, further comprising a data collector running on the server which selectively intercepts HTTP transactions executed on the server in order to collect data passed between components of the web application.

31_9. ] The system of claim 30, further comprising an application which starts the server in a separate process and through which the client can be started.

32_9. ] The system of claim 31, where the application is an integrated development environment.

33_9. ] The system of claim 32, wherein the application includes an HTTP server.

34_9. ] The system of claim 33, wherein the HTTP server includes a mechanism for receiving data from the data collector and notifying the client of the collected data.

35_9. ] The system of claim 29, further comprising a request player which reconstructs the request using data associated with the HTTP transactions prior to the server processing the request.

36_9. ] The system of claim 35, further comprising an editor through which data associated with the selected number of the HTTP transactions can be edited prior to sending the request to the server.

37_9. ] The system of claim 36, wherein the client includes an action for invoking the editor.

38_9. ] The system of claim 29, wherein the client includes a controller which manages access to the directory.