JP2011008558A - Web application operating method, web application system, and processing program thereof - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simply conduct the alteration, addition and deletion of the contents of Web browser operations, and also to maintain continuity among the preceding and subsequent operations, without rerecording the operations from the beginning and rewriting scripts which are the contents of the failed operations in case that a client side records the Web browser operations by a user and reproduces a series of operations thus recorded to measure time required for each operation so as to gain the bodily sensation performance of a Web application, but the reproduction of the recorded operations fails.SOLUTION: When a Web application operating method reproduces and executes operations included in an operation scenario and fails in the reproduction of an operation, it interrupts the reproduction processing with the operation by which the reproduction fails, receives a correcting operation from a user, identifies the point to be corrected for the original operation scenario, and reflects the correcting operation by the user on the original operation scenario to reduce an operational load on a manager.

Description

  The present invention relates to a Web application operation technique.

  Today, the development of information infrastructure is progressing, and information systems can be accessed anytime and anywhere. In addition, Web applications on the front end can be easily operated by anyone via a Web browser that can be easily obtained. Furthermore, in the information society, a search engine for high-speed access to appropriate information from the enormous amount of diversified information, the development of middleware that supports the three levels of the Web, and Web services that can link Web applications on the Internet It is self-evident that usage will continue to expand in the future due to technology.

In this way, with the spread of Web applications, access to Web systems is required to be able to access desired information at high speeds regardless of time and place.
Therefore, in the field of operation management, along with service-in, in order to eliminate the loss of access opportunities from users, response performance is measured for Web applications, Web access performance trends are grasped, and problems can be prevented. Therefore, it is necessary to notice performance deterioration and deal with it quickly.

There are several ways to monitor the performance of a Web application.
One is to monitor the increase / decrease in the number of accesses from the client, the request queue length, and the network input / output volume on the Web server side. Since this method is monitoring on the server side, the operational status regarding what the request from the client has arrived can be grasped, but as a case where the request does not reach from the client to the Web server, it is accepted on the server side. There is a problem that an abnormality cannot be detected for a case in which a request is not accepted because the number of possible requests has been exceeded. This method is disclosed in US Pat.

  The second method that can solve the problem of the method is to measure the response performance by accessing the Web server from the client side at each site. Since this method measures the response performance from the client to the server, it is possible to detect problems such as a failure of the network through which the request passes and the server repels the request. However, in order to measure the response performance from each client by setting up clients at multiple sites, collect a lot of various information to collect the performance of each site and identify the abnormal location. It needs to be analyzed. The analysis method is not described here because it is not directly related to the contents of the present invention. This method is disclosed in Patent Document 2 and Patent Document 3. In Patent Document 2, only the communication performance to the Web site on the Web server can be acquired. However, in Patent Document 3, the Web application execution performance provided by the Web site, that is, the application performance on the client side is included. Performance can be acquired. Therefore, Patent Document 3 can be said to be more effective performance information in actual operation because it collects the user's experience performance for the Web application.

  Japanese Patent Application Laid-Open No. 2004-133867 discloses a technique for searching for a content closer to the recorded operation content by searching the currently reproduced Web page and performing an operation on the detected operation target. Patent Document 5 discloses a method in which input data can be edited and changed by generating a script from operation information and making the script.

Japanese Patent No. 3863740 Patent 3083805 JP 2007-172377 A JP 2006-127117 A JP-A 2005-266954

  In order to acquire the experience performance of a Web application, the Web browser operation by the user is recorded on the client side, and the time required for each operation is measured by playing back the recorded series of Web browser operations. While this series of Web browser operations are automatically replayed over a long period of time and performance information is collected, the contents of the monitored website are changed, the login password for accessing the website expires, and the operation information If the input information in is invalid or an error occurs after the expiration date, a series of operations are interrupted.

  Therefore, three methods can be considered as countermeasures for the case where the reproduction for the recorded operation fails.

  First, as disclosed in Patent Document 4, a content closer to the recorded operation content is found by searching the currently reproduced Web page, and the operation is performed on the detected operation target. There is also a method. However, an operation target that is close to the recorded operation target is not always found on the currently playing Web page.

  The second method is to record a series of operations again. However, it is burdensome for the user to put the effort of redoing all of the series of operations, and it is useless to re-record the operations that have no problem because of some operation failures.

  The third is a method of editing a failed operation and adding or deleting an operation in a series of recorded operation lists. In the method as in Patent Document 5, in order to rewrite or add the record information that is the operation content of the operation list, the user must be able to rewrite the record content with knowledge about the script representing the operation information. In addition, by changing, deleting, or adding some operations, the operations may not be continuous between the previous and subsequent operations.

  The object of the present invention is that if a series of Web browser operations fails, there is little need to re-record the operations from the beginning, and the operation contents can be easily changed without knowledge of rewriting the script representing the failed operation contents. It is possible to change, add, delete, and maintain continuity with previous and subsequent operations.

  Therefore, when an operation included in a certain operation scenario is being played back, if the playback of the operation fails, the playback process is interrupted with the operation that failed to be played back, the corrective operation is accepted from the user, and the corrected part of the original operation scenario And the above-mentioned problem is solved by reflecting the correction operation by the user in the original operation scenario.

  Even if the operation scenario that was recorded due to modification of the web page or change of input information can no longer be played back, it is partially corrected, so it is not necessary to record the operation scenario from the beginning, reducing the workload of the administrator Can do.

