WO2013190607A1 - 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 - Google Patents
画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 Download PDFInfo
- Publication number
- WO2013190607A1 WO2013190607A1 PCT/JP2012/065465 JP2012065465W WO2013190607A1 WO 2013190607 A1 WO2013190607 A1 WO 2013190607A1 JP 2012065465 W JP2012065465 W JP 2012065465W WO 2013190607 A1 WO2013190607 A1 WO 2013190607A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- screen
- client
- information
- screen information
- computer
- Prior art date
Links
Images
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/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
- G06F16/24565—Triggers; Constraints
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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
-
- 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
Definitions
- the present invention relates to a screen information collection computer that collects client screen information from a client computer.
- the server In the Web application, the server generates screen information to be displayed on the client, and the server transmits the generated screen information to the client. For this reason, since the server displays a screen displayed by the client immediately after the server transmits the screen information, the server administrator can easily check this screen.
- the screen displayed by the client changes depending on the user operation accepted by the client.
- the server can acquire the screen information displayed on the client by embedding processing for acquiring the screen information in a screen script generated to display the screen information on the client.
- the storage capacity of the server is quantitatively limited. Therefore, it is necessary for the server to acquire the screen information displayed on the client at an appropriate timing.
- JP 2011-76152 A Patent Document 1
- Patent Document 1 JP 2011-76152 A (Patent Document 1) as a technique for acquiring this screen information.
- This gazette states that “a capture system that captures the display contents of items that require visual confirmation on the screen among the screens provided by the web application to the web browser, and items that need confirmation on the screen for each test case.
- Analyzing means for analyzing the checklist defining the confirmation contents, and capturing only specific items defined in the checklist according to the analysis result of the analyzing means in the screen provided by the Web application and storing them in the image file
- Capture acquisition means capture acquisition result generation means for generating a confirmation screen file by associating the acquired image file and confirmation contents
- capture acquisition result for displaying the contents of the confirmation screen file generated by the capture acquisition result generation means It is characterized by comprising display means ”( About reference).
- the screen information acquisition timing also depends on how the Web application is used, it is difficult for the administrator to determine the screen information acquisition timing when developing the Web application.
- Patent Document 1 only discloses capturing a specific item defined in the checklist, and does not disclose the acquisition timing of image information, and cannot solve the above-described problem.
- the present invention has been made in view of these problems, and an object of the present invention is to provide a computer that automatically determines the optimum acquisition timing of image information displayed on a client.
- a typical example of the invention disclosed in the present application is as follows. That is, in a screen information collection computer that collects client screen information that is information of the client screen from a client computer that accepts a user operation on the displayed client screen, client screen information collection that collects the client screen information from the client computer And the operation information collection unit that collects operation information indicating information that can identify the user operation on the client screen, and the client screen information collection unit includes the client screen information among the user operations on the client screen.
- a trigger operation determination unit that determines a trigger operation that is a timing to collect, and the trigger operation determination unit is configured to perform the trigger operation based on client screen information and the operation information displayed on the client computer. Determination characterized in that it.
- FIG. 1 is a schematic explanatory diagram of an embodiment of the present invention.
- the information processing system of this embodiment includes a client computer (PC) 10, a business Web server 20, and a log recording / reproducing server 40.
- the client PC 10, the business Web server 20, and the log recording / playback server 40 are connected via a network 80.
- the client PC 10 executes the screen script transmitted from the business Web server 20, displays the client screen, and accepts user input via the displayed client screen.
- the client PC 10 transmits a request to the business Web server 20 when a predetermined button is operated on the client screen.
- the client PC 10 transmits to the log recording / reproducing server 40 operation information indicating the operation content on the client screen and the client screen.
- the business Web server 20 receives the request transmitted by the client PC 10, executes processing corresponding to the request, generates a screen script for causing the client PC 10 to display a client screen according to the execution result, and generates the generated screen
- the script is transmitted to the client PC 10.
- the log recording / reproducing server 40 records the client screen information and operation information transmitted from the client PC 10 and displays the recorded client screen information and operation information.
- the client PC 10 is executing a business application for a travel expense settlement system, and displays a travel expense settlement system screen 50 as a client screen.
- the user operates the client screen of the travel expense settlement system, and inputs information to each input item (settlement date, domestic and overseas, departure date, export control, business trip destination, etc.) of the travel expense settlement system screen 50, and the client PC 10 displays Accept input operations.
- the client PC 10 displays an error screen 60 including an inquiry button 61 as a client screen.
- the client PC 10 When the client PC 10 accepts a pressing operation of the inquiry button 61 by the user on the error screen 60, the client PC 10 transmits the currently displayed error screen 60 to the log recording / reproducing server 40 as client screen information.
- the log recording / reproducing server 40 When the log recording / reproducing server 40 receives the client screen information of the error screen 60, the log recording / reproducing server 40 records the received error screen 60 information and notifies the operator terminal 70 managed by the operator that an error has occurred.
- the operator terminal 70 displays an error screen 60 that is currently displayed on the client PC 10 in which an error has occurred and is recorded in the log recording / reproducing server 40 by an operator's operation.
- the cause of the error is an input operation on the travel expense settlement system screen 50
- information that the operator wants to know does not exist on the error screen 60 but exists on the travel expense settlement system screen 50.
- the operator needs to ask the user for an explanation of the user's operation content on the travel expense settlement system screen 50, but it is difficult for the user to explain the operation content.
- the log recording / reproducing server 40 is operated by a user operation (timing for transmitting the client screen information to the log recording / reproducing server 40 to the client PC 10 based on the recorded client screen information, operation information, and the like). Trigger operation) is determined. Based on the recorded client screen information and operation information, the log recording / reproducing server 40 uses, as a trigger operation, an operation that is likely to cause a specific state (for example, an error) in the business Web server 20 and the client PC 10. decide. The log recording / reproducing server 40 acquires a client screen displayed on the client PC 10 when the client PC 10 receives a trigger operation.
- the client PC 10 performs the input operation of the item “departure date” on the travel expense settlement system screen 50.
- the information on the travel expense settlement system screen 50 reflecting the input operation is transmitted to the log recording / reproducing server 40 as client screen information. Since the log recording / reproducing server 40 can acquire information on the travel expense settlement system screen 50 reflecting the input operation of the item “departure date”, the client screen that the operator wants to know can be displayed on the operator terminal 70. As a result, the operator can quickly investigate the cause of the error, and can accurately support the user.
- the log recording / reproducing server 40 since the log recording / reproducing server 40 records the client screen information when a trigger operation that is likely to cause a specific state is received, the recording capacity for recording the client screen information can be reduced. In addition, since the log recording / reproducing server 40 automatically determines the trigger operation based on the client screen information and the operation information, technical knowledge and know-how regarding the Web application are not required for the administrator. Furthermore, the trigger operation is not set in advance in the log recording / reproducing server 40, but the log recording / reproducing server 40 determines the trigger operation based on the client screen information and the operation information at a predetermined timing. The trigger operation can be determined according to how the Web application is used.
- the function of the business Web server 20 and the function of the log recording / playback server 40 may be implemented in one computer.
- the business Web server 20 is implemented.
- a computer having the function of the server 20 and the function of the log recording / reproducing server 40 will be described as the server 90 (for example, see FIG. 2), but the present invention is not limited to this.
- FIG. 2 is a first sequence diagram showing an outline of the embodiment of the present invention.
- FIG. 2 illustrates a case where an error occurs on the server 90 side when this embodiment is applied to an information processing system.
- the client PC 10 When the client PC 10 receives a user's predetermined operation on the client screen (201), the client PC 10 transmits a request to the server 90 (202).
- This request includes data necessary for the operation of the application 91 executed by the server 90 to provide the business.
- the predetermined operation in which the client PC 10 transmits a request is an operation of a login button when the client screen is a login screen.
- the client PC 10 transmits a login request including the user ID and password input by the user to the server 90.
- the application 91 executed by the server 90 transmits an ACK of the received request to the client PC 10 (203). Then, the application 91 executes processing corresponding to the received request, generates a screen script for causing the client PC 10 to display a client screen corresponding to the processing result, and transmits the generated screen script to the client PC 10 (204) ).
- the screen script generated by the application 91 is described in a language (for example, HTML) that can be interpreted by the browser 11.
- the browser 11 executes the received screen script and displays a client screen corresponding to the received screen script.
- the client screen that was initially displayed on the client PC 10 transitions to the client screen that corresponds to the screen script transmitted in the process of step 204.
- the browser 11 when the browser 11 receives a user operation on the currently displayed client screen (205), the browser 11 stores the received user operation as an operation log, and changes the client screen based on the received user operation.
- the browser 11 When the browser 11 receives a predetermined operation on the displayed client screen (206), the browser 11 transmits a request to the server 90 (207).
- the application 91 transmits an ACK corresponding to the received request to the client PC 10 (208), and executes the process corresponding to the received request. To do. In FIG. 2, it is assumed that an error occurs during the execution of the process by the application 91.
- the application 91 generates a screen script for displaying an error screen on the client PC 10, and transmits the generated screen script to the client PC 10 (209).
- the browser 11 displays an error screen as the client screen. Then, the user of the client PC 10 looks at the error screen, recognizes that an error has occurred, and makes an inquiry to the help desk on the error screen (210).
- the server 90 Since the client PC 10 transmits only the data necessary for the operation of the application 91 when transmitting a request in the processing of steps 202 and 207, the server 90 performs an operation causing an error and the client at the time of the operation. Screen information is not stored. Therefore, the server 90 cannot display a screen that the help desk operator wants to know.
- the client PC 10 when the operation received by the client PC 10 in the process of step 206 is determined as the trigger operation, the client PC 10 receives the client screen information and the operation log when receiving the trigger operation in the process of step 206. Send to server 90. As a result, the server 90 can obtain a screen that the help desk operator wants to know.
- the server 90 shown in FIG. 2 generates client screen information and operation information (specifically, acquired so far) when an error occurs in the application 91 and a screen script for displaying the error occurrence screen on the client PC 10 is generated.
- the trigger operation is determined based on the client screen information, the operation information, and a screen script table 520 (to be described later).
- FIG. 3 is a second sequence diagram showing an outline of the embodiment of the present invention.
- FIG. 3 illustrates a case where an error occurs on the client PC 10 side when this embodiment is applied to an information processing system.
- the same processes as those shown in FIG. 3 the same processes as those shown in FIG.
- the browser 11 of the client PC 10 accepts a user operation after accepting a user operation in the process of step 205 (301).
- the browser 11 displays an error screen (302).
- the browser 11 transmits client screen information, which is information on the currently displayed error screen, and an operation log to the server 90 (303).
- the server 90 may display a screen that the help desk operator wants to know. Can not.
- the client PC 10 when the operation received by the client PC 10 in the process of step 301 is determined as the trigger operation, the client PC 10 receives the trigger operation in the process of step 301 and displays the client screen information and the operation log. Send to server 90. As a result, the server 90 can obtain a screen that the help desk operator wants to know.
- the server 90 shown in FIG. 3 receives client screen information that is error screen information from the client PC 10, the server 90 performs a trigger operation based on the client screen information, operation information, and screen script table 520 acquired so far. decide.
- FIG. 4 is a functional block diagram of the client PC 10 according to the embodiment of this invention.
- the client PC 10 includes a Web application execution unit (browser) 11 and a communication unit 12.
- the Web application execution unit 11 generates a client screen by executing the screen script 500 transmitted by the server 90, and displays the generated client screen.
- the web application execution unit 11 receives a user operation on the client screen.
- the communication unit 12 is an interface for connecting the client PC 10 to the network 80.
- the Web application execution unit 11 includes an operation reception unit 111, a screen script reception / update unit 112, a screen script execution unit 113, and a screen information generation / display unit 114.
- the operation reception unit 111 receives a user operation on the client screen displayed by the client PC 10.
- the screen script reception / update unit 112 receives the screen script 500 received by the communication unit 12 and updates the screen script 500 to be received as the screen script to be executed.
- the screen script execution unit 113 executes the screen script 500.
- the screen information generation display unit 114 generates client screen information 13 based on the execution result of the screen script 500 by the screen script execution unit 113, and displays the generated client screen information 13 as a client screen.
- the screen script 500 includes a business unit 501 that is a script related to a business provided by the server 90 to the client PC 10 and a client that transmits the client screen information 13 and the operation history 14 to the server 90 when the client PC 10 receives a trigger operation.
- Screen information transmission unit 510 (see FIG. 5).
- the client screen information transmission unit 510 includes an operation information recording unit 511, an operation event determination unit 512, a screen information recording unit 513, a help desk inquiry unit 514, a data transmission unit 515, and trigger operation specifying information 516.
- the operation information recording unit 511 acquires the user operation received by the operation receiving unit 111 and records the acquired user operation as an operation history 14 in a storage area (not shown) of the client PC 10.
- the operation event determining unit 512 refers to the trigger operation specifying information 516 and determines whether or not the user operation acquired by the operation information recording unit 511 is a trigger operation specified by the trigger operation specifying information 516.
- the screen information recording unit 513 acquires the client screen information 13 generated by the screen information generation display unit 114, and acquires the acquired client screen information 13 Is recorded in a storage area (not shown) of the client PC 10.
- the help desk inquiry unit 514 When the help desk inquiry unit 514 receives a pressing operation by the user of the help desk inquiry button included in the client screen, the help desk inquiry unit 514 causes the screen information recording unit 513 to acquire the client screen information 13, and the operator disposed at the client PC 10 and the help desk. A terminal 70 is connected.
- the operation event determination unit 512 determines that the user operation is a trigger operation
- the data transmission unit 515 acquires the user operation history 14 on the client screen on which the user has performed the trigger operation from the operation history 14, and The client screen information 13 and the acquired operation history 14 are transmitted to the server 90.
- FIG. 5 is a functional block diagram of the server 90 according to the embodiment of this invention.
- the server 90 includes a Web application execution unit 21, a communication unit 22, an ID generation unit 23, and a client screen information collection unit 400.
- the Web application execution unit 21 executes the application 91 according to the received request, generates a screen script 500, and generates the generated screen script 500 as the client PC 10.
- the communication unit 22 is an interface for connecting the server 90 to the network 80.
- the ID generation unit 23 generates identification information (ID) of the screen script 500 in order to associate the client screen information 13 and the operation history 14 collected from the client PC 10 and the log 24 output by the Web application execution unit 21.
- ID is assigned to the screen script 500 generated by the screen script generation unit 213.
- the client screen information collection unit 400 collects the client screen information 13 and the operation history 14 from the client PC 10, and determines a trigger operation when the state of the client PC 10 and the server 90 becomes a specific state.
- the Web application execution unit 21 includes a request reception unit 211, a request processing unit 212, a screen script generation unit 213, and a screen script transmission unit 214.
- the request reception unit 211 receives a request from the client PC 10 received by the communication unit 22.
- the request processing unit 212 executes processing corresponding to the request by executing the application 91 in response to the request received by the request receiving unit 211. Further, the request processing unit 212 outputs its own operation as a log 24, and the output log 24 is recorded in the log table 240 of the server 90. Details of the log table 240 will be described with reference to FIG.
- the screen script generation unit 213 generates the business unit 501 of the screen script 500 based on the processing result by the request processing unit 212.
- the screen script transmission unit 214 transmits the screen script 500 in which the client screen information transmission unit 510 is inserted into the screen script 500 generated by the screen script generation unit 213 by the script insertion unit 42 to the client PC 10.
- the client screen information collection unit 400 includes a screen script recording unit 41, a script insertion unit 42, a data reception / recording unit 43, a trigger extraction unit 44, a trigger extraction policy setting unit 47, a screen script table 520, a client screen information table 130, an operation It has a history table 140, a trigger operation identification information table 5160, and a trigger extraction policy table.
- the screen script recording unit 41 records the screen script 500 generated by the screen script recording unit 41 in the screen script table 520. Details of the screen script table 520 will be described with reference to FIG.
- the script insertion unit 42 inserts the client screen information transmission unit 510 into the screen script 500 generated by the screen script generation unit 213.
- the screen script transmission unit 214 of the Web application execution unit 21 transmits the screen script 500 in which the client screen information transmission unit 510 is inserted by the script insertion unit 42 to the client PC 10.
- the data reception / recording unit 43 receives the client screen information 13 and the operation history 14 received from the client PC 10 by the communication unit 22, records the received client screen information 13 in the client screen information table 130, and receives the received operation history 14. Is recorded in the operation history table 140. Details of the operation history table 140 will be described with reference to FIG.
- the trigger extraction unit 44 When the trigger extraction unit 44 detects that at least one of the client PC 10 and the server 90 is in a specific state, the trigger extraction unit 44 determines a new trigger operation according to the trigger extraction policy table 48.
- the trigger extraction policy setting unit 47 registers the trigger extraction policy input by the user in the trigger extraction policy table 48.
- a policy for the trigger extraction unit 44 to determine a new trigger operation is registered.
- FIG. 5 the example in which the Web application execution unit 21 and the client screen information collection unit 400 are mounted on the same server 90 has been described. However, as described in FIG. 1, the Web application execution unit 21 and the client screen information The information collection unit 400 may be mounted on a different computer.
- FIG. 6 is a flowchart of overall processing by the information processing system according to the embodiment of this invention.
- the screen script reception / update unit 112 of the client PC 10 receives the screen script 500 transmitted by the server 90 (601).
- the screen script execution unit 113 executes the received screen script 500, and the screen information generation / display unit 114 generates the client screen information 13, and displays the client screen of the generated client screen information 13 (602).
- the operation receiving unit 111 receives the user's operation (603), and the operation information recording unit 511 of the screen script 500 receives the user's operation received by the operation receiving unit 111.
- the operation is recorded as the operation history 14 (604).
- the operation event determining unit 512 of the screen script 500 determines whether or not the user operation received by the operation receiving unit 111 is a trigger operation specified by the trigger operation specifying information 516 included in the screen script 500. (605).
- step 605 When it is determined in step 605 that the user operation is a trigger operation, the screen information recording unit 513 of the screen script 500 acquires the client screen information 13 generated by the screen information generation / display unit 114 (606). ), The data transmission unit 515 transmits the client screen information 13 acquired by the screen information recording unit 513 to the server 90 (607), and proceeds to the processing of step 608. On the other hand, if it is determined in step 605 that the user operation is not a trigger operation, the process proceeds to step 608 without executing steps 606 and 607.
- the client PC 10 determines whether or not the user operation received by the operation receiving unit 111 is an operation (request transmission operation) preset as an operation for transmitting a request to the server 90 (608).
- step 608 If it is determined in step 608 that the user operation is not a request transmission operation, the screen information generation / display unit 114 causes the client screen information 13 to reflect the user operation received by the operation reception unit 111 on the client screen. (609), and the process returns to step 603.
- step 608 if it is determined in step 608 that the user operation is a request transmission operation, the data transmission unit 515 transmits the operation history 14 corresponding to the client screen information 13 for which the request transmission operation has been performed to the server 90. (610), a request corresponding to the request transmission operation is transmitted to the server 90 (611), and the process returns to step 601.
- the server 90 waits for processing until the request reception unit 211 receives a request transmitted from the client PC 10 (621).
- the request processing unit 212 executes the application 91 corresponding to the received request (622), and outputs the log 24 indicating its own operation (623).
- the output log 24 is recorded in the log table 240.
- the ID generation unit 23 generates an ID to be assigned to the screen script 500 (624), and the screen script generation unit 213 generates the screen script 500 based on the processing result of the request processing unit 212 (625).
- the screen script recording unit 41 of the client screen information collection unit 400 records the screen script 500 generated by the screen script generation unit 213 in the screen script table 520 (626).
- the script insertion unit 42 of the client screen information collection unit 400 inserts the client screen information transmission unit 510 into the screen script 500 recorded by the screen script recording unit 41 (627), and the screen script transmission unit 214 replaces the business unit 501.
- the screen script 500 including the client screen information transmission unit 510 is transmitted to the client PC 10 (628).
- the trigger extraction unit 44 of the client screen information collection unit 400 refers to the log table 240, the screen script table 520, and the operation history table 140, and monitors whether the client PC 10 and the server 90 are in a specific state (631). ). Then, when the client PC 10 and the server 90 are in a specific state, the trigger extraction unit 44 refers to the client screen information 13 and the operation history 14, determines a new trigger operation (632), and returns to the process of step 631. .
- the data reception / recording unit 43 of the client screen information collection unit 400 receives the client screen information 13 and the operation history 14 transmitted from the client PC 10 in the processes of steps 607 and 610 (641). Then, the data reception / recording unit 43 records the received client screen information 13 in the client screen information table 130 and records the received operation history 14 in the operation history table 140 (642).
- FIG. 7 is an explanatory diagram of the screen script table 520 according to the embodiment of this invention.
- the screen script table 520 includes a generation time 701, an ID 702, a screen URL 703, a script 704, and a previous screen ID 705.
- the generation time 701 the time when the screen script 500 is generated is registered.
- ID 702 an ID given to the screen script 500 by the ID generation unit 23 is registered.
- screen URL 703 the URL of the access destination is registered.
- Screen scripts 500 having the same URL registered in the screen URL 703 generate the same client screen.
- the contents of the screen script 500 are registered in the script 704.
- an ID assigned to the screen script 500 immediately before the screen script 500 is registered.
- FIG. 8 is an explanatory diagram of the operation history table 140 according to the embodiment of this invention.
- the operation history table 140 includes an occurrence time 801, an ID 802, a screen URL 803, an operation event 804, and accompanying information 805.
- the time when the operation receiving unit 111 of the client PC 10 receives a user operation is registered.
- Registered in the ID 802 is an ID assigned to the screen script 500 being executed when the operation receiving unit 111 receives a user operation.
- the screen URL 803 the access destination URL of the screen script 500 identified by the ID registered in the ID 802 is registered.
- the operation event 804 the type of user operation received by the operation receiving unit 111 is registered.
- the accompanying information 805 information accompanying the user operation received by the operation receiving unit 111 is registered. For example, the coordinate information 805 of the record in which “mouse movement” is registered in the operation event 804 is registered in the accompanying information 805 in the record in which “button pressed” is registered in the operation event 804. The type of the operated button is registered.
- FIG. 9 is an explanatory diagram of the log table 240 according to the embodiment of this invention.
- the log table 240 includes an occurrence time 901, an ID 902, an event 903, and accompanying information 904.
- the time when the log 24 is output from the request processing unit 212 is registered.
- the ID 902 the ID of the screen script 500 included in the request corresponding to the process being executed by the request processing unit 212 when the request processing unit 212 outputs the log 24 is registered.
- the client PC 10 transmits the request including the ID and screen URL of the screen script 500 being executed.
- the type of processing being executed by the request processing unit 212 when the request processing unit 212 outputs the log 24 is registered.
- a screen URL included in a request corresponding to a process being executed by the request processing unit 212 when the request processing unit 212 outputs the log 24 is registered.
- FIG. 10 is an explanatory diagram of the trigger operation specifying information table 5160 according to the embodiment of this invention.
- the trigger operation specifying information table 5160 includes a screen URL 1001, an operation event 1002, and accompanying information 1003.
- the URL of the access destination of the screen script 500 is registered in the screen URL 1001.
- the type of operation to be a trigger operation is registered.
- the accompanying information 1003 information accompanying the trigger operation is registered.
- the type of button to be operated is registered in the accompanying information 1003 of the record in which “button press” is registered in the operation event 1002.
- FIG. 11 is an explanatory diagram of the trigger extraction policy table 48 according to the embodiment of this invention.
- the trigger extraction policy table 48 includes a type 1101, a screen URL / event 1102, a search range 1103, and an extraction method 1104.
- the type 1101 a type of timing at which the trigger extraction unit 44 starts executing the trigger extraction process is registered.
- the screen URL / event 1102 includes a screen URL of the screen script 500 being executed on the client PC 10 when a user operation (trigger extraction operation) for starting execution of the trigger extraction process by the trigger extraction unit 44 is performed, or When the request processing unit 212 outputs the log 24, the type of processing being executed by the request processing unit 212 is registered.
- the search range 1103 the search range of the client screen information 13 acquired when the trigger operation is determined is registered.
- the type of trigger extraction method for determining the trigger operation and the threshold value used for the trigger extraction method are registered.
- the trigger extraction method of the present embodiment includes a trigger extraction method a and a trigger extraction method b, and details will be described with reference to FIGS. 19, 20, 24 and 25.
- the trigger extraction process execution start timing is the timing at which the trigger extraction unit 44 detects that at least one of the client PC 10 and the server 90 is in a specific state.
- the specific state of the client PC 10 is a case where the client PC 10 receives a trigger extraction operation on a specific screen (see FIG. 13)
- the specific state of the server 90 is a specific state for the server 90 to display the specific screen. This is the case when the screen script 500 is generated (see FIG. 12) or when the server 90 outputs a specific log 24 (see FIG. 14).
- FIG. 12 is an explanatory diagram of the trigger extraction process executed when the server 90 according to the embodiment of this invention generates a specific screen script 500.
- the request processing unit 212 of the server 90 activates the application 91 and starts processing of the application 91 (1201).
- the operation reception unit 111 of the client PC 10 receives a specific user operation
- the client PC 10 transmits a request to the server 90 (1202).
- Specific user operations include, for example, a click operation of a link to the application 91 on the browser 11 and an input operation of the URL of the application 91 on the browser 11.
- the request reception unit 211 of the server 90 receives a request transmitted from the client PC 10
- the process corresponding to the request received by the request processing unit 212 is executed (1203), and the screen script 500 is generated based on the execution result. (1204), and the generated screen script 500 is transmitted to the client PC 10.
- the server 90 executes the application 91 in response to a request from the client PC 10 and repeatedly executes a process of generating the screen script 500 based on the execution result.
- the screen script generation unit 213 When an error occurs during the execution of these processes, the screen script generation unit 213 generates a screen script 500 for displaying the error screen as a client screen (1205). Since the generation of the screen script 500 for the error screen is registered in the trigger extraction policy table 48, the trigger extraction unit 44 detects the specific screen, detects that the server 90 is in the specific state (1206), and triggers An extraction process is executed (1207). In this trigger extraction process, “aaa operation on xxx screen” is extracted as the trigger operation.
- the server 90 After executing the trigger extraction process in the process of step 1207, the server 90 repeatedly executes the generation process of the screen script 500 based on the execution result of the process according to the request from the client PC 10.
- the script insertion unit 42 includes the client screen information transmission unit including the trigger operation specifying information indicating “aaa operation on the xxx screen”. 510 is inserted into the screen script 500 generated in step 1208 (1209), and the screen script 500 is transmitted to the client PC 10 (1210).
- the client PC 10 executes the screen script 500 and displays the xxx screen as a client screen (1211).
- the operation accepting unit 111 accepts an aaa operation while the xxx screen is displayed (1212)
- the client screen information 13 of the client screen being displayed is acquired, and the acquired client screen information 13 is transmitted to the server 90 ( 1213).
- the server 90 When the server 90 receives the client screen information 13, the server 90 stores the received client screen information 13 in the client screen information table 130 (1214).
- the trigger extraction unit 44 determines that the server 90 is in a specific state and determines a new trigger operation.
- FIG. 13 is an explanatory diagram of a trigger extraction process executed when the client PC 10 according to the embodiment of this invention receives a trigger extraction operation on a specific screen. Of the processes shown in FIG. 13, the same processes as those shown in FIG.
- the server 90 transmits the screen script 500 generated in step 1204 to the client PC 10 (1301).
- the client PC 10 When the client PC 10 receives the screen script 500 transmitted in step 1301, the client PC 10 executes the screen script 500 and displays a client screen (1302). Then, the operation reception unit 111 of the client PC 10 receives a user operation on the displayed client screen, and records the received user operation in the operation history 14 (1303). Then, the client PC 10 updates the client screen information 13 to reflect the user operation received by the operation receiving unit 111 (1304), but it is assumed that an error occurs in this update process.
- the client PC 10 receives a pressing operation of the help desk inquiry button included in the client screen being displayed, and records the received pressing operation in the operation history 14 (1305). Since the pressing operation of the help desk inquiry button is registered as the trigger operation in the trigger operation specifying information shown in FIG. 10, the client PC 10 detects the trigger operation, acquires the client screen information 13 being displayed, and acquires it. The client screen information 13 is transmitted to the server 90 (1306).
- the help desk inquiry button is displayed on any client screen, and the pressing operation of the help desk inquiry button is a trigger operation.
- the server 90 When the server 90 receives the client screen information 13 transmitted in step 1306, the server 90 records the received client screen information 13 in the client screen information table 130 (1307).
- the received client screen information 13 is transmitted by pressing a help desk inquiry button, and includes notification of help desk inquiry. Since the notification of the help desk inquiry is registered in the trigger extraction policy table 48 shown in FIG. 11, the trigger extraction unit 44 determines that the client PC 10 has accepted the trigger extraction operation, and executes trigger extraction processing (1308). In this trigger extraction process, “bbb operation on the zzz screen” is extracted as the trigger operation.
- the server 90 After executing the trigger extraction process in the process of step 1308, the server 90 repeatedly executes the generation process of the screen script 500 based on the execution result of the process according to the request from the client PC 10.
- the script insertion unit 42 includes the client screen information transmission unit including trigger operation specifying information indicating “bbb operation on the zzz screen”. 510 is inserted into the screen script 500 generated in step 1308 (1310), and the screen script 500 is transmitted to the client PC 10 (1311).
- the client PC 10 executes the screen script 500 and displays the zzz screen as a client screen (1312).
- the operation reception unit 111 receives a bbb operation while the zzz screen is displayed (1313), the client screen information 13 of the client screen being displayed is acquired, and the acquired client screen information 13 is transmitted to the server 90 ( 1314).
- the server 90 When the server 90 receives the client screen information 13, the server 90 stores the received client screen information 13 in the client screen information table 130 (1315).
- the trigger extraction unit 44 determines that the client PC 10 has entered a specific state, and determines a new trigger operation.
- FIG. 14 is an explanatory diagram of trigger extraction processing executed when the server 90 according to the embodiment of the present invention outputs a specific log 24 according to the embodiment of the present invention. Among the processes shown in FIG. 14, the same processes as those shown in FIG.
- the log 24 is output. Assume that the request processing unit 212 outputs a log 24 indicating an error (1401). In this case, since the output of the log 24 indicating the error is registered as the specific state of the server 90 in the trigger extraction policy table 48 shown in FIG. 11, the trigger extraction unit 44 indicates that the server 90 has entered the specific state. Is detected (1402). Then, the trigger extraction unit 44 executes trigger extraction processing in step 1207. The subsequent processing is the same as the processing shown in FIG.
- the trigger extraction unit 44 determines that the server 90 is in a specific state, and determines a new trigger operation.
- FIG. 15 is a specific explanatory diagram of a trigger extraction process executed when the server 90 according to the embodiment of the present invention generates a specific screen script 500.
- the same processes as those shown in FIG. 15 are identical processes as those shown in FIG.
- the screen script generation unit 213 When the screen script generation unit 213 generates the screen script 500 of the xxx screen in the process of step 1204, the screen script generation unit 213 adds a new record to the screen script table 520, and the ID generation unit 23 selects the screen script. An ID “003” assigned to 500 is generated. Then, the screen script generation unit 213 registers the generation time of the screen script 500 in the generation time 701 of the added record, registers the generated ID “003” in the ID 702 of the added record, and the screen URL 703 of the added record. The URL to be the access destination of the screen script 500 is registered, and the contents of the screen script 500 are registered in the script 704 of the added record. Since the screen script 500 generated immediately before the screen script 500 does not exist, the screen script generation unit 213 registers nothing in the previous screen ID 705 of the added record.
- the screen script generation unit 213 When the screen script generation unit 213 generates the screen script 500 of the error screen in the process of step 1205, the screen script generation unit 213 adds a new record to the screen script table 520, and the ID generation unit 23 displays the screen script.
- An ID “011” to be assigned to 500 is generated.
- the screen script generation unit 213 registers the generation time of the screen script 500 in the generation time 701 of the added record, registers the generated ID “011” in the ID 702 of the added record, and adds the screen URL 703 of the added record.
- the URL to be the access destination of the screen script 500 is registered, and the contents of the screen script 500 are registered in the script 704 of the added record.
- the screen script generation unit 213 registers the ID “010” of the screen script generated immediately before the screen script 500 in the previous screen ID 705 of the added record.
- the trigger extraction unit 44 monitors whether or not the URL that is the access destination of the specific screen is registered in the screen URL 703 of the screen script table 520.
- “/aaa/bbb/error.html” is registered in advance as the URL that is the access destination of the specific screen. Accordingly, since “/aaa/bbb/error.html” is registered in the screen URL 703 of the record added to the screen script table 520 in the process of step 1205, the trigger extracting unit 44 performs the specific screen in the process of step 1206. Is detected.
- the trigger extraction unit 44 determines that the server 90 is in the specific state, and executes the trigger extraction process in the process of step 1207. Specifically, the trigger extraction unit 44 triggers using the search range 1103 and the extraction method 1104 of records in which “/aaa/bbb/error.html” is registered in the screen URL / event 1102 of the trigger extraction policy table 48. Execute the extraction process. In this trigger extraction process, the pressing operation of the determination button on the client display screen by the screen script 500 whose access destination URL is “/aaa/bbb/xxx.html” is determined as the trigger operation.
- the trigger extraction unit 44 adds a new record to the trigger operation specifying information table 5160, registers “/aaa/bbb/xxx.html” in the screen URL 1001 of the added record, and sets “ “Button press” is registered, and “button,“ decision ”” is registered in the accompanying information 1003.
- the trigger extraction unit 44 refers to the screen script table 520, detects the generation of a specific screen, detects that the server 90 is in a specific state, and executes trigger extraction processing. In addition, the trigger extraction unit 44 executes trigger extraction processing based on the trigger extraction policy table 48 and registers the trigger operation determined in the trigger extraction processing in the trigger identification information table 5160.
- FIG. 16 is a specific explanatory diagram of the trigger acquisition process according to the embodiment of the present invention. Of the processes shown in FIG. 16, the same processes as those shown in FIG.
- the screen script generation unit 213 generates a screen script 500 whose access destination URL is “/aaa/bbb/xxx.html”.
- the script insertion unit 42 refers to the trigger operation identification information table 5160 and inserts a script to be the client screen information transmission unit 510 into the screen script 500 generated by the screen script generation unit 213. To do. Specifically, the script insertion unit 42 inserts a script for displaying the help desk inquiry button 1601 on the client screen. Further, the script insertion unit 42 acquires the client screen information 13 being displayed when the help desk inquiry button 1601 is pressed, and transmits the acquired client screen information 13 to the server 90. Insert the script.
- the script insertion unit 42 displays the client screen that is displayed when the enter button 1602 is pressed on the client screen displayed by the screen script 500 in which the URL of the access destination is “/aaa/bbb/xxx.html”.
- Information 13 is acquired, and a script serving as a client screen information transmission unit 510 that transmits the acquired client screen information 13 to the server 90 is inserted.
- the screen script transmission unit 214 transmits the screen script 500 into which the script is inserted by the script insertion unit 42 to the client PC 10.
- step 1211 the screen script execution unit 113 of the client PC 10 executes the received screen script 500, and the screen information generation / display unit 114 displays the client screen 1600 based on the execution result of the screen script execution unit 113.
- the client screen 1600 displayed in the process of step 1211 includes a help desk inquiry button 1601 and a determination button 1602.
- step 1212 the operation reception unit 111 receives a pressing operation of the determination button 1602 by the user, and the operation information recording unit 511 records the operation.
- the operation event determination unit 512 determines that the operation received in the process of step 1212 is a trigger operation, and in the process of step 1213, the data transmission unit 515 displays the client screen information 13 of the client screen 1600 being displayed.
- the acquired client screen information 13 is transmitted to the server 90.
- step 1214 when the server 90 receives the client screen information 13 transmitted in the process of step 1213, the server 90 records the received client screen information 13 in the client screen information table 130.
- the script insertion unit 42 refers to the trigger operation specifying information table 5160 and inserts the client screen information transmission unit 510 into the screen script 500 generated by the screen script generation unit 213. If the client screen information transmission unit 510 determines that the trigger operation has been performed, the client PC 10 acquires the client screen information 13 of the currently displayed client screen, and transmits the acquired client screen information 13 to the server 90. .
- FIG. 17 is an explanatory diagram of a specific example of the trigger extraction process executed when the client PC 10 according to the embodiment of this invention receives a trigger extraction operation on a specific screen.
- the same processes as those shown in FIG. 17 are identical processes as those shown in FIG.
- step 1305 the operation reception unit 111 of the client PC 10 receives a pressing operation of the help desk inquiry button 1601 by the user, and the operation information recording unit 511 records the operation in the operation history 14.
- the client PC 10 Since the pressing operation of the help desk inquiry button 1601 is a trigger operation, the client PC 10 transmits the client screen information 13 of the currently displayed client screen to the server 90 in the process of step 1306.
- the server 90 When the server 90 receives the client screen information 13 by the pressing operation of the help desk inquiry button 1601 of the user, in step 1307, the server 90 records the received client screen information 13 in the client screen information table 130, and the client PC 10 is in a specific state.
- the trigger extraction unit 44 refers to the trigger extraction policy table 48 when the help desk inquiry button is pressed, and executes trigger extraction processing. Specifically, the trigger extraction unit 44 executes trigger extraction processing using the search range 1103 and the extraction method 1104 for records in which “help desk inquiry” is registered in the screen URL / event 1102 of the trigger extraction policy table 48. .
- This trigger extraction process triggers an operation to change the state of the check box “ABC” on the client display screen displayed by the screen script 500 whose access destination URL is “/aaa/bbb/yyy.html” to ON. Determined as operation.
- the trigger extracting unit 44 adds a new record to the trigger operation specifying information table 5160, registers “/aaa/bbb/yyy.html” in the screen URL 1001 of the added record, and sets “ “Check state change” is registered, and “check box,“ ABC ”, ON” is registered in the accompanying information 1003.
- the server 90 detects that the client PC 10 is in a specific state, and executes trigger extraction processing.
- FIG. 18 is an explanatory diagram of a specific example of the trigger extraction process executed when the server 90 according to the embodiment of the present invention outputs the specific log 24.
- the request processing unit 212 When the request reception unit 211 receives a request, the request processing unit 212 outputs a log 24 indicating that the request has been received. In this case, the request processing unit 212 adds a new record to the log table 240, registers the output time of the log 24 in the occurrence time 901 of the added record, and the screen script 500 included in the request received in the ID 902. An ID “003” is registered, an event name “request received” indicating that a request has been received is registered in the event 903, and a screen URL “/aaa/bbb/yyy.html” included in the request is included in the accompanying information 904. Register. In the request, the ID “003” of the screen script 500 for displaying the client screen that has accepted the operation for transmitting the request and the URL (screen URL) “/ aaa / bbb / yyy. html ".
- the request processing unit 212 If an error occurs while the request processing unit 212 executes a process corresponding to a request including the ID “006” of the screen script 500, the request processing unit 212 outputs the log 24 indicating the error in the process of step 1401. To do. In this case, the request processing unit 212 adds a new record to the log table 240, registers the output time of the log 24 in the occurrence time 901 of the added record, and the screen script 500 included in the request received in the ID 902. The ID “006” is registered, the event name “error 1” indicating an error is registered in the event 903, and nothing is registered in the accompanying information 904.
- the trigger extraction unit 44 has registered the output of the event log 24 indicating error 1 in the trigger extraction policy table 48 as the specific state of the server 90, so that the server 90 has entered the specific state. Is detected.
- the trigger extraction unit 44 executes the trigger extraction process with reference to the trigger extraction policy table 48 when the error 24 log 24 is output. Specifically, the trigger extraction unit 44 executes the trigger extraction process using the search range 1103 and the extraction method 1104 for records in which “error 1” is registered in the screen URL / event 1102 of the trigger extraction policy table 48. In this trigger extraction process, the pressing operation of the determination button on the client display screen by the screen script 500 whose access destination URL is “/aaa/bbb/xxx.html” is determined as the trigger operation.
- the trigger extraction unit 44 adds a new record to the trigger operation specifying information table 5160, registers “/aaa/bbb/xxx.html” in the screen URL 1001 of the added record, and sets “ “Button press” is registered, and “button,“ decision ”” is registered in the accompanying information 1003.
- the server 90 detects that the server 90 is in a specific state when the request processing unit 212 outputs the specific log 24, and executes trigger extraction processing.
- FIG. 19 is a schematic explanatory diagram of the trigger extraction method a of the embodiment of the present invention.
- the trigger extraction unit 44 includes the first client screen transition sequence including a predetermined number of client screen information up to a specific screen and the first client screen transition sequence leading to the specific screen.
- the number of operations of the same user operation in the same client screen information is totaled between the second client screen transition sequence including the same client screen information as the screen transition sequence, and a user operation in which the total number of operations is equal to or greater than a threshold is set as a trigger operation decide.
- the user operation that is likely to reach the specific screen is determined as the trigger operation, and thus the server 90 can acquire the client screen information that reflects the user operation that is likely to reach the specific screen.
- the trigger extraction unit 44 refers to the screen URL 703 of the screen script table 520 and detects that a specific screen has occurred (Step 1).
- the trigger extraction unit 44 acquires client screen information from the specific screen detected in Step 1 to the specified range (Step 2). Specifically, the trigger extraction unit 44 selects a record in which the screen URL of the specific screen detected in the screen URL / event 1102 is registered from the records in the trigger extraction policy table 48, and enters the search range 1103 of the selected record. Get the registered number. Then, the trigger extraction unit 44 refers to the screen script table 520 and acquires the screen script 500 existing between the numbers acquired from the screen script 500 of the detected specific screen.
- the client screen information of the specific screen detected in Step 1 and the client screen information by the screen script 500 acquired in Step 2 are referred to as a first client screen transition sequence.
- the trigger extraction unit 44 searches the client screen information other than the client screen information acquired in Step 2 for a second client screen transition sequence including the same client screen information as the first client screen transition sequence acquired in Step 2 ( Step 3).
- the trigger extraction unit 44 refers to the operation history 14 of the same client screen information between the first client screen transition sequence and the second client screen transition sequence, and operates the same operation between the two client screen information. The number of times is totaled (Step 4).
- the trigger extraction unit 44 determines, as a trigger operation, an operation in which the number of operations of the same operation is equal to or greater than a threshold value based on the aggregation result (Step 5).
- the trigger operation determined by the trigger extraction method a is a user operation with a large number of operations in the client screen information up to the specific screen, it is estimated that the user operation has a high possibility of reaching the specific screen.
- FIG. 20 is a schematic explanatory diagram of the trigger extraction method b according to the embodiment of the present invention.
- the trigger extraction unit 44 has the same client screen information as the first client screen transition sequence including a predetermined number of client screen information up to the specific screen and the client screen information other than the specific screen in the first client screen transition sequence.
- the number of operations of the same user operation in the same client screen information is totaled with the third client screen transition sequence including the client screen information, and a user operation whose total number of operations is equal to or less than a threshold is determined as a trigger operation.
- the user operation that is likely to reach the specific screen is determined as the trigger operation, and thus the server 90 can acquire the client screen information that reflects the user operation that is likely to reach the specific screen.
- the trigger extraction unit 44 refers to the screen URL 703 of the screen script table 520 and detects that a specific screen has occurred (Step 1).
- the trigger extraction unit 44 acquires client screen information from the specific screen detected in Step 1 to the specified range (Step 2). Since Step 1 and Step 2 of the trigger extraction method b are the same processing as Step 1 and Step 2 of the trigger extraction method a, a specific description is omitted.
- the trigger extraction unit 44 includes, from the client screen information other than the client screen information acquired in Step 2, the same client screen information except for the client screen information of the specific screen in the first client screen transition sequence acquired in Step 2.
- the 3 client screen transition sequence is searched from the screen script table 520 (Step 3).
- the trigger extraction unit 44 refers to the operation history 14 of the same client screen information between the first client screen transition sequence and the third client screen transition sequence, and operates the same operation between the two client screen information. The number of times is totaled (Step 4).
- the trigger extraction unit 44 determines, as a trigger operation, an operation in which the number of operations of the same operation is equal to or less than a threshold value based on the aggregation result (Step 5).
- the trigger operation determined by the trigger extraction method b is a user operation in which the number of operations is small between the client screen information up to the specific screen and the specific screen, and the same client screen information as the client screen information. . That is, if it is considered that a specific screen is reached because a user operation with a small number of operations is performed, the user operation is estimated to be a user operation with a high possibility of reaching the specific screen.
- the trigger extraction policy setting screen 2100 is displayed on a display device (not shown) by the server 90.
- FIG. 21 is an explanatory diagram of the trigger extraction policy setting screen 2100 according to the embodiment of this invention.
- the trigger extraction policy setting screen 2100 includes a search range 201, a screen 2102, an operation 2103, a log 2104, an extraction method a setting field 2111, an extraction method b setting field 2112, and a combination method setting field 2113.
- the search range 2101 is a field for setting the range of the client screen information 13 acquired when the trigger operation is determined.
- a client screen displayed on the client PC 10 by the screen script 500 stored in the screen script table 520 is displayed.
- the operation 2103 displays the user operation accepted on the client screen displayed on the screen 2102.
- the server 90 displays the operation indicated by the record registered in the ID of the screen script 500 corresponding to the client screen displayed on the screen 2102 among the records registered in the operation history table 140 in the client screen. Is displayed as the user operation accepted at.
- a log 24 indicating the operation of the request processing unit 212 that is executing the process corresponding to the request including the ID of the screen script 500 that displays the client screen displayed on the screen 2102 is displayed.
- the server 90 displays the log 24 indicated by the record in which the ID of the screen script 500 corresponding to the client screen displayed on the screen 2102 is registered in the ID 902 among the records registered in the log table 240. .
- the user selects a specific state of the server 90 and the client PC 10 that is the start timing of trigger extraction processing from the information displayed on the screen 2102, the operation 2103, and the log 2104 of the trigger extraction policy setting screen 2100.
- the server 90 refers to the screen script table 520, and the screen URL 703 of the record in which the ID of the screen script 500 corresponding to the client screen selected in the ID 702 is registered. URL registered in. Then, the server 90 adds a new record to the trigger extraction policy table 48, registers screen generation in the added record type 1101, and registers the acquired URL in the screen URL / event 1102 of the added record.
- the server 90 adds a new record to the trigger extraction policy table 48, registers a client notification in the added record type 1101, and adds it.
- the selected user operation is registered in the screen URL / event 1102 of the record.
- the server 90 adds a new record to the trigger extraction policy table 48, registers the log in the added record type 1101, and adds the added record.
- the event indicated by the selected log is registered in the screen URL / event 1102.
- the extraction method a setting field 2111 includes a check box for determining whether or not to perform trigger extraction processing using the trigger extraction method a, and a field for setting a threshold used when a trigger operation is extracted using the trigger extraction method a. Including.
- the extraction method b setting field 2112 includes a check box for determining whether or not to execute trigger extraction processing using the trigger extraction method b, and a field for setting a threshold used when a trigger operation is extracted using the trigger extraction method b. Including.
- the trigger operation extracted by the trigger extraction method a and the trigger extraction method b This is a field that allows the user to select how to combine the trigger operations extracted in.
- the same trigger operation is determined as the trigger operation among the trigger operation extracted by the trigger extraction method a and the trigger operation extracted by the trigger extraction method b.
- the trigger operation extracted by the trigger extraction method a and the trigger operation extracted by the trigger extraction method b are determined as the trigger operation.
- the third client screen displayed on the screen 2102 is selected as the specific screen. Then, the second client screen selected from the client screen selected by the user is selected as the search range 2101.
- the check box of the extraction method a setting field 2111 is checked, and “5” is selected as the threshold used for the trigger extraction process by the trigger extraction method a.
- the determination button 2114 When the determination button 2114 is pressed, the contents selected on the trigger extraction policy setting screen 2100 are registered in the trigger extraction policy table 48.
- FIG. 22 is an explanatory diagram of the trigger extraction policy setting screen 2100 according to the embodiment of this invention.
- the log displayed in the log 2104 is selected as a specific state. Then, the second to the second client screen corresponding to the log selected by the user is selected as the search range 2101.
- the check box of the extraction method b setting field 2112 is checked, and “4” is selected as the threshold value used in the trigger extraction process by the trigger extraction method b.
- the determination button 2114 When the determination button 2114 is pressed, the contents selected on the trigger extraction policy setting screen 2100 are registered in the trigger extraction policy table 48.
- FIG. 23 is an overall flowchart of trigger extraction processing according to the embodiment of this invention.
- the trigger extraction unit 44 monitors whether or not at least one of the server 90 and the client PC 10 is in a specific state (2301).
- the trigger extraction unit 44 extracts the record corresponding to the specific state detected in the trigger extraction policy table 48.
- the execution of the trigger extraction process by the trigger extraction method a is registered, the execution of the trigger extraction process by the trigger extraction method b is registered, or the trigger extraction process by the combination of the trigger extraction method a and the trigger extraction method b. It is determined whether execution is registered (2302).
- step 2302 If it is determined in step 2302 that execution of the trigger extraction process by the trigger extraction method a is registered in the extraction method 1104, the trigger extraction unit 44 executes the trigger extraction process by the trigger extraction method a (2303). ).
- the trigger extraction process by the trigger extraction method a will be described in detail with reference to FIG. Then, the trigger extracting unit 44 registers the trigger operation extracted in the process of step 2303 in the trigger operation specifying information table 5160 (2304), and returns to the process of step 2301.
- step 2302 If it is determined in step 2302 that execution of the trigger extraction method b by the trigger extraction method b is registered in the extraction method 1104, the trigger extraction unit 44 executes the trigger extraction process by the trigger extraction method b (2305). ).
- the trigger extraction process by the trigger extraction method b will be described in detail with reference to FIG.
- step 2304 the trigger extraction unit 44 registers the trigger operation extracted in step 2305 in the trigger operation identification information table 5160, and returns to step 2301.
- step 2302 If it is determined in step 2302 that execution of the trigger extraction process by the combination of the trigger extraction method a and the trigger extraction method b is registered, the trigger extraction unit 44 executes the trigger extraction process by the trigger extraction method a (2306), trigger extraction processing by the trigger extraction method b is executed (2307). Next, the trigger extraction unit 44 determines whether the combination method is “and” (2308). When it is determined in the process of step 2308 that the combination method is “and”, the trigger extraction unit 44 is the same among the trigger operation extracted by the trigger extraction method a and the trigger operation extracted by the trigger extraction method b. The trigger operation is registered in the trigger operation specifying information table 5160 (2309), and the process returns to step 2301.
- step 2308 If it is determined in step 2308 that the combination method is not “and”, that is, if the combination method is “or”, the trigger extraction unit 44 uses the trigger operation and trigger extraction method extracted by the trigger extraction method a.
- the trigger operation extracted in b is registered in the trigger operation specifying information table 5160 (2310), and the process returns to Step 2301.
- FIG. 24 is a flowchart of the trigger extraction process by the trigger extraction method a according to the embodiment of the present invention.
- the trigger extraction unit 44 acquires the number of client screen information registered in the search range 1103 of records corresponding to the specific state detected by the processing of step 2301 of the trigger extraction policy table 48, and the first client screen transition A column is acquired (2401).
- Step 2301 The case where the specific state detected in the process of Step 2301 is a state where the server 90 has generated the specific screen script 500 will be specifically described.
- the trigger extraction unit 44 acquires a record in which the ID of a specific screen script 500 is registered in the ID 702 of the screen script table 520. Then, the trigger extraction unit 44 acquires records that exist between the acquired records and the number registered in the search range 1103 of the trigger extraction policy table 48. Then, the trigger extraction unit 44 acquires, as a first client screen transition sequence, a transition of client screen information that is displayed on the client PC 10 by the screen script 500 specified by the acquired record.
- the processing in step 2401 will be specifically described in the case where the specific state detected in the processing in step 2301 is a state in which a specific user operation is accepted by the client PC 10. It is assumed that a script for transmitting a notification to that effect to the server 90 when the client PC 10 accepts a specific user operation is inserted into the screen script 500 that enables the specific user operation.
- the notification that the specific user operation has been received includes the ID of the screen script 500 being executed by the client PC 10 when the user operation has been received.
- the trigger extraction unit 44 acquires a record in which the ID of the screen script 500 included in the notification that the specific user operation has been received is registered in the ID 702 of the screen script table 520. Subsequent processing is the same as the case where the state in which the server 90 generated the specific screen script in the processing of Step 2301 is detected as the specific state, and thus description thereof is omitted.
- step 2401 the processing in step 2401 will be specifically described in the case where the specific state detected in the processing in step 2301 is a state in which the server 90 has output the specific log 24.
- the trigger extraction unit 44 acquires a record in which the ID of the screen script 500 included in the log 24 output by the request processing unit 212 of the server 90 is registered in the ID 702 of the screen script table 520. Subsequent processing is the same as the case where the state in which the server 90 generated the specific screen script in the processing of Step 2301 is detected as the specific state, and thus description thereof is omitted.
- the trigger extraction unit 44 acquires, as a second client screen information transition sequence, a transition of client screen information that is the same transition as the first client screen transition sequence acquired in the process of Step 2401 (2402).
- the trigger extraction unit 44 arranges the URLs registered in the screen URL 703 of the screen script table 520 so that the URLs of the screen scripts 500 constituting the first client screen transition sequence acquired in the process of Step 2401 are arranged. Get the same records as. Then, the trigger extraction unit 44 acquires, as a second client screen transition sequence, a transition of client screen information that is displayed on the client PC 10 by the screen script 500 specified by the acquired record group.
- the trigger extraction unit 44 calculates the number of operations of the same user operation on the same client screen. Aggregate (2403).
- the trigger extraction unit 44 identifies the screen scripts 500 having the same URL between the screen script 500 configuring the first client screen transition sequence and the screen script 500 configuring the second client screen transition sequence. To do. Then, the trigger extraction unit 44 acquires an operation event 804 and accompanying information 805 of a record in which the ID 802 of the operation history table 140 matches the ID of each screen script 500. The trigger extraction unit 44 performs an operation operation specified by the information registered in the operation event 804 and the accompanying information 805 when the operation event 804 acquired by each screen script 500 matches the information registered in the accompanying information 805. Increment the number of times.
- the trigger extraction unit 44 determines an operation in which the number of operations counted in the process of Step 2403 is equal to or greater than a threshold value as a trigger operation (2404), and ends the process.
- FIG. 25 is a flowchart of the trigger extraction process by the trigger extraction method b according to the embodiment of the present invention. Of the processes shown in FIG. 25, the same processes as those shown in FIG.
- the trigger extraction unit 44 performs third transition of client screen information in which the client screen information other than the client screen information is the same transition by the screen script 500 corresponding to the specific state of the first client screen transition sequence acquired in the process of Step 2401. Obtained as a client screen information transition sequence (2501).
- the trigger extraction unit 44 identifies the URL arrangement registered in the screen URL 703 of the screen script table 520 from among the screen scripts 500 constituting the first client screen transition sequence acquired in the process of Step 2401. The same record group as the URL arrangement of the screen script 500 other than the screen script 500 corresponding to the state is acquired. Then, the trigger extraction unit 44 acquires a transition of client screen information displayed on the client PC 10 by the screen script 500 specified by the acquired record group as a third client screen transition sequence.
- the trigger extraction unit 44 determines, as a trigger operation, an operation in which the number of operations counted in the processing of Step 2403 is equal to or less than a threshold (2502), and ends the processing.
- the trigger extraction unit 44 is limited to only client screen information in which the operating environment of the client PC 10 and the user ID of the user of the client PC 10 are the same, and the first client screen transition sequence, the second client screen transition sequence, and the third client screen A transition sequence may be acquired.
- the operating environment of the client PC 10 include the type of the browser 11, the type of OS operating on the client PC 10, the type of device of the client PC 10, and the like.
- the client PC 10 when transmitting a request to the server 10, transmits its operating environment and user ID to the request to be transmitted.
- the server 10 When the server 10 generates the screen script 500 corresponding to the received request and records the generated screen script 500 in the screen script table 520, the operation of the client PC 10 included in the request corresponding to the generated screen script 500 is performed.
- the environment and user ID are recorded in the screen script table 500 in association with the ID included in the generated screen script 500.
- the trigger extraction unit 44 When the trigger extraction unit 44 detects that at least one of the server 90 and the client PC 10 is in a specific state, the trigger extraction unit 44 refers to the screen script table 520 and the operating environment associated with the ID of the screen script 500 corresponding to the specific state, Obtain a user ID. Then, the trigger extraction unit 44 refers to the screen script table 520, and selects the first client screen transition sequence, the second client screen transition sequence, from the screen script 500 in which at least one of the acquired operating environment and user ID matches. The screen script 500 that displays the client screen information 13 constituting the third client screen transition sequence is acquired.
- Possible causes of the server 90 and the client PC 10 to be in a specific state include the operating environment of the client PC 10 and a user-specific operation method.
- the trigger extraction unit 44 determines the trigger operation by limiting to at least one of the operating environment and the user ID of the client PC 10 to the same client screen information 13, and therefore determines the operation that is likely to reach a specific state as the trigger operation. can do.
- the trigger extraction unit 44 determines the trigger operation in units of user operations using the trigger extraction method a and the trigger extraction method b. However, the trigger extraction unit 44 may determine the trigger operations in units of operation sequences including a plurality of user operations. .
- the execution timing of a trigger extraction process is the timing of the server 90 and client PC10.
- the timing is not limited to a case where at least one of the trigger extraction policies is in a specific state, and may be a timing at which a new trigger extraction policy is registered in the trigger extraction policy table 48 via the trigger extraction policy setting screen 2100, for example.
- the server 90 can display the trigger operation registered in the trigger operation specifying information table 5160 as a trigger operation display screen 2600 (see FIG. 26) in response to an administrator request.
- the trigger operation display screen 2600 will be described with reference to FIG.
- FIG. 26 is an explanatory diagram of the trigger operation display screen 2600 according to the embodiment of this invention.
- the trigger operation display screen 2600 includes a screen URL 2601, an operation event 2602, accompanying information 2603, and a close button 2604.
- the URL registered in the screen URL 1001 of the trigger operation specifying information table 5160 is displayed.
- the operation event 2602 an operation event registered in the operation event 1002 of the trigger operation specifying information table 5160 is displayed.
- the accompanying information 2603 information registered in the accompanying information 2603 of the trigger operation specifying information table 5160 is displayed.
- the administrator can confirm the trigger operation set in the server 90.
- the server 90 can display the client screen information 13 acquired from the client PC 10 and recorded in the client screen information table 130 as a client screen information display screen 2700 (FIG. 27) in response to an administrator request.
- the client screen information display screen 2700 will be described with reference to FIG.
- FIG. 27 is an explanatory diagram of the client screen information display screen 2700 according to the embodiment of this invention.
- the client screen information display screen 2700 includes an acquisition time 2701, an ID 2702, an acquisition screen 2703, a related information button 2704, and a close button 2705.
- the acquisition time 2701 displays the time when the client screen information 13 is acquired.
- the ID 2702 the ID of the screen script 500 that displays the acquired client screen information 13 is displayed.
- the acquired client screen information 13 is displayed on the acquisition screen 2703.
- the server 90 displays related information (for example, the operation history 14 and the log 24) of the client screen information corresponding to the pressed related information button 2704.
- the close button 2705 is pressed, the server 90 closes the window of the client screen information display screen 2700.
- the server 90 displays an enlarged display screen 2710 in which the pressed client screen information 13 is enlarged.
- the enlarged display screen 2710 includes a close button 2711. When the close button is pressed, the window of the enlarged display screen 2710 is closed.
- the administrator can confirm the client screen information 13 acquired by the server 90.
- this invention is not limited to the above-mentioned Example, Various modifications are included.
- the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
- a part of the configuration of a certain embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of a certain embodiment.
- each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
- Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.
- Information such as programs, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Computational Linguistics (AREA)
- Debugging And Monitoring (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Description
Claims (19)
- 表示したクライアント画面におけるユーザの操作を受け付けるクライアント計算機から、前記クライアント画面の情報であるクライアント画面情報を収集する画面情報収集計算機において、
前記クライアント計算機から前記クライアント画面情報を収集するクライアント画面情報収集部と、
前記クライアント画面におけるユーザの操作を特定可能な情報を示す操作情報を収集する操作情報収集部と、
前記クライアント画面におけるユーザの操作のうち、前記クライアント画面情報収集部が前記クライアント画面情報を収集するタイミングとなるトリガ操作を決定するトリガ操作決定部と、を有し、
前記トリガ操作決定部は、前記クライアント計算機に表示されるクライアント画面情報及び前記操作情報に基づいて、前記トリガ操作を決定することを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記クライアント画面情報収集部は、
前記トリガ操作決定部によって決定されたトリガ操作を特定可能なトリガ操作特定情報を前記クライアント計算機に送信し、
前記クライアント計算機が前記トリガ操作情報によって特定されるトリガ操作を受け付けた場合に送信する前記クライアント画面情報を受信することによって、前記クライアント画面情報を収集することを特徴とする画面情報収集計算機。 - 請求項2に記載の画面情報収集計算機であって、
前記クライアント画面情報収集部は、前記クライアント計算機が実行することによって前記クライアント画面を生成する画面スクリプトに前記トリガ操作特定情報を埋め込んで前記クライアント計算機に送信することを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記クライアント計算機が前記クライアント画面におけるリクエスト操作を受け付けた場合に前記クライアント計算機が送信するリクエストに対応する処理を実行し、自身の動作を示すログを出力するリクエスト処理部と、
前記リクエスト処理部による処理結果に基づいて、前記クライアント計算機が実行することによって前記クライアント画面を生成する画面スクリプトを生成する画面スクリプト生成部と、
前記画面スクリプト生成部によって生成された前記画面スクリプトの識別情報を生成し、前記生成した識別情報を前記画面スクリプトに付与する識別情報生成部と、を備え、
前記クライアント画面情報収集部は、前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記クライアント画面情報を収集し、
前記操作情報収集部は、前記操作情報によって特定される操作がなされた前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記操作情報を収集し、
前記リクエスト処理部は、前記リクエスト操作がなされた前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記ログを出力し、
前記クライアント画面情報、前記操作情報及び前記ログは、前記画面スクリプトに付与された識別情報によって関連付けられることを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記トリガ操作決定部は、前記クライアント計算機の動作環境及び前記クライアント計算機のユーザ識別情報の少なくとも一方が同じ前記クライアント画面情報及び前記操作情報に基づいて、前記トリガ操作を決定することを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記トリガ操作決定部は、前記クライアント計算機及び前記画面情報収集計算機の少なくとも一方が特定状態となったことを検出した場合、前記トリガ操作を決定することを特徴とする画面情報収集計算機。 - 請求項6に記載の画面情報収集計算機であって、
前記トリガ操作決定部は、
前記クライアント計算機及び前記画面情報収集計算機の少なくとも一方が前記特定状態となったことを検出した場合、前記特定状態に対応するクライアント画面情報までの所定数のクライアント画面情報を第1クライアント画面遷移列として取得し、
前記取得したクライアント画面遷移列に基づいて、第1方式及び第2方式の少なくとも一方を用いて前記トリガ操作を決定し、
前記第1方式では、
前記クライアント計算機に表示されるクライアント画面情報から、前記取得した第1クライアント画面遷移列と同じ遷移のクライアント画面情報を第2クライアント画面遷移列として取得し、
前記第1クライアント画面遷移列及び前記第2クライアント画面遷移列の同じクライアント画面情報における操作情報から同じ操作の操作回数を集計し、
前記集計した操作回数が第1所定値以上である操作を前記トリガ操作に決定し、
前記第2方式では、
前記クライアント計算機に表示されるクライアント画面情報から、前記取得した第1クライアント画面遷移列の前記特定状態に対応するクライアント画面情報以外のクライアント画面情報が同じクライアント画面情報を第3クライアント画面遷移列として取得し、
前記第1クライアント画面遷移列及び前記第3クライアント画面遷移列の同じクライアント画面情報における操作情報から同じ操作の操作回数を集計し、
前記集計した操作回数が第2所定値以下である操作を前記トリガ操作に決定することを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記トリガ操作決定部によって決定されたトリガ操作を表示するトリガ操作表示部及び、前記クライアント画面情報収集部によって収集されたクライアント画面情報を表示するクライアント画面情報表示部の少なくとも一方を備えることを特徴とする画面情報収集計算機。 - 請求項1に記載の画面情報収集計算機であって、
前記トリガ操作は、前記クライアント画面におけるユーザの複数の操作を含むことを特徴とする画面情報収集計算機。 - 表示したクライアント画面におけるユーザの操作を受け付けるクライアント計算機と、
前記クライアント画面の情報であるクライアント画面情報を前記クライアント計算機から収集する画面情報収集計算機と、を備えるシステムにおける画面情報収集方法であって、
前記方法は、
前記画面情報収集計算機が、前記クライアント計算機から前記クライアント画面情報を収集する第1ステップと、
画面情報収集計算機が、前記クライアント画面におけるユーザの操作を特定可能な情報を示す操作情報を収集する第2ステップと、
前記画面情報収集計算機が、前記クライアント画面におけるユーザの操作のうち、前記第1ステップで前記クライアント画面情報を収集するタイミングとなるトリガ操作を決定する第3ステップと、を含み、
前記第3ステップでは、前記クライアント計算機に表示されるクライアント画面情報及び前記操作情報に基づいて、前記トリガ操作を決定することを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記第1ステップでは、
前記画面情報計算機が。前記第3ステップで決定されたトリガ操作を特定可能なトリガ操作特定情報を前記クライアント計算機に送信し、
前記クライアント計算機が、前記トリガ操作情報によって特定されるトリガ操作を受け付けた場合に前記クライアント画面情報を前記画面情報計算機に送信し、
前記画面情報計算機が前記クライアント画面情報を受信することによって、前記クライアント画面情報を収集することを特徴とする画面情報収集方法。 - 請求項11に記載の画面情報収集方法であって、
前記第1ステップでは、前記画面情報計算機が、前記クライアント計算機が実行することによって前記クライアント画面を生成する画面スクリプトに前記トリガ操作特定情報を埋め込んで前記クライアント計算機に送信することを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記クライアントが、前記クライアント画面におけるリクエスト操作を受け付けた場合にリクエストを送信する第4ステップと、
前記画面情報収集計算機が、前記リクエストを受信した場合、前記リクエストに対応する処理を実行し、自身の動作を示すログを出力する第5ステップと、
前記画面情報収集計算機が、前記第5ステップにおける処理結果に基づいて、前記クライアント計算機が実行することによって前記クライアント画面を生成する画面スクリプトを生成する第6ステップと、
前記画面情報収集計算機が、前記第6ステップで生成された前記画面スクリプトの識別情報を生成し、前記生成した識別情報を前記画面スクリプトに付与する第7ステップと、を含み、
前記第1ステップでは、前記画面情報収集計算機が、前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記クライアント画面情報を収集し、
前記第2ステップでは、前記画面情報収集計算機が、前記操作情報によって特定される操作がなされた前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記操作情報を収集し、
前記第5ステップでは、前記画面情報収集計算機が、前記リクエスト操作がなされた前記クライアント画面を表示する前記画面スクリプトに付与された識別情報を含む前記ログを出力し、
前記クライアント画面情報、前記操作情報及び前記ログは、前記画面スクリプトに付与された識別情報によって関連付けられることを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記第3ステップでは、前記画面情報収集計算機が、前記クライアント計算機の動作環境及び前記クライアント計算機のユーザ識別情報の少なくとも一方が同じ前記クライアント画面情報及び前記操作情報に基づいて、前記トリガ操作を決定することを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記第3ステップでは、前記クライアント計算機及び前記画面情報収集計算機の少なくとも一方が特定状態となったことを検出した場合、前記トリガ操作を決定することを特徴とする画面情報収集方法。 - 請求項15に記載の画面情報収集方法であって、
前記第3ステップは、
前記画面情報収集計算機が、前記クライアント計算機及び前記画面情報収集計算機の少なくとも一方が前記特定状態となったことを検出した場合、前記特定状態に対応するクライアント画面情報までの所定数のクライアント画面情報を第1クライアント画面遷移列として取得するステップと、
前記画面情報収集計算機が、前記取得したクライアント画面遷移列に基づいて、第1方式及び第2方式の少なくとも一方を用いて前記トリガ操作を決定するステップと、を含み、
前記第1方式では、
前記画面情報収集計算機が、前記クライアント計算機に表示されるクライアント画面情報から、前記取得した第1クライアント画面遷移列と同じ遷移のクライアント画面情報を第2クライアント画面遷移列として取得し、
前記画面情報収集計算機が、前記第1クライアント画面遷移列及び前記第2クライアント画面遷移列の同じクライアント画面情報における操作情報から同じ操作の操作回数を集計し、
前記画面情報収集計算機が、前記集計した操作回数が第1所定値以上である操作を前記トリガ操作に決定し、
前記第2方式では、
前記画面情報収集計算機が、前記クライアント計算機に表示されるクライアント画面情報から、前記取得した第1クライアント画面遷移列の前記特定状態に対応するクライアント画面情報以外のクライアント画面情報が同じクライアント画面情報を第3クライアント画面遷移列として取得し、
前記画面情報収集計算機が、前記第1クライアント画面遷移列及び前記第3クライアント画面遷移列の同じクライアント画面情報における操作情報から同じ操作の操作回数を集計し、
前記画面情報収集計算機が、前記集計した操作回数が第2所定値以下である操作を前記トリガ操作に決定することを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記画面情報収集計算機が、前記第3ステップで決定されたトリガ操作を表示する第8ステップ及び前記画面情報収集計算機が、前記第1ステップで収集されたクライアント画面情報を表示する第9ステップの少なくとも一方を含むことを特徴とする画面情報収集方法。 - 請求項10に記載の画面情報収集方法であって、
前記トリガ操作は、前記クライアント画面におけるユーザの複数の操作を含むことを特徴とする画面情報収集方法。 - 表示したクライアント画面におけるユーザの操作を受け付けるクライアント計算機から、前記クライアント画面の情報であるクライアント画面情報を収集し、プロセッサ及び記憶領域を有する画面情報収集計算機で実行され、前記クライアント画面情報の収集処理を前記プロセッサに実行させるプログラムを記憶する計算機読み取り可能な記憶媒体であって、
前記処理は、
前記クライアント計算機から前記クライアント画面情報を収集する処理と、
前記クライアント画面におけるユーザの操作を特定可能な情報を示す操作情報を収集する処理と、
前記クライアント画面におけるユーザの操作のうち、前記クライアント画面情報を収集するタイミングとなるトリガ操作を決定する処理と、を含み、
前記トリガ操作の決定処理は、前記クライアント計算機に表示されるクライアント画面情報及び前記操作情報に基づいて、前記トリガ操作を決定することを特徴とする計算機読み取り可能な記憶媒体。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014521099A JP5758544B2 (ja) | 2012-06-18 | 2012-06-18 | 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 |
US14/396,288 US20150326677A1 (en) | 2012-06-18 | 2012-06-18 | Screen information collecting computer, screen information collecting method, and computer-readable storage medium |
PCT/JP2012/065465 WO2013190607A1 (ja) | 2012-06-18 | 2012-06-18 | 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2012/065465 WO2013190607A1 (ja) | 2012-06-18 | 2012-06-18 | 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013190607A1 true WO2013190607A1 (ja) | 2013-12-27 |
Family
ID=49768239
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/065465 WO2013190607A1 (ja) | 2012-06-18 | 2012-06-18 | 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20150326677A1 (ja) |
JP (1) | JP5758544B2 (ja) |
WO (1) | WO2013190607A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016152017A (ja) * | 2015-02-19 | 2016-08-22 | 富士通株式会社 | ログ情報収集プログラム、ログ情報収集装置、及びログ情報収集方法 |
WO2022180863A1 (ja) * | 2021-02-26 | 2022-09-01 | 日本電信電話株式会社 | ユーザ操作記録装置およびユーザ操作記録方法 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11172027B2 (en) * | 2019-02-27 | 2021-11-09 | Rohde & Schwarz Gmbh & Co. Kg | System and method for monitoring remote usage of test and measuring instruments |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003044320A (ja) * | 2001-07-31 | 2003-02-14 | Pfu Ltd | 教育システム |
JP2007323143A (ja) * | 2006-05-30 | 2007-12-13 | Hitachi Ltd | 業務管理システム、情報システム及び業務管理方法 |
JP2008041041A (ja) * | 2006-08-10 | 2008-02-21 | Hitachi Information Systems Ltd | ログ通知条件定義支援装置とログ監視システムおよびプログラムとログ通知条件定義支援方法 |
JP2010044457A (ja) * | 2008-08-08 | 2010-02-25 | Sky Co Ltd | 操作監視システム |
WO2011081126A1 (ja) * | 2009-12-28 | 2011-07-07 | 株式会社エスディー | システムイベントログシステム |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8782541B2 (en) * | 2001-03-12 | 2014-07-15 | Nice-Systems Ltd. | System and method for capturing analyzing and recording screen events |
-
2012
- 2012-06-18 US US14/396,288 patent/US20150326677A1/en not_active Abandoned
- 2012-06-18 JP JP2014521099A patent/JP5758544B2/ja not_active Expired - Fee Related
- 2012-06-18 WO PCT/JP2012/065465 patent/WO2013190607A1/ja active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003044320A (ja) * | 2001-07-31 | 2003-02-14 | Pfu Ltd | 教育システム |
JP2007323143A (ja) * | 2006-05-30 | 2007-12-13 | Hitachi Ltd | 業務管理システム、情報システム及び業務管理方法 |
JP2008041041A (ja) * | 2006-08-10 | 2008-02-21 | Hitachi Information Systems Ltd | ログ通知条件定義支援装置とログ監視システムおよびプログラムとログ通知条件定義支援方法 |
JP2010044457A (ja) * | 2008-08-08 | 2010-02-25 | Sky Co Ltd | 操作監視システム |
WO2011081126A1 (ja) * | 2009-12-28 | 2011-07-07 | 株式会社エスディー | システムイベントログシステム |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016152017A (ja) * | 2015-02-19 | 2016-08-22 | 富士通株式会社 | ログ情報収集プログラム、ログ情報収集装置、及びログ情報収集方法 |
WO2022180863A1 (ja) * | 2021-02-26 | 2022-09-01 | 日本電信電話株式会社 | ユーザ操作記録装置およびユーザ操作記録方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2013190607A1 (ja) | 2016-02-08 |
US20150326677A1 (en) | 2015-11-12 |
JP5758544B2 (ja) | 2015-08-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10613916B2 (en) | Enabling a web application to call at least one native function of a mobile device | |
US8566648B2 (en) | Automated testing on devices | |
JP5325177B2 (ja) | ウェブアプリケーションの操作記録方法およびシステム | |
US7464004B2 (en) | Troubleshooting to diagnose computer problems | |
US20100229112A1 (en) | Problem reporting system based on user interface interactions | |
US20140317489A1 (en) | Device-independent validation of website elements | |
US20130198333A1 (en) | Method and device for recording and reproducing web operation | |
KR102257500B1 (ko) | 프로그램, 시스템, 및 정보 처리 방법 | |
CN111198797B (zh) | 操作监控方法及装置、操作分析方法及装置 | |
JP5758544B2 (ja) | 画面情報収集計算機、画面情報収集方法及び計算機読み取り可能な記憶媒体 | |
US9727281B2 (en) | Image processing apparatus, computer readable medium, and image processing method | |
CN110209557B (zh) | 用户操作录制还原方法、装置、设备及可读存储介质 | |
US9769246B2 (en) | Information processing terminal and control method | |
US20220164703A1 (en) | Model acceptance determination support system and model acceptance determination support method | |
JP5747751B2 (ja) | リグレッションテスト支援プログラム及びリグレッションテスト支援装置 | |
JP2012208919A (ja) | 電子機器、情報処理システム、及びプログラム | |
US20140344756A1 (en) | Information processing apparatus, and control method therefor | |
US11747966B2 (en) | Detecting paste and other types of user activities in computer environment | |
US9858549B2 (en) | Business transaction resource usage tracking | |
CN111367703A (zh) | 故障排查方法及装置 | |
CN114465738A (zh) | 应用程序的取证方法、系统、设备及存储介质 | |
JP6261244B2 (ja) | Webアプリケーションテスト装置およびそのプログラム | |
JP2014123298A (ja) | 情報管理プログラム及び情報管理方法 | |
KR102278878B1 (ko) | 통합 사용 로그 데이터를 생성하는 서버 및 그 동작 방법 | |
JP6353759B2 (ja) | テスト実行装置、テスト実行方法およびコンピュータプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12879222 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2014521099 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14396288 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12879222 Country of ref document: EP Kind code of ref document: A1 |