JP2012027627A - Maintenance and improvement work supporting system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce time required for understanding an information system.SOLUTION: A system has a client unit for issuing an executing request for processing and a server unit. The server unit has an application execution unit for executing processing in response to the request from the client, and an execution information acquiring control unit for controlling acquisition of execution information. The client unit stores an acquisition start request for the execution information when receiving it. Then, when the client unit receives an execution request to the application execution unit after receiving the acquisition start request for the execution information, the client unit transmits the stored execution request and also the acquisition request for the execution information to the server unit. The application execution unit executes processing based on the execution request, and the execution information acquiring control unit stores the execution information of the processing executed by the application execution unit in a storage device.

Description

  The present invention relates to a technique for supporting a maintenance / improvement worker in maintenance / improvement work of an information system.

  Persons in charge of maintenance improvement of information systems are required to improve the efficiency of maintenance and improvement of information systems (such as an increase in turnover rate and cost reduction) in accordance with changes in the business environment. However, because of the discrepancy between the information system source code and documents (design documents, specifications, etc.), the complexity of the source code due to repeated maintenance and improvement of the information system, to investigate the cause of failure and add functions The number of man-hours required to grasp the current information system tends to increase, making it difficult to achieve efficient maintenance and improvement.

  A technique for analyzing the logic of a program and analyzing a database access based on information at the time of execution of the program has been considered, and supports the work of maintenance and improvement workers (hereinafter, the database is abbreviated as DB). For example, (1) screen operation information of a Web application, (2) execution history information of a program execution environment, and (3) DB access information are linked in units of requests, and the history information of (1) to (3) is collected. It realizes a mechanism to display as the basis of unity, and supports the understanding promotion of the person in charge who maintains and improves the information system. Here, the request is one access indicating a job request from the client PC to the server. Further, Patent Document 1 reads information previously described in a source code (for example, as a comment) on the server side in order to reduce a recording amount of a screen input operation history of a Web application, and performs an input operation of an acquisition target candidate. A function that can customize the acquisition status is realized.

JP 2009-25597 A

  A method of acquiring information at the time of execution in a server in units of users or in units of requests in a Web application system having a feature such that a plurality of users simultaneously access a server using a client PC and use the same program There is no. In Patent Document 1, there is a need for the above method because the performance degradation of the Web application and the compression of the storage capacity due to the constant acquisition of information at the time of execution in the server can be considered.

  In addition, there is no method for selectively acquiring runtime information without modifying the source code. As disclosed in Patent Document 2, means for selecting information to be acquired at the time of execution on the server side based on the information added to the source code is considered. However, a candidate for an input operation target to be acquired at the time of execution is added. When the information added to the source code is corrected, it is necessary to compile the source code and rearrange the Web application each time.

The system includes a client unit that issues a process execution request and a server unit. The server unit includes an application execution unit that executes processing in response to a request from a client, and a runtime information acquisition control unit that controls acquisition of execution information. Upon receiving the execution information acquisition start request, the client unit stores this. When the client unit receives an execution request for the application execution unit after receiving the execution information acquisition start request, the client unit transmits the execution information acquisition request together with the stored execution request to the server unit. The application execution unit executes processing based on the execution request, and the execution information acquisition control unit stores execution information of the processing executed by the application execution unit in the storage device.

  In the maintenance / improvement work of the information system, it is possible to acquire the runtime information of the Web application for each user, or to determine the start and end of acquisition of the runtime information by the user himself. For this reason, it is possible to reduce the work of dividing the acquired execution time information into related information and non-interesting information (for example, uninteresting execution time information or execution time information by other users). Lead time for understanding current information systems can be shortened. Further, it is possible to reduce the performance degradation of the Web application and the compression of the storage capacity due to the acquisition of runtime information. Also, there is no need to put information for selectively acquiring runtime information in the source code in advance.