Configuration diagram of information processing system 2100 Hardware configuration diagram of information processing system 2100 Diagram showing an example of the operation scenario table 2110 The figure which showed an example of the execution history table 2111 The figure which showed an example of the correction scenario table 2112 Flow diagram showing overall processing by each component that makes up the performance monitoring server Flow diagram showing the correction process by the scenario correction unit How to record and play dialog operations Recording process flow Playback procedure for browser and dialog operations Playback processing method of browser operation and dialog operation Playback processing flow

  The best mode for carrying out the invention will be described with reference to the drawings.

  FIG. 1 is a configuration diagram of an information processing system 2100 according to the present invention.

  The information processing system 2100 includes a performance monitoring server 2101, a web server 2102, and a terminal 2103. The performance monitoring server 2101, the web server 2102, and the terminal 2103 are connected to each other via the network 2006.

  The performance monitoring server 2101 is a computer 2000 that measures operation information and performance information of the Web server 2102. A failure or performance degradation of the Web server 2102 is detected by periodically reproducing and executing a scenario registered in advance and measuring the time and response time required for the operation.

  The performance monitoring server 2101 includes a web browser 2104, a scenario playback unit 2106, a performance measurement unit 2107, a scenario correction unit 2108, and a storage unit 2109.

  The web browser 2104 is a browser to be used and a user agent. The Web server 2102 has a function of acquiring a Web document 2116 provided by the Web server 2102 as a Web document 2105 described later via the network 2006, analyzing the Web document, and outputting based on the analysis result. Some are equipped with a script engine such as JavaScript (registered trademark), others can use Java (registered trademark) plug-ins, Adobe Flash (registered trademark), and the like.

  The web browser 2104 includes a web document 2105. However, although it is a Web document here, it is not limited to a Web document, and any resource can be used as long as it can be handled by a Web browser. Text, an image, and Adobe Flash (registered trademark) may be used.

  Web document 2105 is a resource. The Web document includes, for example, text and images and is described in HTML format, and hyperlinks to other Web documents 2105 are described.

  The scenario playback unit 2106 is a processing unit that plays back and executes an operation process for the Web browser 2104. Scenario information recorded in an operation scenario table 2110 to be described later is read out, and based on the operation information recorded in the scenario information, operation processing specified by the operation information is sequentially executed on the Web browser 2104. The scenario reproducing unit 2106 executes the schedule, reads the operation scenario table 2110 from the storage unit 2109 at the regularly scheduled time, and reproduces and executes it.

  The performance measuring unit 2107 is a processing unit that measures the time required to reproduce the scenario operation process. The time from when the operation is reproduced to the Web browser 2105 until the Web browser responds to the response to the operation is measured. Specifically, when a hyperlink is clicked and the page transitions and another page is displayed, the scenario playback unit 2106 sends a request to click the hyperlink to the web browser 2105, and then the web browser 2105 Measure the time to complete loading of another page. Further, not only the time but also the time when the scenario playback unit 2106 transmits a request to click the hyperlink to the Web browser 2105 and the time when the Web browser 2105 is in a state where the reading of another page is completed are recorded. Furthermore, the time required for the entire scenario is measured by adding the times for each operation. Note that the time recorded by the performance measurement unit 2107 may be the response time of the Web server 2101. The response time is the time from when a request is sent to the Web server 2101 to when there is a response from the Web server 2101. The response time may be the response time up to the arrival time of the Web page, or may be the response time including the rendering time of the Web browser 2104.

  The scenario correction unit 2108 is a processing unit that corrects a scenario. The scenario correction unit 2108 corrects the contents of a scenario in an operation scenario table 2110 described later based on the scenario correction operation input by the administrator.

  The storage unit 2109 is a configuration unit that stores various management information of the performance monitoring server 2101.

  The storage unit 2109 includes an operation scenario table 2110, an execution history table 2111 and a correction scenario table 2112.

  The operation scenario table 2110 is a table for storing information on a scenario to be reproduced by the scenario reproducing unit 2106.

  In the operation scenario table 2110, for example, information as shown in FIG. 3 described later is stored.

  The execution history table 2111 is a table that stores the results of scenario playback by the scenario playback unit 2106.

  In the execution history table 2111, for example, information as shown in FIG. 4 described later is stored.

  The correction scenario table 2112 is a table for temporarily storing scenario correction contents. The scenario correction operation input by the administrator is temporarily stored in the correction scenario table 2112. The scenario stored in the operation scenario table 2110 by the scenario correction unit 2109 based on the information stored in the correction scenario table 2112. To correct.

  The correction scenario table 2112 stores, for example, information as shown in FIG.

  The Web server 2102 is a computer 2000. Accept a Web document request and respond to the requested Web document. The web server 2102 includes a web document 2116.

  A terminal 2103 is a terminal device of the performance monitoring server 2101. The administrator transmits a request to the performance monitoring server 2101 through the terminal 2101 and displays a response from the performance monitoring server 2101 to the request to the administrator.

  The terminal 2103 includes an input / output unit 2113, a transmission / reception unit 2114, and an information processing unit 2115.

  The input / output unit 2113 is a processing unit that transmits information input by the administrator through the terminal to the information processing unit 2115 and outputs information received from the information processing unit 2115 to the administrator.

