WO2003005202A1 - Method and system for providing a virtual user interface - Google Patents

Method and system for providing a virtual user interface Download PDF

Info

Publication number
WO2003005202A1
WO2003005202A1 PCT/US2002/021439 US0221439W WO03005202A1 WO 2003005202 A1 WO2003005202 A1 WO 2003005202A1 US 0221439 W US0221439 W US 0221439W WO 03005202 A1 WO03005202 A1 WO 03005202A1
Authority
WO
WIPO (PCT)
Prior art keywords
control flow
alert
server
module
recording
Prior art date
Application number
PCT/US2002/021439
Other languages
French (fr)
Inventor
Deb D. GANGULY
Prakash Khot
Jayant Pandit
Rutvik Doshi
Original Assignee
Computer Associates Think, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Computer Associates Think, Inc. filed Critical Computer Associates Think, Inc.
Priority to EP02746904A priority Critical patent/EP1405190A4/en
Priority to JP2003511104A priority patent/JP2004535019A/en
Priority to KR10-2004-7000187A priority patent/KR20040019045A/en
Priority to BR0210885-2A priority patent/BR0210885A/en
Priority to CA002452747A priority patent/CA2452747A1/en
Priority to IL15969302A priority patent/IL159693A0/en
Publication of WO2003005202A1 publication Critical patent/WO2003005202A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3414—Workload generation, e.g. scripts, playback
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present application generally relates to information and data management systems and methods.
  • the present application more specifically relates to Information Techonology monitoring.
  • Many information and service providers enable users to access information and services via a client-server architecture, for example using web-based applications written in languages such as Java.
  • Many of the functions performed by such applications are routine functions that a user may periodically request, such as checking a balance of a checking account or making a minimum payment to a credit card account, for example.
  • a method for monitoring interaction associated with a client-server application includes configuring recording, playback and analysis parameters.
  • the method also includes recording control flow and server responses associated with the application.
  • the method further includes replaying the control flow, and comparing responses received from the server to the replayed control flow to recorded server responses to determine whether an alert condition exists.
  • the alert condition is processed according to the configured analysis parameters.
  • a system for monitoring interaction associated with an application includes a configuration module for defining and storing configuration data.
  • the system also includes a recording module for monitoring client-server interaction of the application.
  • the recording module is further operative to store control flow data representing the monitored client-server interaction.
  • the system further includes a playback module.
  • the playback module is operative to replay client portions of the stored control flow data and to analyze server responses to determine and report an alert.
  • the system includes a control module for controlling the configuration module, the recording module and the playback module.
  • Computer-readable storage media are also disclosed which include processing instructions for implementing certain disclosed methods.
  • Figure 1 is a schematic block diagram of an example interaction recording system
  • Figure 2 is a flow chart that illustrates an example methodology for employing the interaction recording system of Figure 1;
  • Figure 3 is an initial window of an exemplary embodiment the present application;
  • Figure 4 is a "New Instance" window of the exemplary embodiment the present application.
  • Figure 5 is a control flow recording window of the exemplary embodiment the present application
  • Figures 6A-6G are various windows presented according to a step-adding wizard for the exemplary embodiment the present application.
  • Figures 7A-7D are various windows enabling method validation configuration for the exemplary embodiment the present application.
  • the present application augments traditional Information Technology management solutions by providing the ability to record, replay and analyze interaction between a user and an application.
  • interaction may represent business logic occurring within a client-server application.
  • client-server architecture other architectures may be utilized, such as a peer to peer architecture, for example.
  • the present application describes an exemplary client-server interaction recorder/player ("Interaction Recorder") which employs a user-friendly wizard-based interface to create a virtual user.
  • the exemplary Interaction Recorder uses the virtual user to simulate a human user interacting with Enterprise Java Beans ("EJB's").
  • EJB's Enterprise Java Beans
  • One or more virtual users then interact periodically with an associated client-server application to analyze whether the interaction or business logic is performing according to specification.
  • the analysis is described as being performed at 3 levels: application response time, returned values, and exceptions, but analysis at other levels are possible.
  • the example interaction recording system 100 for monitoring, recording replaying and analyzing interactions between application client 110 and application server 115.
  • the example interaction recording system 100 enables an end user or application to capture and replay interaction of an EJB client with an EJB server.
  • the captured interaction or control flow is stored as data in store 120.
  • the recording module 125 monitors and records the data provided by the application client 110 as well as data returned by application server 115 as control flow data.
  • Playback module 130 enables an end user, application or intelligent agent to replay a control flow using the stored control flow data associated with the application client 110.
  • the responses from application server 115 are compared to the stored control flow data representing the responses originally provided by application server 115. If the stored responses are not consistent with the responses provided during the replayed control flow, playback module 130 reports an alert.
  • configuration module 135 enables the end user to customize the operation of the playback module 130.
  • Configuration parameters determined by the end user are stored as configuration data in store 140 and include, for example, alert ranges and notification messae contents.
  • Control module 145 enables an intelligent agent, end user or application to interact with the system 100 and controls the recording, playback and configuration modules.
  • a typical user interface built using servlets, may use such methods to provide an ATM-like functionality through a standard web browser.
  • a customer may deposit money, withdraw money and at times check the balance of the user's account.
  • the recording module 125 can be used to record this interaction either through the web browser or directly with the EJBs.
  • Intelligent agents may invoke the playback module 130 to replay the recorded control flow data after a specific time interval.
  • the playback module 130 may determine that the balance check method is returning an unexpected value. This nonconformity could result in an immediate alert message being sent to the administrator who can then check the server and or the database to see why the error occurred and take steps to correct the problem.
  • control module employs a simple user interface that provides wizard-based paradigms to capture the client interaction and server responses.
  • the interface enables the end user to direct the recording of user interactions and the replaying of a recorded control flow from store 120.
  • the interface may simulate the user's actions by repeating the control flow steps in the exact sequence originally monitored.
  • the interface may further report the results of the server's responses and the originally recorded data.
  • Figure 2 illustrates one example methodology 200 that may be employed using the interaction recording system 100 of Figure 1.
  • the end user configures the interaction recording system 100.
  • Configuring the interaction recording system 100 may include, for example, defining a playback interval, defining alert conditions, and defining actions for responding to detected alert conditions.
  • the recording module 125 is employed at block 215 to monitor and record the control flow of a client-server application session.
  • the monitored control flow includes the interaction between the client 110 and the server 115, and is stored as control flow data in store 110.
  • the playback module 130 is employed at block 220 to replay the control flow of the recorded session.
  • the playback module 130 compares the responses to the replayed control data received from application server 115 to the responses stored in control flow data store 120 to determine at block 230 whether an alert condition has occurred. If an alert condition is detected, the alert condition is processed at block 235, otherwise the methodology ends.
  • Figure 3 illustrates an initial window 300 which enables the user to select expert agents, hi order to begin recording a new control flow, the user selects "Instances" from the "WebLogic Business Logic Expert Agent” tree. Alternatively, the user may select "Instances" from the "Tools” menu. Selection of "Instances” enables the user to add, delete or edit stored control flow instances. Selecting "Add” enables the user to begin recording a new control flow.
  • Figure 4 depicts a "New Instance" window 400 which enables the user to define certain characteristics of the control flow to be recorded.
  • the user may define the name under which the control flow will be stored for future reference.
  • the user may also provide a textual description of the control flow, hi the illustrated embodiment, the server name may be selected from the WebLogic EJB servers previously configured in a database under the WebLogic Server Expert Agent.
  • the server connection parameters, such as the URL, user name, and password are populated based on the WebLogic Server Expert Agent.
  • the user may select "Launch Recorder” to begin recording the control flow of an application session.
  • the selection of "Launch Recorder” directs recording module 125 to establish a connection with the WebLogic EJB server and display the control flow recording window 500 depicted in
  • the example control flow recording window employs a familiar document processing interface design augmented with additional EJB-specific options.
  • the interface has the following menu options :
  • This option prompts the recording module to open a new control flow.
  • This option prompts user for the server connection parameters. Record: This option allows user to add new steps to the currently active control flow. Start Recording: This option initializes the control flow recording and is used to begin recording. Add new step: This option starts the wizard that adds a new step at the end of the active control flow. Play: This option is used to access functions that play all or part of a prerecorded control flow. Play Recording: This option plays the currently active control flow from beginning to end. Play Step: This option plays only the next step in the currently active control flow.
  • Each recorded control flow may be made up of one or more individual steps, or portions of a session.
  • FIGs 6A-6G there are illustrated the windows presented by the recording module when adding a single step to a control flow.
  • the successive windows are presented in a "wizard" format that assists the user to record single step of a control flow.
  • the user enters data and selects "Next" button 614 in order to proceed, "Back" button 613 to edit previously entered selections or "Cancel” button 615 to terminate the wizard.
  • Figure 6 A depicts a window 610 that allows the user to define a name 611 associated with the step to be recorded. The user may also provide a textual description 612 of the step.
  • Figure 6B depicts a window 620 that presents user with the available EJB's in the server associated with the control flow. The user may select an unused EJB from selection window 621 or any EJB aheady in use in the control flow from selection window 622. Any EJB's aheady in use in the control flow are presented as 'Cached Beans' in selection window 622.
  • Figure 6C depicts a window 630 that enables the user to select the EJB method to be
  • Figure 6D depicts a window 640 that enables the user to define which parameters from window 645 are to be used by the create method, if any.
  • the Java type of each parameter is displayed for informational purposes.
  • Figure 6E depicts a window 650 that enables the user to select a method to execute from drop-down selection menu 655.
  • Figure 6F depicts a window 640 that enables the user to assign values to the parameters defined in window 640. The values are assigned using input window 666.
  • Figure 6G depicts a window 670 that displays the execution results of the method previously defined by the user using windows 620, 630, 640 650 and 660. Window 670 also enables the user to define validation tests for the method results. The user selects "Validate" button 675 to define the validation tests, "Finish” button 677 to complete the addition of the step to the control flow, "Back" button 613 to edit previously entered selections or "Cancel” button 615 to abort the addition of the step.
  • the configuration module provides a series of windows to enable the user to define how the method results are validated. These windows enable the user to define validation based on three factors: 1) the actual return value of the method, if any; 2) the time taken to execute the method and 3) the exception raised by the method, if any.
  • the validation can include a number of tests for each of the three factors.
  • Figure 7A depicts validation window 700 having the "Result" tab 707 selected, enabling the user to define the validation of the result of the method.
  • the example system supports return values of various types, including for example, strings, integer numbers and double integer numbers.
  • strings When validating strings, the system compares a pre-defined pattern against a returned string value.
  • validating numbers the system compares a pre-defined range of values against a returned numeric value.
  • Window 700 illustrated the validation definition for a double integer numeric value.
  • a lower and upper limit to the overall validation range may be defined, as well as five categories within the range. Each category may be configured to provide a different alert message.
  • Each category has an associated "Details" button, such as button 702, which may be selected to define certain cause, meaning, action and notification parameters associated with the category. When the results fall within a particular category range, the associated parameters determine what notification, if any, to provide.
  • Figure 7B depicts an example "Critical Details" window 720 which is presented if the user selects button 702 for the "Critical" range from window 700.
  • the playback module refers to these parameters to determine any action to take. If the notification parameter 722 is selected, an alert notification will be delivered to a notification recipient's e-mail address or pager.
  • the notification path is pre-defined and configured using the configuration module.
  • the cause 724, meaning 726 and action 728 of the critical alert is incorporated into the alert message.
  • Figure 7C depicts validation window 700 having the "Performance" tab 708 selected, enabling the user to define the validation of the performance of the method.
  • the execution time observed during recording may be used as a benchmark to define an alarming level of performance. Specifically, if the execution of the method takes unexpectedly long, the administrators may need to be notified.
  • the "Performance" tab 708 enables the user to define different levels of performance.
  • the system compares the access time for processing a method with the limits defined by the user using the "Performance” tab 708 of window 700.
  • the "Performance” tab 708 enables the user to define an upper and lower limit to the range of access times, as well as five categories within the range.
  • Each category has an associated "Details” button which enables the user to define any action that may be desired for the category.
  • Figure 7D depicts validation window 700 having the "Exception" tab 709 selected, enabling the user to define the validation in the event an exception occurs during the processing of the method.
  • exceptions indicate errors.
  • an exception may be expected.
  • the exception validation can be used configure the status of the control flow based on the exception message.
  • the configuration is similar to the string return value validation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Software Systems (AREA)
  • Debugging And Monitoring (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
  • General Factory Administration (AREA)

Abstract

A method is provided for monitoring interaction associated with an application. The method includes configuring recording, playback and analysis parameters, and recording control flow and server responses associated with the application (125). The method also includes replaying the control flow and comparing server responses to the replayed control flow to recorded server responses to determine whether an alert condition exists (130). The method further includes reporting the alert condition. Systems and articles of manufacture are also provided to implement the described methods.

Description

METHOD AND SYSTEM FOR PROVIDING A VIRTUAL USER INTERFACE
Cross-Reference to Related Applications
This application claims priority to U.S. Provisional Application Serial Number 60/303,448, filed July 6, 2001, the entirety of which is hereby incorporated by reference.
Technical Field
The present application generally relates to information and data management systems and methods. The present application more specifically relates to Information Techonology monitoring.
Background
Many information and service providers enable users to access information and services via a client-server architecture, for example using web-based applications written in languages such as Java. Many of the functions performed by such applications are routine functions that a user may periodically request, such as checking a balance of a checking account or making a minimum payment to a credit card account, for example.
Presently, each time that a user wishes to perform one of these routine functions, the user must request the function to be performed and provide all of the input for the function to be performed. This is true even in cases where the input is standardized and does not vary from request to request.
Repeatedly requesting the same information from the user to accomplish a previously requested function is an inefficient use of the user's time. Some web-based applications have addressed this inefficiency by providing a capability to store user preferences. Such functionality, however, is only available sporadically, for specific web applications, namely, those applications which have been designed to include a feature of storing and recalling user preferences.
Consequently, a need exists for a system and method for reducing the amount of time and effort a user must provide to submit routine, periodic requests for information or services. Further, a need exists for a solution which is compatible with existing client-server applications. Summary
The following presents a simplified summary of methods, systems, and computer readable media associated with recording and replaying interaction associated with a client- server application, thereby providing a virtual user interface. This summary is not an extensive overview and is not intended to identify key or critical elements of the methods, systems, and/or media or to delineate the scope of the methods, systems, and media. It conceptually identifies the methods, systems, and media in a simplified form as a prelude to the more detailed description that is presented later.
This disclosure provides methods and systems for monitoring interaction associated with a client server application in a computer processing environment. According to one aspect of the disclosure, a method for monitoring interaction associated with a client-server application is disclosed. The method includes configuring recording, playback and analysis parameters. The method also includes recording control flow and server responses associated with the application. The method further includes replaying the control flow, and comparing responses received from the server to the replayed control flow to recorded server responses to determine whether an alert condition exists. The alert condition is processed according to the configured analysis parameters.
A system for monitoring interaction associated with an application is also disclosed. In one embodiment, the system includes a configuration module for defining and storing configuration data. The system also includes a recording module for monitoring client-server interaction of the application. The recording module is further operative to store control flow data representing the monitored client-server interaction. The system further includes a playback module. The playback module is operative to replay client portions of the stored control flow data and to analyze server responses to determine and report an alert. In addition, the system includes a control module for controlling the configuration module, the recording module and the playback module.
Computer-readable storage media are also disclosed which include processing instructions for implementing certain disclosed methods.
Certain illustrative aspects of the methods, systems, and computer readable media are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the methods, systems, and media may be employed and thus the examples are intended to include such aspects and equivalents. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.
Brief Description of the Drawings
For a more complete understanding of the present methods and systems, reference is now made to the following description taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:
Figure 1 is a schematic block diagram of an example interaction recording system;
Figure 2 is a flow chart that illustrates an example methodology for employing the interaction recording system of Figure 1; Figure 3 is an initial window of an exemplary embodiment the present application;
Figure 4 is a "New Instance" window of the exemplary embodiment the present application;
Figure 5 is a control flow recording window of the exemplary embodiment the present application; Figures 6A-6G are various windows presented according to a step-adding wizard for the exemplary embodiment the present application; and
Figures 7A-7D are various windows enabling method validation configuration for the exemplary embodiment the present application.
Detailed Description
Example methods, systems, and computer readable media are now described with reference to the drawings, where like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to facilitate thoroughly understanding the methods and systems. It may be evident, however, that the methods and systems can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to simplify the description.
The present application augments traditional Information Technology management solutions by providing the ability to record, replay and analyze interaction between a user and an application. In one embodiment, such interaction may represent business logic occurring within a client-server application. Although the exemplary system is described with respect to a client-server architecture, other architectures may be utilized, such as a peer to peer architecture, for example.
The present application describes an exemplary client-server interaction recorder/player ("Interaction Recorder") which employs a user-friendly wizard-based interface to create a virtual user. The exemplary Interaction Recorder uses the virtual user to simulate a human user interacting with Enterprise Java Beans ("EJB's"). One or more virtual users then interact periodically with an associated client-server application to analyze whether the interaction or business logic is performing according to specification. The analysis is described as being performed at 3 levels: application response time, returned values, and exceptions, but analysis at other levels are possible.
Referring to Figure 1, there is illustrated an example interaction recording system 100 for monitoring, recording replaying and analyzing interactions between application client 110 and application server 115. The example interaction recording system 100 enables an end user or application to capture and replay interaction of an EJB client with an EJB server. The captured interaction or control flow is stored as data in store 120. The recording module 125 monitors and records the data provided by the application client 110 as well as data returned by application server 115 as control flow data. Playback module 130 enables an end user, application or intelligent agent to replay a control flow using the stored control flow data associated with the application client 110. During the process of replaying of a control flow, the responses from application server 115 are compared to the stored control flow data representing the responses originally provided by application server 115. If the stored responses are not consistent with the responses provided during the replayed control flow, playback module 130 reports an alert.
While providing other functionality, configuration module 135 enables the end user to customize the operation of the playback module 130. Configuration parameters determined by the end user are stored as configuration data in store 140 and include, for example, alert ranges and notification messae contents. Control module 145 enables an intelligent agent, end user or application to interact with the system 100 and controls the recording, playback and configuration modules.
To illustrate the utility of interaction recording system 100, consider an exemplary bank account EJB application that provides deposit, withdraw and check balance methods. A typical user interface, built using servlets, may use such methods to provide an ATM-like functionality through a standard web browser. Using the exemplary EJB application, a customer may deposit money, withdraw money and at times check the balance of the user's account. The recording module 125 can be used to record this interaction either through the web browser or directly with the EJBs.
Intelligent agents may invoke the playback module 130 to replay the recorded control flow data after a specific time interval. During playback, the playback module 130 may determine that the balance check method is returning an unexpected value. This nonconformity could result in an immediate alert message being sent to the administrator who can then check the server and or the database to see why the error occurred and take steps to correct the problem.
In one embodiment, the control module employs a simple user interface that provides wizard-based paradigms to capture the client interaction and server responses. The interface enables the end user to direct the recording of user interactions and the replaying of a recorded control flow from store 120. The interface may simulate the user's actions by repeating the control flow steps in the exact sequence originally monitored. The interface may further report the results of the server's responses and the originally recorded data.
Figure 2 illustrates one example methodology 200 that may be employed using the interaction recording system 100 of Figure 1. At block 210, the end user configures the interaction recording system 100. Configuring the interaction recording system 100 may include, for example, defining a playback interval, defining alert conditions, and defining actions for responding to detected alert conditions.
The recording module 125 is employed at block 215 to monitor and record the control flow of a client-server application session. The monitored control flow includes the interaction between the client 110 and the server 115, and is stored as control flow data in store 110. At a predetermined playback interval, the playback module 130 is employed at block 220 to replay the control flow of the recorded session. The playback module 130 compares the responses to the replayed control data received from application server 115 to the responses stored in control flow data store 120 to determine at block 230 whether an alert condition has occurred. If an alert condition is detected, the alert condition is processed at block 235, otherwise the methodology ends.
Referring now to Figures 3-7D, there are illustrated various example windows which may be presented to the user by the interaction recording system 100 to effect the methods and operate the systems of the present application. The exemplary system is an application designed to be executed on the BEA WebLogic Platform™ provided by BEA Systems, Inc. Figure 3 illustrates an initial window 300 which enables the user to select expert agents, hi order to begin recording a new control flow, the user selects "Instances" from the "WebLogic Business Logic Expert Agent" tree. Alternatively, the user may select "Instances" from the "Tools" menu. Selection of "Instances" enables the user to add, delete or edit stored control flow instances. Selecting "Add" enables the user to begin recording a new control flow. Figure 4 depicts a "New Instance" window 400 which enables the user to define certain characteristics of the control flow to be recorded. Specifically, the user may define the name under which the control flow will be stored for future reference. The user may also provide a textual description of the control flow, hi the illustrated embodiment, the server name may be selected from the WebLogic EJB servers previously configured in a database under the WebLogic Server Expert Agent. The server connection parameters, such as the URL, user name, and password are populated based on the WebLogic Server Expert Agent.
Once the characteristics of the new control flow have been defined, the user may select "Launch Recorder" to begin recording the control flow of an application session. The selection of "Launch Recorder" directs recording module 125 to establish a connection with the WebLogic EJB server and display the control flow recording window 500 depicted in
Figure 5.
The example control flow recording window employs a familiar document processing interface design augmented with additional EJB-specific options. The interface has the following menu options :
File: This option is used to access file handling functions.
New: This option prompts the recording module to open a new control flow.
If at the time another control flow is active, the user is prompted if the control flow should be saved or not. Open: This option prompts the playback module to open a prerecorded control flow. Save: This option saves the currently active control flow under its current name. Save as: This option saves the currently active control flow under a different name.
Exit: This option closes the interaction recording system.
Connect: This option is used to connect to the WebLogic EJB server.
Connect to server: This option prompts user for the server connection parameters. Record: This option allows user to add new steps to the currently active control flow. Start Recording: This option initializes the control flow recording and is used to begin recording. Add new step: This option starts the wizard that adds a new step at the end of the active control flow. Play: This option is used to access functions that play all or part of a prerecorded control flow. Play Recording: This option plays the currently active control flow from beginning to end. Play Step: This option plays only the next step in the currently active control flow.
Each recorded control flow may be made up of one or more individual steps, or portions of a session. Referring now to Figures 6A-6G, there are illustrated the windows presented by the recording module when adding a single step to a control flow. The successive windows are presented in a "wizard" format that assists the user to record single step of a control flow. In each window, the user enters data and selects "Next" button 614 in order to proceed, "Back" button 613 to edit previously entered selections or "Cancel" button 615 to terminate the wizard.
Figure 6 A depicts a window 610 that allows the user to define a name 611 associated with the step to be recorded. The user may also provide a textual description 612 of the step. Figure 6B depicts a window 620 that presents user with the available EJB's in the server associated with the control flow. The user may select an unused EJB from selection window 621 or any EJB aheady in use in the control flow from selection window 622. Any EJB's aheady in use in the control flow are presented as 'Cached Beans' in selection window 622. Figure 6C depicts a window 630 that enables the user to select the EJB method to be
' used to create and/or find Java Bean instances. The user selects an EJB method from selection window 631.
Figure 6D depicts a window 640 that enables the user to define which parameters from window 645 are to be used by the create method, if any. The Java type of each parameter is displayed for informational purposes.
Figure 6E depicts a window 650 that enables the user to select a method to execute from drop-down selection menu 655.
Figure 6F depicts a window 640 that enables the user to assign values to the parameters defined in window 640. The values are assigned using input window 666. Figure 6G depicts a window 670 that displays the execution results of the method previously defined by the user using windows 620, 630, 640 650 and 660. Window 670 also enables the user to define validation tests for the method results. The user selects "Validate..." button 675 to define the validation tests, "Finish" button 677 to complete the addition of the step to the control flow, "Back" button 613 to edit previously entered selections or "Cancel" button 615 to abort the addition of the step.
Referring now to Figures 7A-7D, if the user elects to define validation tests, the configuration module provides a series of windows to enable the user to define how the method results are validated. These windows enable the user to define validation based on three factors: 1) the actual return value of the method, if any; 2) the time taken to execute the method and 3) the exception raised by the method, if any. The validation can include a number of tests for each of the three factors.
Figure 7A depicts validation window 700 having the "Result" tab 707 selected, enabling the user to define the validation of the result of the method. The example system supports return values of various types, including for example, strings, integer numbers and double integer numbers. When validating strings, the system compares a pre-defined pattern against a returned string value. When validating numbers, the system compares a pre-defined range of values against a returned numeric value. Window 700 illustrated the validation definition for a double integer numeric value.
In the illustrated example, a lower and upper limit to the overall validation range may be defined, as well as five categories within the range. Each category may be configured to provide a different alert message.
Each category has an associated "Details" button, such as button 702, which may be selected to define certain cause, meaning, action and notification parameters associated with the category. When the results fall within a particular category range, the associated parameters determine what notification, if any, to provide.
Figure 7B depicts an example "Critical Details" window 720 which is presented if the user selects button 702 for the "Critical" range from window 700. When the returned result of a method parameter falls within the pre-defined critical range, the playback module refers to these parameters to determine any action to take. If the notification parameter 722 is selected, an alert notification will be delivered to a notification recipient's e-mail address or pager. The notification path is pre-defined and configured using the configuration module. The cause 724, meaning 726 and action 728 of the critical alert is incorporated into the alert message.
Figure 7C depicts validation window 700 having the "Performance" tab 708 selected, enabling the user to define the validation of the performance of the method. The execution time observed during recording may be used as a benchmark to define an alarming level of performance. Specifically, if the execution of the method takes unexpectedly long, the administrators may need to be notified. The "Performance" tab 708 enables the user to define different levels of performance.
When validating performance, the system compares the access time for processing a method with the limits defined by the user using the "Performance" tab 708 of window 700. Like the "Result" tab 707, the "Performance" tab 708 enables the user to define an upper and lower limit to the range of access times, as well as five categories within the range. Each category has an associated "Details" button which enables the user to define any action that may be desired for the category.
Figure 7D depicts validation window 700 having the "Exception" tab 709 selected, enabling the user to define the validation in the event an exception occurs during the processing of the method. Generally, exceptions indicate errors. Depending on the recording control flow, however, an exception may be expected. The exception validation can be used configure the status of the control flow based on the exception message. The configuration is similar to the string return value validation. What has been described above includes several examples. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the systems, methods, and computer readable media associated with business process policy data. However, one of ordinary skill in the art may recognize that further combinations and permutations are possible. Accordingly, this application is intended to embrace such alterations, modifications, and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is employed in the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as that term is interpreted when employed as a transitional word in a claim.