It is an example of the system configuration of a maintenance improvement business support environment. It is an example of the hardware constitutions of a server. It is a sequence diagram which shows an example of the processing flow which acquires runtime information. It is a figure which shows the example of a run time information acquisition presence / absence information setting page (P001) and a work page (P002). It is a figure which shows the example of runtime information acquisition presence information (C001). It is a figure which shows the example of a runtime information acquisition object list | wrist (171). It is a figure which shows an example of the memory structure of a server for acquisition of runtime information. It is a figure which shows an example of the runtime information acquisition process flow in a server. It is a figure which shows the example of runtime information stored in runtime information DB (161). It is a figure which shows the other example of runtime information stored in runtime information DB (161). It is a figure which shows the other example of runtime information stored in runtime information DB (161).

Hereinafter, an example of an embodiment will be described in detail with reference to the drawings.

  FIG. 1 is an example of a system configuration.

  The system adopts a client / server configuration in which a plurality of client PCs (101, 102) and a server (120) cooperate via a network (111). Note that functions corresponding to a plurality of clients and servers may be arranged by software on the same computer.

  In the system, regarding the acquisition of information at the time of execution of the Web application, the acquisition of execution time information is controlled for each user of the Web application or for each request.

  The server (120) has a Web application (130), middleware (140), and a program execution platform (150). The entities of the Web application (130), middleware (140), and program execution platform (150) are software included in the server (120) described later, and the CPU (201) of the server (120) is external storage device (204). This is realized by reading the software stored in the main memory (202) and executing it.

  The web application (130) refers to an application group arranged on the server (120). It is assumed that at least one application is arranged in the Web application (130). In this embodiment, a runtime information acquisition presence / absence information setting application (131) and a plurality of business applications (132, 133) are arranged.

  The execution time information acquisition presence / absence information setting application (131) has a function of reading / writing execution time information acquisition presence / absence information attached to a request transmitted from the client PC to the server.

  The middleware (140) has a runtime information acquisition control device (141) and a runtime information acquisition device (142). The entities of the runtime information acquisition control device (141) and the runtime information acquisition device (142) are also software arranged on the middleware (140).

  The runtime information acquisition control device (141) refers to the runtime information acquisition presence / absence information attached to the request transmitted from the client PC via the network, checks the contents, and executes the runtime information acquisition device (142). ) To start / end the acquisition of runtime information.

  The runtime information acquisition device (142) acquires information (log information) at the time of execution of the Web application (130) arranged in the server (120). In this embodiment, the runtime information acquisition device (142) has a Web container runtime information acquisition device (143), a program runtime information acquisition device (144), and a DB access runtime information acquisition device (145). It is not limited to this.

  The Web container runtime information acquisition device (143) acquires information held by a request transmitted from the client PC (101, 102) to the server (120). For example, the URL of the page (on the client PC) that transmitted the request may be used.

  The program execution time information acquisition device (144) acquires information when the Web application (130) is executed on the program execution platform (150). For example, when the program execution platform (150) is a Java (registered trademark) VM, a call relationship between objects (on a memory) that instantiates a Class file (package name, class name, method name, etc. of the call source object) , And the callee object's package name, class name, method name, etc.) information.

  The DB access execution time information acquisition device (145) acquires information when the Web application (130) refers to / stores data in the business DB (162) using SQL or the like. For example, the SQL statement issued to the business DB (162), the value of data acquired by referring to the table of the business DB (162), and the like can be acquired.

  The program execution platform (150) has a function of inserting a machine language for acquiring runtime information when an object is expanded on a memory in order to execute the Web application (130). For example, when the program execution platform (150) is a Java (registered trademark) VM, a java.lang.instrument package is known, and bytecodes are embedded when an object is placed on a memory by instantiating a Class file. Provides functionality.

  The runtime information DB (161) is a DB that stores the runtime information acquired by the runtime information acquisition device (142). The runtime information DB (161) may be mounted on an external storage device (240) of the server (120) described later, or may be mounted on another storage device connected to the server (120). The storage location of the runtime information may be a file in addition to the DB.

  The business DB (162) is a DB that stores and manages business data referred to by the business applications (132, 133). The business DB 162 may be mounted on an external storage device (240) of the server (120) described later, or may be mounted on another storage device connected to the server (120).

  The runtime information acquisition target list (171) is a list in which a list of program names from which runtime information is acquired is recorded. In the present embodiment, it is assumed that the runtime information acquisition target list (171) is stored in a file, but there is a method of storing it in a DB or the like. The runtime information acquisition target list (171) may also be mounted on the external storage device (240) of the server (120) described later, or may be mounted on another storage device connected to the server (120). Good.

  Details of each component will be described below.

  FIG. 2 is an example of a hardware configuration of the server (120).

  The server includes a CPU (201), a main storage device (202), a network connection device (203), an external storage device (204), a display (205), a data input device (206), a network (207), and the like. Note that the client PCs (101, 102) have the same hardware configuration as the server (120).

  FIG. 3 is a sequence diagram illustrating an example of a flow for acquiring runtime information.

  FIG. 4 is a screen example (400) of the client PC (101) displaying the runtime information acquisition presence / absence information setting page (P001) and the business page (P002).

  In the flow shown in FIG. 3, only the case where the “user” communicates with the server (120) using the client PC (101) is taken up, but other “users” are other than the client PC (101) at the same time. The same flow is also followed when communicating with the server (120) using the client PC.

  In accordance with the input from the “user” (input of URL or the like), the client PC displays the runtime information acquisition presence / absence information setting application (P001) provided to the client PC by the runtime information acquisition presence / absence information setting application (131). 101) The server is instructed to display on the top (S301).

  In response to the request from the client PC (101), the server (120) confirms that it is not necessary to acquire execution information by referring to the execution time information acquisition presence / absence information (C001) included in the request, and the response Information for displaying the runtime information acquisition presence / absence information setting page (P001) is returned to the client PC (101) (S302).

  The execution time information acquisition presence / absence information (C001) will be described later, but in S302, S304, and S307, since acquisition of execution time information is not instructed by the user, information included in the execution time information acquisition presence / absence information (C001) is acquired. The value of the key “isOnRecordingOperation” indicating whether it is necessary is “false”. Therefore, the server (120) does not perform execution time information acquisition processing. Next, in accordance with the input from the “user”, the client PC (101) instructs the server to display on the client PC (101) the business page (P002) of the business application for which runtime information is to be acquired (S303).

  In response to the request from the client PC (101), the server (120) confirms that it is not necessary to acquire execution information by referring to the execution time information acquisition presence / absence information (C001) included in the request, and the response Information for displaying the business page (P002) is returned to the client PC (101) (S304).

  Next, the “user” advances the business using the business page (P002) displayed on the client PC (101) (S305). For example, using the example of the business page (P002) of FIG. 4, the value of “product ID” is input to the input form (411), and the “Search” button (412) is pressed.

  The client PC (101) transmits the form data input by the “user” on the business page (P002) to the server (120) (S306).

  The server (120) confirms that it is not necessary to acquire execution information by referring to the execution time information acquisition presence / absence information (C001) included in the request for the received request, and performs business processing according to the request. The information displayed on the business page (P002) is returned as a response (S307).

  As described above, the business process is executed by repeating the processes of (S305), (S306), and (S307).

  If the “user” wants to acquire runtime information, the user can instruct the start of acquisition of runtime information using the runtime information acquisition presence / absence information setting page (P001) (S308). Here, using the example of the runtime information acquisition presence / absence information setting page (P001) in FIG. 4, the user selects the type of runtime information to be acquired through an operation interface (401, 402, 403) such as a check box, Then, an operation interface (404) such as a “Start” button can be pressed to instruct start of acquisition of runtime information.

  In response to an instruction from the user, the client PC (101) sets execution time information acquisition presence / absence information (C001) (S309). FIG. 5 is an example of execution time information acquisition presence / absence information (C001). For example, when the user gives an instruction using the runtime information acquisition presence / absence information setting page (P001) in FIG. 4, the user presses the “Start” button (404), or the client PC receives the instruction from the user. (101) can set the value of the key “isOnRecordingOperation” of the runtime information acquisition availability information (501) to “true” to instruct the server to start acquiring information at the time of execution. Also, the client PC (101) acquires the time when the user presses the “Start” button (404), and sets it to the value of the key “RecordingID” of the runtime information ID (505). When the user checks the check boxes (401, 402, 403), the client PC (101) acquires the value of the key “isRecordedWebContainerOperation” of the Web container runtime information acquisition availability information (502) and the program runtime information. The value of the key “isRecordedProgramOperation” in the permission information (503) and the value of the key “isRecordedDBAccessInfo” in the DB access execution time information acquisition permission information (504) can be set to “true”, respectively. You can specify the type of time information. Further, when the user unchecks the check box, the client PC (101) can set the key value to “false”, and the runtime information set to “false” for the server is acquired from the acquisition target. Can be specified to be removed.

  Next, the “user” advances the business by pressing an operation interface such as a button on the business page (P002) displayed on the client PC (101) (S310).

  The data input by the user to the form on the business page (P002) is transmitted from the client PC (101) to the server (120) as request information (S311). At this time, the runtime information acquisition presence / absence information (C001) previously set in (S309) is also given to the request.

  The server (120) confirms the runtime information acquisition presence / absence information (C001) included in the received request, and returns information displayed on the business page (P002) as a response (S312). Here, since the request execution time information acquisition presence / absence information (C001) includes information for starting the acquisition of the execution time information, the server (120) acquires the execution time information and executes the execution time information DB ( 161).

  Here, the business process is executed by repeating the processes of (S310), (S311), and (S312).