The transmission / reception unit 2114 is a processing unit that transmits information received from the information processing unit 2115 via the network and transmits information received from the network to the information processing unit 2115.
The information processing unit 2115 is a processing unit that processes information transmitted / received from the input / output unit 2113 or the transmission / reception unit 2114.

  FIG. 2 is a hardware configuration diagram showing a computer 2000, an external storage device 2005, a network 2006, an input / output device 2007, an output device 2008, and their connection relationships that constitute the present invention.

  The computer 2000 includes a CPU 2001, a main storage device 2002, an external storage device 2003, and a communication interface 2004, which are connected by a bus.

  Information processing by the processing unit shown in FIG. 1 can be specifically realized by the hardware shown in FIG. The web browser 2104, the scenario playback unit 2106, the performance measurement unit 2107, the scenario correction unit 2108, and the information processing unit 2115 are realized by programs and objects. These processing units can be realized by reading the main storage device 2002 from a storage medium such as a CD-ROM or a DVD and performing information processing by the CPU 2001. These processing units can also be realized by hardware. The storage unit 2109 can be realized by the external storage device 2005. The input / output unit 2113 can be realized by an input / output device. The transmission / reception unit 2114 can be realized by the communication interface 2004.

  FIG. 3 is a diagram showing an example of the operation scenario table 2110.

  Each record of the operation scenario table 2110 stores an operation, and when the operations stored in the record are reproduced in order from top to bottom, a series of Web transactions is obtained.

  The operation scenario table 2110 includes a scenario ID column 2201, an operation ID column 2202, an operation name column 2203, an operation target column 2204, an operation content column 2205, an operation start condition column 2206, an operation end condition 2207, a page An ID column 2208 is provided.

  The scenario ID column 2201 stores identification information that uniquely identifies a scenario. Records with the same scenario ID indicate that they belong to the same scenario.

  The operation ID column 2202 stores identification information that uniquely identifies an operation.

  The operation name column 2203 stores the name of the operation. Here, it is stored in a character string that indicates the operation content. The information to be stored may be input by a person based on the operation content, or text may be automatically generated according to the operation target or operation content.

  The operation target column 2204 stores information for specifying the operation target. The DOM object pattern information specified by analyzing the Web document 2105 and information for specifying the constituent objects of the dialog generated in association with the Web browser 2104 are stored. For example, if the operation is a hyperlink click, the character string displayed in the hyperlink (so-called InnerText value), tag name (a tag), tag attribute (specifically ID attribute, name attribute, href) (Such as attributes) values, tag numbers, relationships with other tags (parent-child relationships, sibling relationships, etc.), or a combination of these. The identification method may be any method, and may be described in a format such as XPath. If the operation is to enter a user name and password in the authentication dialog, the dialog class name and title are stored as information for specifying the authentication dialog, and the field ID is stored as information for specifying the field for entering the user name and password. To do. Relationship information (inclusion relationship etc.) with other configuration objects constituting the authentication dialog may be stored.

  The operation content column 2205 stores information for specifying the operation content. Stores events to be issued to the browser during playback, input text information, window messages sent to dialogs, and the like. Specifically, click events, text information input to a text form, dialog button down, button up message information, and the like.

  The operation start condition column 2206 stores a condition to be satisfied in order to start an operation.

  The operation end condition 2207 stores a condition that must be satisfied in order to complete the operation.

  For example, when the same page is operated between operations in the same scenario, the page ID column 2208 stores the same identifier.

  The dependency column 2209 stores information as to whether or not it depends on the previous operation content. If it depends, it stores “T”, otherwise it stores “F”. The case where it does not depend is, for example, a case where a page is moved by directly specifying a URL.

  FIG. 4 is a diagram showing an example of the execution history table 2111. As shown in FIG.

  The execution history table 2111 includes a history ID column 2301, a scenario ID column 2202, an operation ID column 2203, an execution status column 2304, an execution result column 2305, a start time column 2306, an end time column 2307, and a response time. A column 2308 and a detail column 2309 are provided.

  The history ID column 2301 is identification information for uniquely specifying the scenario reproduction result. Even if the same scenario is played, a different identifier is assigned and managed every time the periodic execution is performed.

  The scenario ID column 2202 stores an identifier for uniquely specifying a scenario.

  The operation ID column 2203 stores an identifier for uniquely specifying an operation constituting the scenario.

  The execution state column 2304 stores the execution state of the operation. For example, “executed” is stored if the execution is completed, “executed” if it is being executed, and “not executed” if it is not being executed.

  The execution result column 2305 stores the status of the execution result. For example, “success” is stored if the operation is successful, “failure” is stored if the operation is unsuccessful, and “n / a” is stored if the operation is not executed.

  The start time column 2306 stores the time when the operation execution is started.

  The end time column 2307 stores the time when the operation execution is ended.

  The response time column 2308 stores the time required for operation execution. The value calculated by obtaining the difference between the time stored in the start time column 2306 and the time stored in the end time column 2307 is stored.

  The detail column 2309 stores related information. For example, when the operation execution fails, the cause is stored.

  FIG. 5 is a diagram showing an example of the correction scenario table 2112.

  The correction scenario table 2112 includes a correction scenario ID column 2401, a scenario ID column 2402, an operation ID column 2403, an operation target 2404, and an operation content column 2405.

  The correction scenario ID column 2401 stores identification information for specifying a correction scenario.

  The scenario ID column 2402 stores identification information for specifying a scenario to be corrected.

  The operation ID column 2403 stores identification information for specifying operations constituting the correction scenario.

  The operation target 2404 stores information for specifying the operation target of the operation constituting the correction scenario. The operation target of the operation input by the administrator is stored as pattern information. The acquisition method and format are the same as those in the operation target column 2204 of the operation scenario table 2110.

  The operation content column 2405 stores information for specifying the operation content of the operations that constitute the correction scenario. The operation content of the operation input by the administrator is stored. The acquisition method and format are the same as those in the operation target column 2205 of the operation scenario table 2110.

  FIG. 6 is a flowchart showing overall processing by each component constituting the performance monitoring server.

  (1) The scenario playback unit 2106 receives a scenario A execution request (step 2501).

  (2) The scenario playback unit 2106 reads the operation scenario table 2110 and identifies scenario A scheduled for playback execution according to the schedule (step 2502). The scenario ID column 2201 is searched to obtain a record having an identifier corresponding to the scenario A.

  (3) The scenario playback unit 2106 identifies the first operation A of scenario A (step 2503). Among the records acquired at step 2502, the first record is specified as operation A.

  (4) The scenario playback unit 2106 identifies the operation content A and the operation target pattern A from the operation A (step 2504). The content stored in the operation content column 2205 of the record specified in step 2503 is defined as operation content A, and the content stored in the operation target column 2204 is defined as operation target pattern A.

  (5) The scenario playback unit 2106 reads the Web document 2105 from the Web browser 2104, and specifies the target B that matches the operation target pattern A (step 2505). When the Web document 2105 is composed of a DOM, an object that matches the operation target pattern A is acquired from the DOM of the Web document 2105 and set as a target B.

  (6) The scenario playback unit 2106 determines whether or not there is a target B (step 2506). If there is a target B as a result of the determination in step 2506, the process proceeds to step 2508. Otherwise, go to Step 2507.

  (7) If the result of determination in step 2506 is that there is no target B, the scenario correction unit 2108 corrects scenario A (step 2507). This process will be described in detail with reference to FIG. Once corrected, go to step 2508.

  (8) If there is a target B as a result of the determination in step 2506, the scenario reproducing unit 2106 executes the operation content A on the target B (step 2508). For example, when the target B is a link and the operation content A is a link click, the link click is executed on the link. Further, if the target B is a text form configured with an input tag having an id attribute “user”, and the operation content A is the text “user001” input to the form, the character string “user001” is embedded in the text form.

  (9) The performance measurement unit 2107 records the execution start time (step 2509). For example, a new record is generated in the execution history table 2111 and the current time is stored in the start time column 2306.

  (10) The scenario playback unit 2106 determines whether the operation is completed (step 2510). For example, the completion of the operation determines whether the condition described in the operation end condition column 2207 of the operation scenario table 2110 is met. Specifically, if the operation end condition column 2207 stores the pattern information of the event that occurs until the operation is completed after the operation is executed, it is determined that the operation is completed when an event that matches the pattern arrives. .

  (11) If the result of determination in step 2510 is complete, the performance measurement unit 2106 records the execution end time. For example, the current time is stored in the end time column 2307 of the record generated in step 2509. Instead of the current time, the time when the condition in the operation end condition column 2207 is satisfied in step 2501 may be measured.

  (12) The performance measurement unit 2106 calculates the time taken for the operation A from the execution start time and the execution end time, and stores it as a response time (step 2512). For example, in the execution history table 2111, the difference between the start time column 2306 and the end time column of the record generated in step 2509 is calculated and stored in the response time column 2308.

  (13) The scenario playback unit 2106 stores the successful execution of the operation A (step 2513). For example, in the execution history table 2111, “success” is stored in the execution result column 2305 of the record generated in step 2509.

  (14) The scenario playback unit 2106 changes the operation A to the executed state (step 2514). For example, in the execution history table 2111, “executed” is stored in the execution status column 2304 of the record generated in step 2509.

  (15) The scenario playback unit 2106 determines whether there is a next operation in the unexecuted state in the scenario A (step 2515). If there is a next operation, the process proceeds to step 2516. If not, the process proceeds to step 2517.

  (16) If the result of determination in step 2515 is that there is a next operation, the scenario playback unit 2106 acquires the next operation A that has not been executed from the scenario A (step 2516). The processing after step 2504 is repeated in the same manner.

  (17) If the result of determination in step 2515 is that there is no next operation, the performance measurement unit 2107 adds up the time for each operation and calculates the time taken for scenario A (step 2517). When step 2517 is executed, the process ends.

  (18) If the operation A has not been completed in the determination in step 2510, the scenario reproducing unit 2106 determines whether a timeout has occurred (step 2518). If it is before the timeout, the process returns to step 2510. If timed out, the process proceeds to step 2519.

  (19) If the result of determination in step 2518 is timeout, the performance measurement unit 2107 stores the operation end time (step 2519). Same as step 2519.

  (20) The performance measurement unit 2107 calculates and stores the time taken for the operation A from the execution start time and the execution end time (step 2520). Same as step 2520.

  (21) The scenario playback unit 2106 stores the execution failure of the operation A (step 2621). For example, in the execution history table 2111, “failure” is stored in the execution result column 2305 of the record generated in step 2509.

  (22) The scenario playback unit 2106 changes the operation A to the executed state (step 2522). For example, in the execution history table 2111, “executed” is stored in the execution status column 2304 of the record generated in step 2509.

  (23) The scenario reproducing unit 2106 determines whether or not there is an operation that can be executed in the unexecuted state in the scenario A (step 2523). As a result of the determination, if there is, the process proceeds to Step 2114. If not, exit. For example, in the record related to the operation scenario A in the execution history table 2111, the execution status column 2304 is “not executed”, and the dependency column 2209 of the record in the operation scenario table 2110 associated with the operation ID column 2302 and the operation ID column 2202 is Judge whether there is a record with "T".

  (24) If there is a corresponding operation as a result of the determination in step 2523, the scenario reproducing unit 2106 acquires an executable operation in an unexecuted state from the scenario A and sets it as the operation A (step 2114). After step 2114, step 2504 and subsequent steps are repeated by a new operation A.

