HTTP transaction monitor

• US 7,016,953 B2
• Filed: 12/06/2000
• Issued: 03/21/2006
• Est. Priority Date: 10/03/2000
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Lemon, Ana H. von Klopp
• Primary Examiner(s): Lim, Krisna
• Assistant Examiner(s): BARQADLE, YASIN M
• Application Number:
  US09/730,686
• Publication Number:
  US 20020103896A1
• Time in Patent Office: 1,931 Days
• Field of Search: 709/203, 709223-225, 709216-219, 715/513
• US Class Current: 709/224
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• 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 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An apparatus for monitoring data flow in a web application includes a data collector which collects data about transactions on a server that hosts components of the web application. The transactions on the server are initiated through an HTTP request from a client. The apparatus further includes a graphical display which displays the collected data.

Claims

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

a data collector configured to;

collect information about a HTTP request when a first hook is triggered in the server while the server is servicing the HTTP request and to return control to the server once information about the HTTP request has been collected, and

collect information about a HTTP response generated by the server in response to the HTTP request when a second hook in the server is triggered while servicing the HTTP request and to return control to the server once information about the HTTP response has been collected; and

a graphical display which displays the information about the HTTP request and information about the HTTP response

wherein each of the first hook and the second hook is embedded in at least one selected from the group consisting of the server and a server plug-in application configured to execute on the server,

wherein the server is configured to process the HTTP request to generate the HTTP response, and

wherein the first hook is triggered in at least one selected from the group consisting of the server and the server plug-in application prior to generating the HTTP response and the second hook is triggered in at least one selected from the group consisting of the server and the server plug-in after generating the HTTP response.

2. The system of claim 1, wherein the information about the HTTP request and the information about the HTTP response further comprises one selected from the group consisting of data contained in the HTTP request, data contained in the HTTP response, properties of a 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.

3. The system of claim 2, wherein the information about the HTTP request further comprises properties of a HTTP session associated with the HTTP request.

4. The system of claim 1, further comprising a directory for storing the information about the HTTP request and the information about the HTTP response on a per-transaction basis.

5. The system of claim 4, further comprising means for retrieving the information about the HTTP request and the information about the HTTP response stored in the directory and for updating the graphical display with the information about the HTTP request and the information about the HTTP response.

6. The system of claim 5, further comprising means for deleting the information about the HTTP request and the information about the HTTP response associated with a selected HTTP request from the directory.

7. A system for monitoring data flow in a web application, comprising:

a server which hosts the web application servicing a HTTP request from a client, wherein servicing the HTTP request triggers a first hook and a second hook, wherein each of the first hook and the second hook is embedded in at least one selected from the group consisting of the server and a server plug-in application configured to execute on the server, and wherein servicing the HTTP request comprises processing the HTTP request by the server to generate a HTTP response;

a data collector configured to;

collect information about the HTTP request when the first hook is triggered and to return control to the server once the information about the HTTP request has been collected, and

collect information about the HTTP response generated by the server in response to the HTTP request when a second hook is triggered and to return control to the server once the information about the HTTP response has been collected; and

an application that provides a graphical display for displaying the information about the HTTP request and the information about the HTTP response,

wherein the first hook is triggered in at least one selected from the group consisting of the server and the server plug-in application prior to generating the HTTP response and the second hook is triggered in at least one selected from the group consisting of the server and the server plug-in after generating the HTTP response.

8. The system of claim 7, wherein the information about the HTTP request and the information about the HTTP response further comprises one selected from the group consisting of data contained in the HTTP request, data contained in the HTTP response, properties of a dynamic component invoked by the server to process the HIP request, data contained in a cookie associated with the HTTP request, data contained in a cookie associated with the HTTP response, and combinations thereof.

9. The system of claim 8, wherein the information about the HTTP request further comprises properties of a HTTP session associated with the HTTP request.

10. A system for test-running and debugging a web application, comprising:

a server which hosts the web application servicing a HTTP request from a client, wherein servicing the HTTP request triggers a first hook and a second hook, wherein each of the first hook and the second hook are embedded in at least one selected from the group consisting of the server and a server plug-in application configured to execute on the server, and wherein servicing the HTTP request comprises processing the HTTP request by the server to generate a HTTP response;

the client configured to send the HTTP requesting to the server;

a data collector configured to;

collect information about the HTTP request when the first hook is triggered and to return control to the server once the information about the HTTP request has been collected, and