Next, the “user” uses the execution time information acquisition presence / absence information setting page (P001) to instruct the end of execution time information acquisition (S313). For example, the “user” presses the “Finish” button (405) on the runtime information acquisition presence / absence information setting page (P001) of FIG. In response to this, the client PC (101) sets the value of the key “isOnRecordingOperation” of the runtime information acquisition availability information (501) to “false” (S314). The request issued from the client PC (101) to the server from the next time is attached with runtime information acquisition presence / absence information (C001) in which the value of the key “isOnRecordingOperation” is set to “false”. As in the case of S304 and S307, the execution time information is not acquired. In this way, the “user” performs the operation from the start of acquisition of execution time information (S308) to the operation of end of acquisition of execution time information (S313). By repeating a series of operations, it is possible to perform business processing while acquiring runtime information for only predetermined processing.

  Next, the “user” closes the business page (P002) (S315). For example, using the example of the business page (P002) in FIG. 4, when the operation interface (413) such as a button is pressed, the client PC (101) closes the business page (P002).

  Next, the “user” closes the runtime information acquisition presence / absence information setting page (P001) (S316). For example, using the example of the business page (P002) in FIG. 4, when the user presses the operation interface (406) such as a button, the client PC (101) closes the runtime information acquisition presence / absence information setting page (P001).

  FIG. 5 shows the execution time information acquisition presence / absence information set by the client PC (101) based on the instruction from the user input in the execution time information acquisition presence / absence information setting page (P001) in the processing (S309, S314). In this embodiment, the execution time information acquisition availability information (501), the Web container execution time information acquisition availability information (502), the program execution time information acquisition availability information (503), and the DB access execution time information. It is assumed to be composed of items of acquisition availability information (504) and runtime information ID (505).

  The runtime information acquisition availability information (501) is expressed in the key-value format, and when the value for the key “isOnRecordingOperation” is “true”, it indicates the start of acquisition of runtime information. On the other hand, when the value is “false”, it indicates the end of acquisition of runtime information.

  The Web container runtime information acquisition availability information (502) is expressed in the key-value format. When the value for the key “isRecordedWebContainerOperation” is “true”, the Web container runtime information acquisition device (143) is in the Web container. Get runtime information. On the other hand, when the value is “false”, it indicates the end of acquisition of runtime information.

  The program execution time information acquisition availability information (503) is expressed in the key-value format. When the value for the key “isRecordedProgramOperation” is “true”, the program execution time information acquisition device (144) displays the program execution time information. Get information. On the other hand, when the value is “false”, it indicates the end of the acquisition of the program runtime information.

  The DB access execution time information acquisition availability information (504) is expressed in the key-value format. When the value for the key “isRecordedDBAccessInfo” is “true”, the DB access execution time information acquisition apparatus (145) Get runtime information for. On the other hand, when the value is “false”, it indicates the end of acquisition of DB access execution time information.

  The runtime information ID (505) is an item that identifies runtime information acquired in units of “users” and is expressed in a key-value format. In this embodiment, the time at which execution start of acquisition of runtime information is instructed by the runtime information acquisition presence / absence information setting page (P001) is set as a value for the key “RecordingID”.

  As a specific means for adding some information to the request from the page displayed on the browser such as the runtime information acquisition presence / absence information setting page (P001), writing to Cookie can be cited. That is, when the user instructs execution start / end of the execution time information using the execution time information acquisition presence / absence information setting page (P001), the client PC obtains the execution time information acquisition existence information created based on the instruction. (C001) is held in the memory. At this time, whenever the user issues a request using the business page (P002), the client PC that has received the request assigns the runtime information acquisition presence / absence information (C001) stored in the memory to the server. 120.

  FIG. 6 is an example of a runtime acquisition target list (171) that is referred to when the program execution platform (150) inserts a machine language for acquiring runtime information.

  The execution time acquisition target list (171) is a file storing file names of programs for acquiring execution time information. In this embodiment, the program is specified by the class name (601) of the program described in Java (registered trademark) language. Also, by using a symbol such as an asterisk “*”, it is possible to specify all of the classes below the package.

  Hereinafter, the operation on the server side of the sequence diagram (FIG. 3) showing the flow of obtaining the runtime information will be described.

  FIG. 7 shows the memory (main storage device) in the server (120) of the thread associated with one request transmitted from the client PC in the processing (302, 304, 307, 312) requested by the client PC. 202). In this embodiment, the memory (202) includes a Web application memory area (710), a runtime information acquisition control apparatus memory area (720), a Web container runtime information acquisition apparatus memory area (730), and a program execution time. The information acquisition device memory area (740), the DB access execution time information acquisition device memory area (750), and the in-thread variable area memory area (760) are configured.

  The web application memory area (710) is a memory area used by the web application (130). In the present embodiment, it is assumed that a Web application described in Java (registered trademark) language is used, and objects (711, 712, 713) instantiated from a Class file are arranged. In particular, the object (712) is instantiated from a Class file on the runtime information acquisition target list (171), and a machine language for acquiring runtime information is inserted by the program execution platform (150). ing.

  The runtime information acquisition control device memory area (720) is a memory area used by the runtime information acquisition control device (141).

  The web container runtime information acquisition device memory area (730) is a memory area used by the web container runtime information acquisition device (143).

  The program execution time information acquisition device memory area (740) is a memory area used by the program execution time information acquisition device (144).

  The DB access execution time information acquisition device memory area (750) is a memory area used by the DB access execution information acquisition device (145).

  The in-thread variable area memory area (760) is a variable area provided for each thread. For example, in the case of Java (registered trademark) language, it is provided as a thread local variable area. In this embodiment, it is assumed that an object (761) is arranged.

  FIG. 8 is a sequence diagram illustrating a flow of processing executed by the server (120) when the server (120) receives a request to which execution time information acquisition presence / absence information (C001) is added. Through this processing flow, the server (120) acquires the runtime information according to the content of the runtime information acquisition presence / absence information (C001) given to the request and stores it in the runtime information DB (161).

  This flow is started when the server (120) receives a request transmitted from the client PC (101) via the network (111).

  The runtime information acquisition control device (141) acquires the runtime information from the Web container runtime information acquisition device (143) according to the content of the runtime information acquisition presence / absence information (C001) given to the request. The value of the runtime information ID (505) is transmitted together with the start / end instruction message (S701). In this embodiment, when the example of the runtime information acquisition presence / absence information (C001) in FIG. 5 is used, the value for the key “isOnRecordingOperation” of the runtime information acquisition availability information (501) is “true” and the Web container runtime information is acquired. When the value for the key “isRecordedWebContainerOperation” in the availability information (502) is “true”, a message for starting acquisition of runtime information is transmitted. On the other hand, when the value for the key “isOnRecordingOperation” in the runtime information acquisition availability information (501) is “false” or the value for the key “isRecordedWebContainerOperation” in the Web container runtime information acquisition availability information (502) is “false”. , A message indicating completion of acquisition of runtime information is transmitted.

  Next, the Web container runtime information acquisition device (143) acquires runtime information in response to the message received from the runtime information acquisition control device (141), and executes it together with the value of the runtime ID (505). The information is stored in the information DB (161) (S702).

  Next, the execution time information acquisition control device (141), according to the contents of the execution time information acquisition presence / absence information (C001) given to the request, a message for instructing start / end of DB access execution time information and The value of the runtime information ID (505) is transmitted to the object (761) in the in-thread variable area memory area (760) (S703). In this embodiment, when the example of the execution time information acquisition presence / absence information (C001) in FIG. 5 is used, the value for the key “isOnRecordingOperation” of the execution time information acquisition availability information (501) is “true” and the DB access execution time information acquisition is performed. When the value for the key “isRecordedDBAccessInfo” in the permission information (504) is “true”, a message for starting acquisition of DB access execution time information is transmitted. On the other hand, when the value for the key “isOnRecordingOperation” in the runtime information acquisition availability information (501) is “false” or the value for the key “isRecordedDBAccessInfo” in the DB access runtime information acquisition availability information (504) is “false”. Then, a message indicating completion of acquisition of DB access runtime information is transmitted.

  Next, the object (761) in the thread internal variable area (760) stores the value of the runtime information ID (505) and DB access in accordance with the message received from the runtime information acquisition control device (141). The flag for starting / ending the acquisition of execution time information is set (S704).

  Next, the runtime information acquisition control device (141) responds to the program runtime information acquisition device (144) according to the content of the runtime information acquisition presence / absence information (C001) given to the request received from the client PC. Then, the value of the runtime information ID (505) is transmitted together with a message for instructing the start / end of acquisition of runtime information (S705). In the present embodiment, if the example of the execution time information acquisition presence / absence information (C001) in FIG. 5 is used, the value for the key “isOnRecordingOperation” of the execution time information acquisition availability information (501) is “true” and the program execution time information acquisition availability is possible. When the value for the key “isRecordedProgramOperation” of the information (503) is “true”, a message for starting acquisition of program execution time information is transmitted. On the other hand, when the value for the key “isOnRecordingOperation” in the runtime information acquisition availability information (501) is “false” or the value for the key “isRecordedProgramOperation” in the program runtime information acquisition availability information (503) is “false”, A message indicating the end of acquisition of program runtime information is sent.

  Next, the program execution time information acquisition device (144) sets a program execution time information acquisition start / end flag in response to a message from the execution time information acquisition control device (141). The value of the runtime information ID (505) is stored in the area (740) internally (S706).

  Next, the runtime information acquisition control device (141) calls a Web application corresponding to the request received by the server (S707). In the present embodiment, the object (711) in the Web application memory area (710) is called.

  Next, the object (711) in the web application memory area (710) calls the object (712) (S708).

  Next, the object (712) in the web application memory area (710) calls the object (713) (S709).

  Next, the object (712) in the memory area for web application (710) transmits a message for requesting execution time information acquisition to the program execution time information acquisition device (144) in accordance with the embedded machine language. (S710).

  Next, when receiving the execution time information acquisition request message, the program execution time information acquisition apparatus (144) refers to the start / end flag of the execution time information acquisition set internally (S711).

  The program execution time information acquisition device (144) acquires the execution time information in (S709) when the referenced start / end flag of the execution time information indicates the start of execution time information acquisition. And stored in the runtime information DB (161) together with the stored runtime information ID (505) (S712).