FIG. 7 is a flowchart showing the correction processing by the scenario correction unit 2108.
The processing from step 2601 to step 2607 is a processing operation for receiving and storing the correction operation from the administrator who is the user.

  (1) The scenario correction unit 2108 detects an operation failure (step 2601).

  (2) The scenario correction unit 2108 stores the operation A as a failure operation Y (step 2602). The operation A is temporarily stored as the failure operation Y.

  (3) The scenario correction unit 2108 initializes the correction scenario A (step 2603). The correction scenario table 2112 is initialized so that the correction operation from the user can be recorded.

  (4) The scenario correction unit 2108 receives a user operation C (step 2604). The user's operation C for the web browser 2104 and the dialog is accepted.

  (5) The scenario correction unit 2108 stores the operation C in the correction scenario A (step 2605). For example, an operation for returning a browser transition history, an operation for re-entering a password in a text form, and the like are stored. The browser event or window message is received, the operation target and the operation content are specified, and stored in the correction scenario table 2112. Each time initialization is performed in step 2603, a new identifier is recorded in the modified scenario ID column 2401. The scenario ID column 2402 stores the value of the scenario ID column 2302 of the record corresponding to the operation A in the execution history table 2111. The operation ID column 2403 stores identification information for identifying the record of the correction scenario table 2112. The operation target column 2404 stores the specified operation target information, and the operation content column 2405 stores the specified operation content information.

  (6) The scenario correction unit 2108 determines whether the operation target of the operation C matches the operation target of the failure operation Y (step 2606). As a result of the determination, if they match, the process proceeds to step 2607. If they do not match, the process returns to step 2604. The determination process in step 2606 is a process for determining the end of the correction operation from the user. If the operation corresponding to the operation stored as the failure operation Y has succeeded in the correction processing operation, it is determined that the correction processing operation has ended. Whether or not the operation corresponds to the failed operation Y is determined by whether or not the operation is the same operation target as the operation target of the failed operation Y.