collect information about the HTTP response generated by the server in response to the HTTP request when a second hook is triggered and to return control to the server once the information about the HTTP response has been collected; and

an application that provides a graphical display for displaying the information about the HTTP request and the information about the HTTP response,

wherein the first hook is triggered in at least one selected from the group consisting of the server and the server plug-in application prior to generating the HTTP response and the second hook is triggered in at least one selected from the group consisting of the server and the server plug-in after generating the HTTP response.

11. The system of claim 10, wherein the information about the HTTP request and the information about the HTTP response further comprises one selected from the group consisting of data contained in the HTTP request, data contained in the HTTP response, properties of a 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. The system of claim 11, further comprising an integrated development environment which starts the server in a separate process.

13. The system of claim 12, wherein the graphical display is accessible from within the integrated development environment.

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

15. The system of claim 12, wherein the integrated development environment comprises a mechanism that listens for requests from external processes and updates the graphical display in response to a notification from the data collector.

16. The system of claim 11, further comprising a directory for storing the information about the HTTP request and the information about the HTTP response on a per-transaction basis.

17. The system of claim 16, further comprising a mechanism running as part of the client which updates the graphical display with the information about the HTTP request and the information about the HTTP response stored in the directory.

18. A system for test-running and debugging a web application, comprising:

a server which hosts the web application servicing a HTTP request from a client, wherein servicing the HTTP request triggers a first hook and a second hook, wherein each of the first hook and the second hook are embedded in at least one selected from the group consisting of the server and a server plug-in application configured to execute on the server, and wherein servicing the HTTP request comprises processing the HTTP request by the server to generate a HTTP response;

an integrated development environment which starts the server in a separate process;

the client configured to send the HTTP request to the server;

a data collector configured to;

collect information about the HTTP request when the first hook is triggered and to return control to the server once information about the HTTP request has been collected, and

collect information about the HTTP response generated by the server in response to the HTTP request when a second hook is triggered and to return control to the server once information about the HTTP response has been collected; and

an application that provides a graphical display for displaying the information about the HTTP request and information about the HTTP response,

wherein the first hook is triggered in at least one selected from the group consisting of the server and the server plug-in application prior to generating the HTTP response and the second hook is triggered in at least one selected from the group consisting of the server and the server plug-in after generating the HTTP response.

19. The system of claim 18, wherein the information about the HTTP request and information about the HTTP response further comprises one selected from the group consisting of data contained in the HTTP request, data contained in the HTTP response, properties of a 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.

20. The system of claim 19, wherein the information about the HTTP request further comprises properties of a HTTP session associated with the HTTP request.

21. A method for monitoring data flow in a web application, comprising:

sending a HTTP request to a server hosting the web application, wherein the HTTP request is associated with a transaction;

receiving the HTTP request by the server;

triggering a first hook in the server prior to servicing the HTTP request by the server and after receiving the HTTP request, whereby triggering the first hook transfers control to a data collector, wherein the data collector is configured to collect information about the HTTP request when the first hook is triggered and to return control to the server once information about the HTTP request has been collected;

servicing the HTTP request by the server to generate a HTTP response after control is returned to the server;

triggering a second hook in the server after the HTTP response has been generated, whereby triggering the second hook transfers control to a data collector, wherein the data collector is configured to collect information about the HTTP response when the second hook is triggered and to return control to the server once information about the HTTP response has been collected; and

forwarding the HTTP response to a client that sent the HTTP request after control is returned to the server,

wherein each of the first hook and the second hook are embedded in at least one selected from the group consisting of the server and a server plug-in application configured to execute on the server, wherein the server is configured to process the HTTP request to generate the HTTP response, and wherein the first hook is triggered in at least one selected from the group consisting of the server and the server plug-in application prior to generating the HTTP response and the second hook is triggered in at least one selected from the group consisting of the server and the server plug-in after generating the HTTP response.

22. The method of claim 21, wherein the collected data further comprises one selected from the group consisting of data contained in the HTTP request, data contained in the HTTP response, properties of a 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.

23. The method of claim 22, wherein the collected data further comprises properties of a HTTP session associated with the HTTP request.

24. The method of claim 21, wherein the HTTP request is intercepted prior to the server making any modifications to the HTTP request.

25. The method of claim 24, wherein the HTTP response is intercepted prior to the server making any modifications to the HTTP response.