Next, the object (713) in the Web application memory area (710) performs operations such as access to the business DB (162) and reference of business data to the DB access execution time information acquisition device (145). A message to be requested is transmitted (S713).
The DB access execution time information acquisition device (145) accesses the business DB (162) and executes operation of business data (S714).

The DB access execution time information acquisition device memory area (145) refers to the object (761) in the in-thread variable area memory area (760), and the DB access execution time information acquisition start / end flag (S715).
The DB access execution time information acquisition device memory area (145) indicates that the DB access execution time information acquisition start / end flag indicates that the DB access execution time information acquisition start is the DB in (S714). The access execution time information is acquired and stored in the execution time information DB (161) together with the stored execution time information ID (505) (S716).

  FIG. 9 shows an example (900) of runtime information acquired in the Web container, which is stored in the runtime information DB (161) through the process (S702) in the Web container runtime information acquisition device (143). In this embodiment, “execution information ID”, “request ID”, “URL”, “request caller URL”, and “QueryString” are listed.

  “Execution time information ID” is an item for specifying execution time information acquired for each user. In this embodiment, the Web container execution time information acquisition device (143) executes from the execution time information acquisition control device (141). The value of “execution time information ID” can be acquired when receiving the time information acquisition start / end message.

  “Request ID” is an item that uniquely identifies a request. It is given mechanically at the timing when the Web container receives the request.

  “URL” is an item for specifying a resource requested by a request. For example, in the case of Java (registered trademark) language, it can be mechanically acquired on the server side from a request object generated when a request is received.

  The “request call source URL” is an item that identifies the resource (displayed on the client PC) that transmitted the request. For example, in the case of Java (registered trademark) language, it can be mechanically acquired on the server side from a request object generated when a request is received.

  “QueryString” is an item indicating user input data added at the time of request transmission. For example, if the page is described in HTML, the value input in the form displayed by the FORM tag is added to the request. Can be sent to the server. In the case of the Java (registered trademark) language, it can be mechanically acquired on the server side from a request object generated when a request is received.

  FIG. 10 is an example (1000) of runtime information acquired by the program runtime information acquisition device (144). In this embodiment, “execution time information ID”, “calling object information”, and “calling object information” are listed.

  The “execution time information ID” is an item for specifying execution time information acquired for each user. In this embodiment, the program execution time information acquisition device (144) is executed from the execution time information acquisition control device (141). When the information acquisition start / end message is received, the value of “execution time information ID” is stored inside the program execution time information acquisition device (144).

  “Calling object information” is an item indicating information held by an object that transmits a message to another object, and can be acquired mechanically when a certain object transmits a message. In this embodiment, in the case of Java (registered trademark) language, the character string “com.hitachi.sdl.appB” corresponding to the package and the character string “SearchItemServlet” corresponding to the class are connected by a symbol such as a period “.”. In addition, the character string “SearchItemServlet” corresponding to the class and the character string “doGet” corresponding to the method are connected by a symbol such as “#”.

  “Called object information” is an item indicating information held by an object that receives a message from another object, and can be acquired mechanically when a certain object receives the message. In this embodiment, in the case of Java (registered trademark) language, a character string “com.hitachi.sdl.appB” corresponding to a package and a character string “ProductBeans” corresponding to a class are connected by a symbol such as a period “.”. Furthermore, the character string “ProductBeans” corresponding to the class and the character string “setProductID” corresponding to the method are connected by a symbol such as a sharp symbol “#”.

  FIG. 11 is an example (1100) of runtime information acquired by the DB access runtime information acquisition device (145). In this embodiment, “execution time information ID” and “SQL information” are listed.

  The “execution time information ID” is an item for specifying execution time information acquired for each user. In this embodiment, the DB access execution time information acquisition device (145) is controlled by the execution time information acquisition control device (141). The value of “run time information ID” stored in the object (761) in the thread internal variable area (760) can be referred to.

  “SQL information” is an item indicating information such as data operations and definitions issued to the business DB 162, and in this embodiment, a character string “SELECT * FROM PRODUCT_TABLE WHERE ITEM = 001” described in the SQL language. ".