(7) If the results of the determination in step 2606 match, the scenario correction unit 2108 determines whether the operation A has succeeded (step 2607). As a result of the determination, if it is successful, the process proceeds to Step 2608. If unsuccessful, the process returns to step 2603 to prompt the user to input again.

The processing from step 2608 to step 2618 is a processing operation for correcting the original scenario based on the correction information received from the administrator who is the user.

  (8) If the result of the determination in step 2607 is successful, the scenario correcting unit 2108 temporarily stores the failed operation Y as a correcting operation (step 2608). This is a process for specifying the correction range in the original operation scenario, and temporarily specifies the operation from the failed operation Y to the operation being corrected as a correction candidate operation.

(9) The scenario correction unit 2108 reads the correction scenario A (step 2609). The correction scenario table 2112 is read from the storage unit 2109 to obtain a series of correction scenarios A.
(10) The scenario correction unit 2108 reads the first operation D from the correction scenario A (step 2610). Acquire the first operation D constituting the correction scenario A. Specifically, the first record of the correction scenario table 2112 is acquired.

  (11) The scenario correction unit 2108 determines whether there is an operation E in which the operation D and the operation target match among the operations from the operation being corrected in scenario A to the failure operation Y (step 2611). If they match as a result of the determination, the process proceeds to step 2612. If not, the process proceeds to step 2614. Among the operations stored in the operation scenario table 2110 and specified as correction candidates, an operation corresponding to the correction operation D input by the user is specified. The corresponding operation is identified based on whether or not the operation targets match.

  (12) The scenario correcting unit 2108 replaces the content of the operation E in the scenario with the content of the operation D if they match as a result of the determination in step 2611. By changing the operation in the operation scenario table 2110 to the content of the correction operation input by the user, the correction is reflected in the original operation scenario.

  (13) The scenario correction unit 2108 temporarily stores the operation E as an operation being corrected (step 2613). After storing, go to step 2617. Narrow the range of correction.

  (14) As a result of the determination in step 2611, if they do not match, the scenario correcting unit 2108 determines whether or not the operation D is an operation for returning the browser history (step 2614). If it is a return operation, the process proceeds to step 2615. If it is not a return operation, the process proceeds to step 2616. In the case of a return operation, the content of the original operation scenario is not changed, but the operation for the page displayed before the failed operation is corrected. Therefore, the return operation itself is not stored, and the information in the page ID column 2208 Based on the above, expand the range of correction candidates.

  (15) If the result of determination in step 2614 is a return operation, the scenario correction unit 2108 temporarily stores the operation corresponding to the return destination page in scenario A as the operation being corrected (step 2615). After storing, go to step 2617.

  (16) If the result of the determination in step 2614 is that the operation is not a return operation, the scenario correcting unit 2108 adds the operation E to the scenario A as the operation next to the operation stored as the operation being corrected (step 2616). After the addition, go to step 2613. Since this is a case where an operation that is not in the original operation scenario is required, a new addition correction is made to the original operation scenario.