Claims

What is claimed is:
1. A method for monitoring interaction associated with a client-server application, comprising: configuring recording, playback and analysis parameters; recording control flow and server responses associated with the application; replaying the control flow; comparing server responses to the replayed control flow to recorded server responses to determine whether an alert condition exists; and reporting the alert condition.
2. The method of claim 1, wherein configuring includes determining a playback interval, and replaying is performed at the playback interval.
3. The method of claim 1, wherein configuring includes determining alert conditions.
4. The method of claim 1, wherein configuring includes determining actions to be performed when reporting the alert condition.
5. The method of claim 1, wherein configuring includes determining at least one alert range.
6. The method of claim 1, wherein recording includes adding a step to a pre-recorded control flow.
7. The method of claim 1, wherein reporting includes constructing and transmitting an e- mail message describing the alert.
8. The method of claim 1, wherein reporting includes constructing and transmitting a pager message describing the alert.
9. A system for monitoring interaction associated with an application, comprising: a configuration module for defimng and storing configuration data; a recording module for monitoring client-server interaction of the application and storing control data representing monitored client-server interaction in a store of control flow data; a playback module for replaying client portions of stored control flow data and analyzing server responses to report an alert; and a control module for controlling the configuration module, the recording module and the playback module.
10. The system of claim 9, wherein the configuration module is operative to determine a playback interval, and the playback module is operative to replay the control flow at the playback interval.
11. The system of claim 9, wherein the configuration module is operative to define alert conditions.
12. The system of claim 9, wherein the configuration module is operative to define actions to be performed when reporting the alert condition.
13. The system of claim 9, wherein the configuration module is operative to define at least one alert range.
14. The system of claim 9, wherein the recording module is operative to add a step to a pre-recorded control flow.
15. The system of claim 9, wherein the playback module is operative to construct and transmit an e-mail message describing the alert.
16. The system of claim 9, wherein the playback module is operative to construct and transmit a pager message describing the alert.
17. A system for monitoring interaction associated with an application, comprising: means for defining and storing configuration data; means for monitoring client-server interaction of the application and storing control data representing monitored client-server interaction; means for replaying client portions of stored control flow data; means for and analyzing server responses; and means for reporting an alert based on the server responses.
18. A computer-readable storage medium encoded with processing instructions for monitoring interaction associated with a client-server application, including: computer readable instructions for configuring recording, playback and analysis parameters, including determining a playback interval; computer readable instructions for recording control flow and server responses associated with the application; computer readable instructions for replaying the control flow at the playback interval; computer readable instructions for comparing server responses to the replayed control flow to recorded server responses to determine whether an alert condition exists; and computer readable instructions for reporting the alert condition.
PCT/US2002/021439 2001-07-06 2002-07-08 Method and system for providing a virtual user interface WO2003005202A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP02746904A EP1405190A4 (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface
JP2003511104A JP2004535019A (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface
KR10-2004-7000187A KR20040019045A (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface
BR0210885-2A BR0210885A (en) 2001-07-06 2002-07-08 Method and system for monitoring interaction associated with an application, and, computer readable storage medium
CA002452747A CA2452747A1 (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface
IL15969302A IL159693A0 (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US30344801P 2001-07-06 2001-07-06
US60/303,448 2001-07-06

Publications (1)

Publication Number Publication Date
WO2003005202A1 true WO2003005202A1 (en) 2003-01-16

Family

ID=23172127

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/021439 WO2003005202A1 (en) 2001-07-06 2002-07-08 Method and system for providing a virtual user interface

Country Status (10)

Country Link
US (1) US20030088644A1 (en)
EP (1) EP1405190A4 (en)
JP (1) JP2004535019A (en)
KR (1) KR20040019045A (en)
CN (1) CN1592891A (en)
BR (1) BR0210885A (en)
CA (1) CA2452747A1 (en)
IL (1) IL159693A0 (en)
WO (1) WO2003005202A1 (en)
ZA (1) ZA200400134B (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2868566A1 (en) * 2004-04-01 2005-10-07 Metapages Sarl Method invocation sequence recording process for e.g. object, involves recording and protecting structural information, of invocation graph, representing sequence of invocations and comprising temporal information of invocations
WO2008051855A1 (en) * 2006-10-20 2008-05-02 Oracle International Corporation Database workload capture and replay architecture
US7634512B2 (en) 2006-10-20 2009-12-15 Oracle International Corporation Migrating temporary data of a session
US7890457B2 (en) 2006-10-20 2011-02-15 Oracle International Corporation Transactionally consistent database workload replay
US7890458B2 (en) 2006-10-20 2011-02-15 Oracle International Corporation Capturing database workload while preserving original transactional and concurrency characteristics for replay
US7984015B2 (en) 2006-10-20 2011-07-19 Oracle International Corporation Database workload capture and replay architecture
US8024299B2 (en) 2006-10-20 2011-09-20 Oracle International Corporation Client-driven functionally equivalent database replay
US8418150B2 (en) 2009-04-03 2013-04-09 Oracle International Corporation Estimating impact of configuration changes
US8433680B2 (en) 2008-07-01 2013-04-30 Oracle International Corporation Capturing and restoring database session state
EP2770438A1 (en) * 2013-02-22 2014-08-27 Bull Sas Monitoring of performance tests executed in a computer system
US8863095B2 (en) 2011-05-09 2014-10-14 International Business Machines Corporation Recording and playback of system interactions in different system environments
US8997048B1 (en) 2007-02-14 2015-03-31 Oracle America, Inc. Method and apparatus for profiling a virtual machine
US11556500B2 (en) 2017-09-29 2023-01-17 Oracle International Corporation Session templates

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8250201B2 (en) * 2002-09-09 2012-08-21 International Business Machines Corporation Servlet monitoring tool
CN100565537C (en) * 2006-04-19 2009-12-02 腾讯科技（深圳）有限公司 Network leisure game recording and playback method
JP2009163370A (en) * 2007-12-28 2009-07-23 Noritsu Koki Co Ltd Capture software program and capture device
JP2009163391A (en) * 2007-12-28 2009-07-23 Noritsu Koki Co Ltd Viewer software program and viewer apparatus
JP5039932B2 (en) * 2007-12-28 2012-10-03 Ｎｋワークス株式会社 Capture software program and capture device
JP5003478B2 (en) * 2007-12-28 2012-08-15 Ｎｋワークス株式会社 Capture software program and capture device
JP2009163385A (en) * 2007-12-28 2009-07-23 Noritsu Koki Co Ltd Viewer software program and viewer device
US20120124174A1 (en) * 2010-11-16 2012-05-17 Carefusion 303, Inc. Alert notification service
US9280788B2 (en) * 2012-06-13 2016-03-08 Oracle International Corporation Information retrieval and navigation using a semantic layer
CN105579955A (en) * 2013-09-27 2016-05-11 慧与发展有限责任合伙企业 Application control flow models
US10061687B2 (en) * 2014-06-17 2018-08-28 Paypal, Inc. Self-learning and self-validating declarative testing
US10650621B1 (en) 2016-09-13 2020-05-12 Iocurrents, Inc. Interfacing with a vehicular controller area network
JP6816087B2 (en) * 2018-11-02 2021-01-20 ファナック株式会社 Robot alarm notification system
US10873578B1 (en) 2019-12-09 2020-12-22 Evan Chase Rose Biometric authentication, decentralized learning framework, and adaptive security protocols in distributed terminal network
JP7340585B2 (en) * 2021-12-14 2023-09-07 株式会社日立製作所 Vulnerability management system and vulnerability management method

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303166A (en) * 1992-04-14 1994-04-12 International Business Machines Corporation Method and system for automated network benchmark performance analysis
US5553235A (en) * 1992-10-23 1996-09-03 International Business Machines Corporation System and method for maintaining performance data in a data processing system
US5812780A (en) * 1996-05-24 1998-09-22 Microsoft Corporation Method, system, and product for assessing a server application performance
US6138157A (en) * 1998-10-12 2000-10-24 Freshwater Software, Inc. Method and apparatus for testing web sites
WO2001016753A2 (en) 1999-09-01 2001-03-08 Mercury Interactive Corporation Post-deployment monitoring of server performance
US6360332B1 (en) * 1998-06-22 2002-03-19 Mercury Interactive Corporation Software system and methods for testing the functionality of a transactional server

Family Cites Families (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5153886A (en) * 1990-01-31 1992-10-06 Hewlett Packard Company Visual display signal processing system and method
US5157782A (en) * 1990-01-31 1992-10-20 Hewlett-Packard Company System and method for testing computer hardware and software
US5357452A (en) * 1992-06-30 1994-10-18 Sun Microsystems, Inc. Automatic generation of auto-checking testing functions
US5521844A (en) * 1993-09-10 1996-05-28 Beloit Corporation Printing press monitoring and advising system
US5758062A (en) * 1996-04-30 1998-05-26 Oracle Corporation Method and apparatus for regression testing of application logic
US5748884A (en) * 1996-06-13 1998-05-05 Mci Corporation Autonotification system for notifying recipients of detected events in a network environment
US6072777A (en) * 1996-06-28 2000-06-06 Mci Communications Corporation System and method for unreported root cause analysis
US5974572A (en) * 1996-10-15 1999-10-26 Mercury Interactive Corporation Software system and methods for generating a load test using a server access log
EP0951706A4 (en) * 1996-12-03 2000-02-23 Ergolight Ltd Computerized apparatus and methods for identifying usability problems of a computerized system
US6038538A (en) * 1997-09-15 2000-03-14 International Business Machines Corporation Generating process models from workflow logs
US6108711A (en) * 1998-09-11 2000-08-22 Genesys Telecommunications Laboratories, Inc. Operating system having external media layer, workflow layer, internal media layer, and knowledge base for routing media events between transactions
US6370508B2 (en) * 1998-09-11 2002-04-09 Genesys Telecommunications Laboratories, Inc. Interface engine for managing business processes within a multimedia communication-center
US6182086B1 (en) * 1998-03-02 2001-01-30 Microsoft Corporation Client-server computer system with application recovery of server applications and client applications
US6219679B1 (en) * 1998-03-18 2001-04-17 Nortel Networks Limited Enhanced user-interactive information content bookmarking
US6587969B1 (en) * 1998-06-22 2003-07-01 Mercury Interactive Corporation Software system and methods for testing the functionality of a transactional server
US6826553B1 (en) * 1998-12-18 2004-11-30 Knowmadic, Inc. System for providing database functions for multiple internet sources
US20010012286A1 (en) * 1999-01-29 2001-08-09 Emmanuel L. Huna Method and apparatus for computer alert of device independent messages
US6473794B1 (en) * 1999-05-27 2002-10-29 Accenture Llp System for establishing plan to test components of web based framework by displaying pictorial representation and conveying indicia coded components of existing network framework
US6993747B1 (en) * 1999-08-30 2006-01-31 Empirix Inc. Method and system for web based software object testing
US6934934B1 (en) * 1999-08-30 2005-08-23 Empirix Inc. Method and system for software object testing
JP2001134610A (en) * 1999-11-09 2001-05-18 Fujitsu Ltd Method for specifying browser display content
US6901582B1 (en) * 1999-11-24 2005-05-31 Quest Software, Inc. Monitoring system for monitoring the performance of an application
US6775824B1 (en) * 2000-01-12 2004-08-10 Empirix Inc. Method and system for software object testing
US6832367B1 (en) * 2000-03-06 2004-12-14 International Business Machines Corporation Method and system for recording and replaying the execution of distributed java programs
WO2001069412A2 (en) * 2000-03-14 2001-09-20 Speed-Trap.Com Ltd. Monitoring and modifying services provided over a network
US7000224B1 (en) * 2000-04-13 2006-02-14 Empirix Inc. Test code generator, engine and analyzer for testing middleware applications
US7120676B2 (en) * 2000-04-28 2006-10-10 Agilent Technologies, Inc. Transaction configuration system and method for transaction-based automated testing
US20020038388A1 (en) * 2000-09-13 2002-03-28 Netter Zvi Itzhak System and method for capture and playback of user interaction with web browser content
US7099939B2 (en) * 2000-10-03 2006-08-29 Sun Microsystems Inc. HTTP transaction monitor with sequence replay capacity
US20020065911A1 (en) * 2000-10-03 2002-05-30 Von Klopp Ana H. HTTP transaction monitor with edit and replay capacity
US6865692B2 (en) * 2000-10-27 2005-03-08 Empirix Inc. Enterprise test system having program flow recording and playback
US7231606B2 (en) * 2000-10-31 2007-06-12 Software Research, Inc. Method and system for testing websites
US20020138226A1 (en) * 2001-03-26 2002-09-26 Donald Doane Software load tester
US7197559B2 (en) * 2001-05-09 2007-03-27 Mercury Interactive Corporation Transaction breakdown feature to facilitate analysis of end user performance of a server system
US6738933B2 (en) * 2001-05-09 2004-05-18 Mercury Interactive Corporation Root cause analysis of server system performance degradations
US20020198985A1 (en) * 2001-05-09 2002-12-26 Noam Fraenkel Post-deployment monitoring and analysis of server performance
US6874099B1 (en) * 2001-05-31 2005-03-29 Sprint Communications Company L.P. Method and software for testing and performance monitoring
US6799147B1 (en) * 2001-05-31 2004-09-28 Sprint Communications Company L.P. Enterprise integrated testing and performance monitoring software
CA2455079A1 (en) * 2001-08-06 2003-02-20 Mercury Interactive Corporation System and method for automated analysis of load testing results

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303166A (en) * 1992-04-14 1994-04-12 International Business Machines Corporation Method and system for automated network benchmark performance analysis
US5553235A (en) * 1992-10-23 1996-09-03 International Business Machines Corporation System and method for maintaining performance data in a data processing system
US5812780A (en) * 1996-05-24 1998-09-22 Microsoft Corporation Method, system, and product for assessing a server application performance
US6360332B1 (en) * 1998-06-22 2002-03-19 Mercury Interactive Corporation Software system and methods for testing the functionality of a transactional server
US6138157A (en) * 1998-10-12 2000-10-24 Freshwater Software, Inc. Method and apparatus for testing web sites
WO2001016753A2 (en) 1999-09-01 2001-03-08 Mercury Interactive Corporation Post-deployment monitoring of server performance

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1405190A4

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2868566A1 (en) * 2004-04-01 2005-10-07 Metapages Sarl Method invocation sequence recording process for e.g. object, involves recording and protecting structural information, of invocation graph, representing sequence of invocations and comprising temporal information of invocations
US8732126B2 (en) 2006-10-20 2014-05-20 Oracle International Corporation Filtering workload for database replay
WO2008051855A1 (en) * 2006-10-20 2008-05-02 Oracle International Corporation Database workload capture and replay architecture
US7634512B2 (en) 2006-10-20 2009-12-15 Oracle International Corporation Migrating temporary data of a session
US7890457B2 (en) 2006-10-20 2011-02-15 Oracle International Corporation Transactionally consistent database workload replay
US7890458B2 (en) 2006-10-20 2011-02-15 Oracle International Corporation Capturing database workload while preserving original transactional and concurrency characteristics for replay
US7984015B2 (en) 2006-10-20 2011-07-19 Oracle International Corporation Database workload capture and replay architecture
US8024299B2 (en) 2006-10-20 2011-09-20 Oracle International Corporation Client-driven functionally equivalent database replay
US8997048B1 (en) 2007-02-14 2015-03-31 Oracle America, Inc. Method and apparatus for profiling a virtual machine
US8433680B2 (en) 2008-07-01 2013-04-30 Oracle International Corporation Capturing and restoring database session state
US9104739B2 (en) 2008-07-01 2015-08-11 Oracle International Corporation Capturing and restoring database session state
US8418150B2 (en) 2009-04-03 2013-04-09 Oracle International Corporation Estimating impact of configuration changes
US8863095B2 (en) 2011-05-09 2014-10-14 International Business Machines Corporation Recording and playback of system interactions in different system environments
EP2770438A1 (en) * 2013-02-22 2014-08-27 Bull Sas Monitoring of performance tests executed in a computer system
FR3002663A1 (en) * 2013-02-22 2014-08-29 Bull Sas DISTRIBUTED PERFORMANCE MEASUREMENT MONITORING OF A COMPUTER ARCHITECTURE
US11556500B2 (en) 2017-09-29 2023-01-17 Oracle International Corporation Session templates
US12007941B2 (en) 2017-09-29 2024-06-11 Oracle International Corporation Session state tracking

Also Published As

Publication number Publication date
CN1592891A (en) 2005-03-09
KR20040019045A (en) 2004-03-04
BR0210885A (en) 2004-06-22
ZA200400134B (en) 2005-01-10
EP1405190A1 (en) 2004-04-07
CA2452747A1 (en) 2003-01-16
IL159693A0 (en) 2004-06-20
JP2004535019A (en) 2004-11-18
EP1405190A4 (en) 2007-10-24
US20030088644A1 (en) 2003-05-08

Similar Documents

Publication Publication Date Title
US20030088644A1 (en) Method and system for providing a virtual user interface
US7072935B2 (en) Filtering web proxy for recording web-based transactions that supports secure HTTP steps
US11550596B2 (en) Dynamic generated web UI for configuration
US7568023B2 (en) Method, system, and data structure for monitoring transaction performance in a managed computer network environment
US7966398B2 (en) Synthetic transaction monitor with replay capability
US7792948B2 (en) Method and system for collecting, aggregating and viewing performance data on a site-wide basis
US6631402B1 (en) Integrated proxy interface for web based report requester tool set
US7461369B2 (en) Java application response time analyzer
US6799147B1 (en) Enterprise integrated testing and performance monitoring software
US20050246434A1 (en) Services for capturing and modeling computer usage
US20020138226A1 (en) Software load tester
US20050216573A1 (en) Status-message mapping
US8824656B2 (en) System and method for self-supporting applications
US9405531B2 (en) Methods for building application intelligence into event driven applications through usage learning, and systems supporting such applications
US20160036930A1 (en) Web analytics tags
US20030131008A1 (en) System and method for transaction recording and playback
US7844870B2 (en) Method for embedded integrated end-to-end testing
AU2002316590A1 (en) Method and system for providing a virtual user interface
CN110990237B (en) Information collection system, method and storage medium
CN108108305A (en) A kind of environment availability testing method and system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2452747

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 159693

Country of ref document: IL

WWE Wipo information: entry into national phase

Ref document number: 2002316590

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2003511104

Country of ref document: JP

Ref document number: 1020047000187

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2004/00134

Country of ref document: ZA

Ref document number: 200400134

Country of ref document: ZA

REEP Request for entry into the european phase

Ref document number: 2002746904

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2002746904

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 31/CHENP/2004

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 20028166477

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2002746904

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642