101 Client PC
102 Client PC
120 Server 130 Web Application 140 Middleware 150 Program Execution Platform 161 Runtime Information DB
162 Business DB
171 Runtime information acquisition target list

Claims (10)

A system for acquiring execution information of processing executed on a computer,
A client part that issues a process execution request;
An application execution unit that executes processing in response to a request from the client, and a server unit that includes an execution information acquisition control unit that controls acquisition of the execution information;
When receiving the execution information acquisition start request, the client unit stores this,
Each time the client unit receives an execution request for the application execution unit after receiving the execution information acquisition start request, the client unit acquires an execution information acquisition request together with the execution request based on the stored execution information acquisition start request. To the server unit,
The application execution unit executes processing based on the execution request,
The execution information acquisition control unit stores in a storage device execution information of a process executed by the application execution unit based on the execution information acquisition request. The system of claim 1, comprising:
When the client unit receives the execution information acquisition end request, it stores this,
Each time the client unit receives an execution request to the application execution unit after receiving the execution information acquisition end request, the client unit does not need to acquire execution information together with the execution request based on the stored execution information acquisition end request. Information to be sent to the server unit,
The application execution unit executes processing based on the execution request,
The execution information acquisition control unit performs control so that execution information of a process executed by the application execution unit is not stored in a storage device based on information indicating that the execution information acquisition is unnecessary. The system of claim 1, comprising:
When the client unit receives the execution information acquisition start request, the client unit stores an ID for identifying the execution information acquisition start request;
Each time an execution request for the application execution unit is received after receiving the execution information acquisition start request, an execution information acquisition request and an ID for identifying the acquisition start request are transmitted to the server unit together with the execution request. Feature system. The system of claim 1, comprising:
The server unit includes a plurality of application execution units that execute different processes.
The system wherein the client unit displays an interface for designating whether or not to acquire execution information for each of the plurality of application execution units. The system of claim 1, comprising:
The server unit includes a plurality of application execution units that execute different processes.
The execution information acquisition start request received by the client unit includes identification information of the application execution unit,
The execution information acquisition control unit stores the execution information of the application execution unit indicated by the identification information in the storage device based on the identification information of the application execution unit included in the execution information acquisition request received from the client unit. A system characterized by that. A client part which is a program executed in a computer system and issues a process execution request;
An application execution unit that executes processing in response to a request from the client, and a server unit that includes a runtime information acquisition control unit that controls acquisition of the execution information;
The client part
Receiving an execution information acquisition start request;
Storing the received acquisition start request for the execution information;
When an execution request to the application execution unit is received after receiving the execution information acquisition start request, based on the stored execution information acquisition start request, an execution information acquisition request is sent to the server unit along with the execution request. Perform the sending step,
The application execution unit executes processing based on the execution request,
The execution information acquisition control unit executes a step of storing, in a storage device, execution information of a process executed by the application execution unit based on the execution information acquisition request. The program according to claim 6,
The client unit further includes
Receiving an execution information acquisition end request; and
Storing the execution information acquisition end request;
When an execution request for the application execution unit is received after receiving the execution information acquisition end request, information indicating that the execution information acquisition is not required is stored together with the execution request based on the stored execution information acquisition end request. To send to the department,
The application execution unit executes processing based on the execution request,
The execution information acquisition control unit controls the execution information of the process executed by the application system to be executed by the computer system so as not to be stored in the storage device based on the information indicating that the execution information acquisition is unnecessary. program. The program according to claim 6,
The client part
Receiving the execution information acquisition start request, storing an ID for identifying the execution information acquisition start request;
When an execution request for the application execution unit is received after receiving the execution information acquisition start request, an ID for identifying the execution information acquisition request and the execution information acquisition request is transmitted to the server unit together with the execution request. And a step of executing. The program according to claim 6,
The server unit includes a plurality of application execution units that execute different processes.
The client unit causes the computer system to display an interface for designating whether to acquire execution information for each of the plurality of application execution units. The program according to claim 6,
The server unit includes a plurality of application execution units that execute different processes.
The execution information acquisition start request includes identification information of the application execution unit,
The execution information acquisition control unit stores the execution information of the application execution unit indicated by the identification information in the storage device based on the identification information of the application execution unit included in the execution information acquisition request received from the client unit. A program characterized by executing steps.

Images