(17) After the processing of step 2613 and step 2615, the scenario correction unit 2108 determines whether the correction scenario A has an operation next to the operation D (step 2617). If it is determined that there is a next operation, the process proceeds to step 2618. If not, the correction process is terminated. If an unreflected operation is included in the correction scenario A, the reflection process is continued.
(18) If the result of determination in step 2617 is that there is a next operation, the scenario correction unit 2108 reads the next operation from the correction scenario A and sets it as operation D (step 2618). Step 2611 and subsequent steps are processed by a new operation D.

  With the processing operation shown in FIG. 7, the scenario can be partially corrected without recreating the scenario from the beginning for scenario correction. Also, the administrator does not need to be aware of the changes in the original scenario and the description format of the scenario. The administrator can correct the scenario only by inputting the corrected operation. Unlike the processing in Fig. 8 to be described later, since operations are individually compared, operations that do not need to be reflected in the original scenario included in the revised scenario are identified, and only those that need to be reflected are reflected. Can be made.

  Fig. 8 shows how to record and play back dialog operations. In recording and playing back a dialog operation, processing 1201 is executed for adding a hook to the operation target window and capturing a dialog related to the window. The dialog operation recording process 1202 records the dialog window title, child window authentication information class, EditBox control ID and input data, and various button control IDs for the captured dialog. If the title of the Dialog window matches the recorded Dialog window for the captured Dialog window, 1203 will respond to the window handle (HWND) that matches the recorded window information, class, and control ID. , Send a transmission message containing recorded data.

FIG. 9 is a processing flow of the recording processing unit 1004. The recording processing unit 1004 waits for a recording event 1301 generated when the user clicks the recording button 505 on the operation screen 500 from the execution control unit 1003. When the recording event is received, the Web browser operation recording process 1302, the pop-up dialog recording process 1303, and the stop event waiting process 1304 are executed in parallel.
The Web browser operation record processing 1302 registers 1305 event handlers for acquiring link clicks, text input in forms, button clicks, etc., which are operation events from the user for the document displayed on the Web browser control. When a web browser event is generated 1307 after waiting for a web browser event 1307 by the user's web browser operation 1306 and a web browser event occurs, the tag information that is the event issue source, the operation content such as click or text input, and the page title after the page transition caused by the operation And add 1308 to the end of the operation scenario in order of event occurrence.

  The pop-up dialog recording process 1303 starts a monitoring program for capturing a dialog that is called from this execution program in order to capture the pop-up dialog that appears during the Web browser operation, waits for the pop-up dialog disappearing event 1311, and When the disappearance event occurs, the dialog content 1310 including the input information is acquired and additionally registered 1312 at the end of the operation scenario.

  The stop event waiting process 1304 waits for a stop event 1304 that occurs when the user clicks the stop button 506 from the execution control unit 1003, and ends the recording process 1004 when a stop event occurs.

10 to 12 show the processing contents of the playback processing unit 1005. FIG.
FIG. 10 shows a playback processing procedure for browser operation and dialog operation. FIG. 14 shows a Web browser state 1404 for an operation scenario 1403 caused by the Web browser operation playback processing 1401 by the Main thread and the dialog capture and playback processing 1402 by the child thread. When the click operation 1405 is reproduced on the Web browser, the Web browser enters a document reading start state 1406. Subsequently, when an authentication dialog 1407 appears and an operation on the dialog is reproduced, the Web browser enters a document reading completion state 1408, and reaches the document reading completion operation of the operation scenario.

FIG. 11 shows a reproduction processing method of browser operation and dialog operation. In FIG. 15, the playback processing is executed by the browser control processing thread 1501 and the dialog processing thread 1502. When the browser control processing thread 1501 is executed, the browser control 1503 changes state, and when the dialog processing thread 1502 is executed, the window procedure WinProc 1504 changes state. Here, a browser operation and a browser event associated therewith are set as one operation unit 1505, and the required time is measured for each operation unit. In addition, a series of operation groups 1506 up to one dialog operation is set as a replay processing unit to be continuously executed. The form information input / playback processing 1507 converts a value 1508 before form input into a value 1509 after form input.
FIG. 12 is a processing flow of the reproduction processing unit 1005. When the user clicks the play button 507 from the execution control unit 1003, the process waits for a play event 1601. When a play event is received, the block play process 1602 and the pause event wait 1603 process are executed in parallel.
The pause event wait process 1603 waits for a pause event 1603 generated from the execution control unit 1003 when the user clicks the pause button. When a pause event is received, a playback event wait 1601 is performed.

In the block playback process 1602, the operation scenario is played back in units of blocks, with the pop-up dialog appearing as one block.
First, the operation from the beginning of the unexecuted operation of the operation scenario to the appearance of the pop-up dialog is extracted 1604, and the extracted operation group is set as a reproduction processing unit.
Next, Web browser operation playback processing 1605 and pop-up dialog playback processing 1606 are executed in parallel.

  The Web browser operation playback process 1605 sequentially executes all Web browser operations except for operations on pop-up dialogs. The Web browser operation reproduction process 1605 first registers 1607 an event handler for acquiring a Web page reading completion event in the Web browser control. Next, 1608 is extracted from the beginning of the unexecuted operation of the scenario to be played back to the point immediately before the next operation event other than the document display completion event. Each process of 1610 is executed in parallel. When the document display completion event wait 1610 receives the completion event, the number of events is incremented 1611 and the document display completion event wait 1610 is executed until the number of event arrivals is the same as that at the time of recording.

  The pop-up dialog playback processing 1606 starts a monitoring program for capturing a dialog called from this execution program, waits for the pop-up dialog to appear 1613, and when the pop-up dialog appears, compares it with the window title of the recorded dialog 1614, If they match, the information in the dialog is sent 1615, and if they do not match, the appearance of an unexpected dialog is registered 1616 in the execution history, and the playback process ends.

  As mentioned above, although embodiment of this invention was described, this embodiment is only the illustration for description of this invention, and is not the meaning which limits the scope of the present invention only to that embodiment. The present invention can be implemented in various other modes without departing from the gist thereof.

  By processing in this way, it is not necessary to record the operation scenario from the beginning because the operation scenario that was recorded due to the modification of the web page or the change of input information is partially corrected even if it can no longer be played back. Work load can be reduced. In addition, since the operation scenario is not directly edited, the operation scenario can be corrected in the same way as recording the operation scenario without being aware of the changed part of the operation scenario and the format of the operation scenario.

2101 Performance monitoring server 2102 Web server 2103 Terminal 2104 Web browser 2105 Web document 2106 Network 2107 Performance measurement unit 2108 Scenario correction unit 2109 Storage unit

Claims (5)

A web application operation method in a web application system by an information processing system including a reproduction unit, a correction unit, and a storage unit,
A step of reading an operation scenario stored from the storage unit and causing the reproduction unit to sequentially reproduce and execute operations belonging to the operation scenario;
The correction unit detecting a failure to execute the reproduction by the reproduction unit;
Receiving a correction operation from the user by the correction unit;
The correction unit specifying an operation to be corrected from the operation scenario;
Correcting the operation of the object based on the correction operation;
A method for operating a Web application, comprising: The step in which the correction unit specifies an operation to be corrected from the operation scenario,
2. The step of identifying an operation to be corrected by comparing an operation target of an operation belonging to the operation scenario with an operation target of a correction operation based on the operation for which the reproduction execution has failed. The Web application operation method described. The step in which the correction unit specifies an operation to be corrected from the operation scenario,
When there is an operation for tracing the browser page history in the correction operation,
Narrow down the operation to be corrected in the operation scenario by the operation and Web page identification information,
The step of identifying the operation to be corrected by comparing the operation target of the operation belonging to the operation scenario with the operation target of the correction operation on the basis of the operation for which the reproduction execution has failed. Item 1. Web application operation method. A web application system based on an information processing system including a reproduction unit, a correction unit, and a storage unit,
Means for reading an operation scenario stored from the storage unit and causing the reproduction unit to sequentially reproduce and execute operations belonging to the operation scenario;
Means for the correction unit to detect failure of reproduction execution of the operation by the reproduction unit;
Means for the correction unit to accept a correction operation from a user;
Means for the correction unit to specify an operation to be corrected from the operation scenario;
Means for correcting the operation of the object based on the correction operation;
A method for operating a Web application, characterized by comprising: A web application operation program for causing a web application system to function by an information processing system including a reproduction unit, a correction unit, and a storage unit,
A step of reading an operation scenario stored from the storage unit and causing the reproduction unit to sequentially reproduce and execute operations belonging to the operation scenario;
The correction unit detecting a failure to execute the reproduction by the reproduction unit;
Receiving a correction operation from the user by the correction unit;
The correction unit specifying an operation to be corrected from the operation scenario;
Correcting the operation of the object based on the correction operation;
A Web application operation program characterized by comprising:

Images