JP2011192230A - Maintenance operation support system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To shorten the lead time for a cause position when analyzing the cause of a fault of an information system in maintenance operation of the information system. <P>SOLUTION: A history information tracking key is extracted from a history of operations of a client system in a target system to be analyzed, information of a specific operation of the client system is extracted from the history of operations of the client system on the basis of the history information tracking key, information specifying an object being an origin of a call of objects in a program execution environment is extracted from a history of a web container on the basis of the history information tracking key, and information of all of objects related to the call with the specific object as the origin is extracted from a history of the program execution environment on the basis of information extracted from the history of the web container. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a maintenance work support system, and more particularly to a technique for supporting a maintenance worker in an information system maintenance work.

  Persons in charge of information system maintenance work are required to quickly investigate and cope with causes and to have a deep understanding of the current information system in the event of a failure. However, obsolete documents and modifications that ignore the design policy at the time of development help the complexity of decoding the source code, making it difficult for the person in charge to fully understand the system while being on time.

  A technique for generating specification information such as class / method call relations is considered, and supports the work of maintenance personnel. For example, Patent Document 1 discloses a method of hierarchically storing analysis information of source code of software to be analyzed and sequentially storing it in a storage medium such as a database, and in the case where the memory capacity in a computer system for analysis is not sufficient It supports the reduction of complicated work for maintenance personnel accompanying software analysis, such as having to perform analysis again after taking some measures. Patent Document 2 is characterized in that execution order information is acquired by executing software internally, and dynamic design information such as a sequence diagram is generated, so that a maintenance person understands the behavior of the software. Providing information.

Japanese Patent No. 3997495 JP 2008-310679 A

  In a Web application having a feature such that a user interface such as a Web page and internal execution information (call relationship between classes, etc.) are separated, there is a method of visualizing a specific user operation content and its internal execution information by connecting them. Absent. In addition, as a conventional technique, the visualization of the behavior is performed based on the execution information of the software, but in a Web application having a feature such that a plurality of users use the same one program at the same time, the internals of the plurality of users There is no way to separate internal execution information of execution information from internal execution information of each user.

  In order to solve the above problems, the present invention extracts a history information tracking key from the history of operation of the client PC in the analysis target system, and based on the history information tracking key, identifies a specific client from the history of operation of the client PC. A history information tracking key extraction unit that extracts system operation information, and information that identifies an object that is a starting point for calling an object in the program execution environment from the history of the Web container based on the history information tracking key Based on the information extracted and extracted from the history of the Web container, a history information related display data acquisition unit is provided that extracts information on all objects related to the call from a specific object as a starting point from the history of the program execution environment.

  According to an embodiment of the present invention, in information system maintenance work, it is possible to expect a reduction in lead time to the cause location when analyzing the cause of the failure of the information system.

The figure which shows the software configuration of a maintenance work support environment. The figure which shows hardware constitutions. The figure which shows the flow of history information related display. The figure which shows the example of the client operation history table stored in client operation history DB (111). The figure which shows the example of the web container history table stored in web container history DB (112). The figure which shows the example of the program execution environment execution history table stored in program execution environment execution history DB (113). The figure which shows the example of DB access history table stored in DB access history DB (114). The figure which shows the example of the external library information table stored in external library information DB (115). The figure which shows the detail of step (301) of a log | history information relevant display flow. The figure which shows the example of the client operation history list memorize | stored in a memory area (when taking a client operation history table (400) as an example). The figure which shows the screen of a history information related display tool (scene which selects a client operation history from a client operation history list). The figure which shows the detail of step (312) of a log | history information relevant display flow. The figure which shows the example of the history information relevant display data acquired by step (312) of a history information relevant display flow. The figure which shows the historical information relevant display data processed based on the external library information table (800). The figure which shows the detail of step (323) of a log | history information relevant display flow. The figure which shows the screen of a history information relevant display tool (scene which displayed history information relevant display data). The figure which shows the screen of a history information related display tool (the scene which displayed the history information related display data which aggregated the external library information).

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 shows a software configuration in the embodiment of the present invention.

  The software development environment for realizing the embodiment of the present invention is a specific series of processing contents based on the execution history information from the analysis target system (120) in the maintenance work of the analysis target system (120) as an information system. Extract and visualize.

  The history information tracking key extraction unit (101) extracts a “history information tracking key” for extracting a series of processing contents, and transmits it to the history information related display data acquisition unit (102).

  The history information related display data acquisition unit (102) collects information necessary for generating the history information related display data based on the acquired history information tracking key. The generated history information related display data is transmitted to the history information related display unit (103).

  The history information related display unit (103) processes the acquired history information related display data based on the external library information DB (115), converts it into visually displayable data, and displays it graphically.

  The client operation history DB (111) is a table related to history information such as operations on the browser of the client PC and information acquired from the communication contents when the client PC receives content such as JSP via the network (122). DB with

  The Web container history DB (112) is a DB having a table regarding the reception history of requests from the client PC via the network (122).

  The program execution environment execution history DB (113) is a DB having a table relating to the execution history of programs executed on the program execution environment (124).

  The DB access history DB (114) is a DB having a table relating to an access history to the DB (126).

  The external library information DB (115) is a DB having a table relating to a package to be displayed with an alias when displaying history information related display data.

  The analysis target system (120) includes a client PC (121), a Web container (123), a program execution environment (124), a JDBC driver (125), and a DB (126). The client PC (121) and the Web container ( 123) is a Web application system that cooperates via a network (122). A form in which a plurality of client PCs are connected to the network (122) is also possible.

  The client PC (121) is connected to the network (122), and can start, interact with, and disconnect a Web application through a browser.

  The Web container (123) reads the contents of the request from the client PC, acquires static contents such as html files and image files, and dynamic contents such as servlets and JSPs, and sends them to the client PC (121). Reply.

  The program execution environment (124) executes a program.

  The JDBC driver (125) provides an API that supports the connection between the program execution environment (124) and the DB (126) so that the program execution environment (124) can refer to, update, and write to the DB (126). To do.

  The DB (126) stores data used by the program.

  Details of each component will be described below.

  FIG. 2 shows a hardware configuration according to the embodiment of the present invention.

  A computer that arranges a maintenance work support environment that implements the embodiment of the present invention includes a CPU (201), a main storage device (202), a network connection device (203), an external storage device (204), a display (205), data It has an input device (206), a network (207), and the like. The CPU (201) executes the program read from the storage device and controls each device of the computer. A flow and operation process in an embodiment of the present invention described later is executed by the CPU (201).

  FIG. 3 is a processing flow of history information related display.

  This processing flow is activated by an arbitrary event in the maintenance work support environment that realizes the embodiment of the present invention. Here, the arbitrary event includes redisplay of history information of the analysis target system.

  Next, the history information tracking key extraction unit (101) acquires a client operation history list from the client operation history DB (111) and stores it in the memory area (301).

  Next, one client operation selected from the client operation history list on the memory is acquired (302).

  Next, the values of “request ID” and “session ID” are extracted from the selected client operation history as history information tracking keys (303) and transmitted to the history information related display data acquisition unit (102) (304).

  Next, the history information related display data acquisition unit (102) is activated by receiving the history information tracking key (311). Based on the received history information tracking key, the web container history DB (112), program execution Necessary information is collected from the client operation history list stored in the environment execution history DB (113), DB access history DB (114), and step (301), and history information related display data is generated (312).

  Next, the history information related display data acquisition unit (102) transmits the generated history information related display data to the history information related display unit (103) (313).

  Next, the history information related display unit (103) receives the history information related display data (321), and processes the history information related display data based on the external library information DB (115) (322). Here, depending on the setting, the history information related display data may not be processed.

  Next, the history information relation is graphically displayed based on the history information relation display data (323).

  Next, when another history information related display data is to be displayed, the process returns to the history information tracking key extraction unit (101). On the other hand, when no further display is performed, the process ends.

  FIG. 4 is an example of a client operation history table (400) belonging to the client operation history DB (111).

  The client operation history table (400) is a table for storing operation history information on the browser in the client PC. In this embodiment, items of the client operation history table (400) include “request ID”, “session ID”, “IP address”, “page name”, “operation type”, “operation target”, “acquisition order”. Cite.

  “Request ID” is an item for specifying a reply from the Web container (123), and the client PC (121) can be mechanically acquired from communication contents such as an http header when receiving contents such as an html file or JSP. Shall.

  The “session ID” is an item for identifying a client PC that has transmitted a request to the Web container (123) for a certain period of time. When the client PC (121) receives content such as an html file or JSP, In addition, it can be mechanically acquired from the contents of the HTTP header communication.

  The “IP address” is an item for identifying a client PC connected to the network (122), and “192.168.1.11” is assigned to the client PC (121).

  The “page name” is an item indicating the page name of the Web application that is the analysis target system (120), and can be realized by acquiring a character string sandwiched between html title tags. If the page name could not be obtained, a symbol such as a hyphen is substituted.

  The “operation type” is an item indicating the type of operation on the browser of the client PC. Using a point in time when a specific operation occurs on the browser as a trigger, acquire "request ID", "session ID", "IP address", "page name", "operation target", "acquisition order", and client operation It is assumed that the client operation history list table (400) belonging to the history DB (111) is stored. In this example, “button click” is the trigger target.

  The “operation target” is an item indicating the name of the page element that is the target when a specific operation occurs on the browser of the client PC. In this example, “clicking a button” is given as a specific operation, and therefore, a label name or the like attached to a button is acquired.

  “Acquisition order” is an item indicating the order in which a specific operation has occurred on the browser of the client PC. In this embodiment, the time of the client PC (121) is cited.

  The hyphen symbol (401) indicates that the operation history information could not be acquired. For example, a browser is simply launched on the client PC (121), and static content and dynamic content stored in the web container are displayed. When the URL indicating the URL is acquired by directly inputting it, the “request ID” and the “session ID” cannot be acquired. This is because the “request ID” and the “session ID” are assigned by the Web container (123), and the “request ID” and the “session ID” are not yet assigned to the newly launched browser. .

  Thus, from the page displayed on the browser, “request ID”, “session ID”, “IP address”, “page name”, “operation type”, “operation target” on the page displayed on the browser, As a specific method for mechanically acquiring the “acquisition time”, there is an Ajax (Asynchronous JavaScript and XML) technology (JavaScript is a registered trademark).

  FIG. 5 is an example of the web container history table (500) belonging to the web container history DB (112).

  The web container history table (500) is a table for storing history information of requests received by the web container (123). In this embodiment, “request ID”, “session ID”, and “root content name” are listed.

  The “request ID” is an item for specifying a request transmitted to the Web container (123), and is mechanically assigned at the timing when the Web container (123) receives a request from the client PC (121). Examples of request IDs include communication numbers assigned and managed by the web container itself for requests received by the web container. If there are multiple web containers, add the IP address of the web container. When the above program is activated, a process ID can be added and a set of them can be used as a request ID.

  “Session ID” is an item for specifying a client PC that has transmitted a request to the Web container (123) for a certain period of time, and is mechanically assigned at the timing when the request is transmitted to the Web container (123). Inherited. Specifically, if the Web container (123) does not hold the session ID, a new session ID is assigned. If the Web container (123) already holds the session ID, the Web container (123) already holds the session ID without assigning a new session ID. Inherits the current session ID. If the session ID is not used beyond the valid period, the session ID is discarded. In this example, it is assumed that the session ID is valid so long that the session ID is not automatically discarded when requests are continuously received from the client PC.

  The “root content name” is an item indicating the name of static content (such as an html file) or dynamic content (such as a servlet), and the web container (123) reads the content of the request from the client PC, and mechanically It is assumed that the file name of the content is acquired.

  FIG. 6 is an example of a program execution environment execution history table (600) belonging to the program execution environment execution history DB (113).

  The program execution environment execution history table (600) is a table storing a history information list of message transmission / reception between objects generated by a program executed in the program execution environment. In this example, “calling object ID”, “calling source information”, “calling source attached data”, “calling destination object ID”, “calling destination information”, “calling destination attached data”, and “acquisition order” are listed. Yes.

  The “caller object ID” is an item that identifies an object generated by a program executed on the program execution environment (124), and particularly refers to an item attached to an object that is a caller. It is given mechanically when an object is generated in the program execution environment (124) and can be obtained mechanically when a message is transmitted to another object. An example is a hash code of an object.

  “Caller 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 the present embodiment, a character string in which the “package name” and “class name” of the caller object and the “method name” that sent the message are connected by a period “.” Is used.

  “Caller attached data” is an item indicating data attached to the caller object. When an object such as a servlet is generated on the program execution environment (123) in response to a command from the Web container (123), the “session ID” of the request from the client PC (121) that requested the command can be acquired. . In other cases, nothing is acquired, and the program execution environment execution history table (600) indicates this by using a hyphen symbol.

  The “call destination object ID” is an item for specifying an object generated by a program executed on the program execution environment (124), and particularly refers to an item attached to an object to be called. It is given mechanically when an object is generated in the program execution environment (124), and can be obtained mechanically when a message is received from another object. An example is a hash code of an object.

  “Callee 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, a character string in which the “package name” and “class name” of the call source object and the “method name” of the message transmission destination are connected by a period “.” Is used.

  “Call destination attached data” is an item indicating data attached to the call destination object. When the program execution environment (124) accesses the DB (126) using the JDBC driver (125), the “connection ID” managed by the JDBC driver (125) can be acquired. In other cases, nothing is acquired, and the program execution environment execution history table (600) indicates this by using a hyphen symbol.

  The “acquisition order” is an item indicating the order in which a certain object transmits a message to another object. In this embodiment, the time in the program execution environment (124) is listed.

  FIG. 7 is an example of the DB access history table (700) belonging to the DB access history DB (114).

  The DB access history table (700) is a table for storing a history of accessing the DB (126). In this example, “connection ID”, “table name”, “SQL information”, and “acquisition order” are listed.

  “Connection ID” is an item for specifying a connection with the DB (126), and is managed by the JDBC driver (125).

  The “table name” is an item indicating the name of a table belonging to the DB (126) and can be acquired by analyzing the issued SQL sentence.

  “SQL information” is an item representing information obtained by analyzing an issued SQL sentence, and in this embodiment, issuance types such as Select and Update are listed.

  “Acquisition order” is an item indicating the order of access to the DB (126). In this embodiment, the time in the DB (126) is cited.

  FIG. 8 shows an example of the external library information table (800) belonging to the external library information DB (115).

  The external library information table (800) is a table that stores package names that are desired to be displayed using aliases when displaying history information related display data. In this embodiment, “package name” and “display name” are listed as items.

  “Package name” is an item indicating the name of a package defined as an external library.

  The “display name” is an item indicating the display name of the external library when displaying the history information related display data.

  Details of the steps of the history information related display flow (FIG. 3) will be described below.

  FIG. 9 shows, in step (301) of the history information tracking key extraction unit (101), the client operation history list stored in the client operation history table (400) belonging to the client operation history DB (111) is stored in the memory. It is a flow to do. Through this flow, “request ID”, “session ID” and operation information (“IP address”, “page name”, “operation type”, “operation object”, “acquisition order”) of the client operation history table (400). Correct the deviation.

  “Request ID” and “Session ID” are assigned when a request is transmitted to the Web container (123), while the client PC (121) is attached to a page displayed on the browser by a response to the request. It is acquired for the first time when a specific operation on the page is triggered. Therefore, what is stored as one record in the client operation history table (400) is operation information on a certain page, and “request ID” and “session ID” given to the request transmitted by the previous operation. . Specifically, the “request ID” and “session ID” in the client operation history (403) in FIG. 4 are the “page name”, “operation type”, “operation target”, and “acquisition” in the client operation history (402). It is given to a request sent by an operation having information such as “order”.

  This processing flow is always started when a client operation history list is acquired from the client operation history table (400).

  Next, the memory area a for storing the client investigation history list is initialized (901).

  Next, all “session IDs” stored in the client operation history table (400) belonging to the client operation history DB (111) are acquired so as not to overlap, and stored in the initialized memory area b (902). ).

  Next, the following processing is performed for each “session ID” stored in the memory area b (903 to 907).

  The client operation history including the same “session ID” is extracted from the client operation history table (400) (903), and rearranged in the order of “acquisition order” of each client operation history (904).

  Next, with respect to the list of client operation histories rearranged in the acquisition order, the “request ID” and “session ID” of the client operation history in a certain order are changed to the “request ID” of the previous client operation history, The process of replacing with the “session ID” is performed in order from the earliest (905). By this process, the “request ID” and “session ID” of the record at the top move to the bottom record.

  Next, the client operation history in the last order in the rearranged list of client operation histories is deleted (906), and stored / added to the memory area a (907).

  FIG. 10 shows an example of the client operation history list (1000) stored in the memory area as a result of the processing flow shown in FIG. 9 from the client operation history table (400) belonging to the client operation history DB (111). is there. In the present embodiment, “request ID”, “session ID”, “IP address”, “page name”, “operation type”, “operation target”, and “acquisition order” are listed as the client operation history.

  The “request ID” corresponds to the “request ID” in the client operation history table (400).

  The “session ID” corresponds to the “session ID” in the client operation history table (400).

  The “IP address” corresponds to the “IP address” in the client operation history table (400).

  The “page name” corresponds to the “page name” in the client operation history table (400).

  The “operation type” corresponds to the “operation type” in the client operation history table (400).

  The “operation target” corresponds to the “operation target” in the client operation history table (400).

  The “acquisition order” corresponds to the “acquisition order” in the client operation history table (400).

  FIG. 11 is a screen example (1101) of the history information related display tool for displaying the client operation history to the maintenance staff in step (302) of the history information tracking key extraction unit (101), which is displayed on the screen. This is a scene for selecting a specific client operation history from the client operation history list. In this embodiment, “IP address”, “page name”, “operation target”, “operation type”, and “acquisition order” are listed as the client operation history.

  The “IP address” corresponds to the “IP address” in the client operation history list (1000).

  The “page name” corresponds to the “page name” in the client operation history list (1000).

  The “operation target” corresponds to the “operation target” in the client operation history list (1000).

  The “operation type” corresponds to the “operation type” in the client operation history list (1000).

  The “acquisition order” corresponds to the “acquisition order” in the client operation history list (1000).

  It is assumed that the maintenance person who operates the history information related display tool can select the client operation history from the client operation history list by using an operation interface (1102) such as a check box. Further, it is possible to instruct whether or not external library information is applied to the history information displayed by the history information related display tool using an operation interface (1103) such as a check box. Depending on this instruction, it is possible to select whether or not to execute step (322) of the history information related display unit. Further, by performing an operation such as pressing an OK button (1104), the client history information selected by the operation interface (1103) can be transmitted to the history information tracking key extraction unit (102).

  FIG. 12 is a processing flow for extracting information necessary for generating history information related display data based on the received history information tracking key in step (312) of the history information related display data acquisition unit (102).

  This processing flow starts by acquiring a history information tracking key from the history information tracking key extracting unit (101).

  Next, the client operation history list (1000) stored in the memory area (memory area a) is stored by using the value of “request ID” and the value of “session ID” which are acquired history information tracking keys as keys. Each of “request ID” and “session ID” is searched, and “IP address”, “page name”, “operation object”, “operation type”, and “acquisition order” of the corresponding client operation history are acquired (1201). .

  Next, “request ID” and “session ID” of the web container history table (500) are searched using the value of “request ID” and the value of “session ID” as the acquired history information tracking key as keys. The value of “root content name” of the web container history obtained is acquired (1202), and “calling source information” and “calling source attached data” of the program execution environment execution history table (600) are obtained in step (1202), respectively. The value of the “calling object ID” in the program execution environment execution history table (600) that matches the value of the “root content name” and the value of the “session ID” that is the history information tracking key is acquired (1203). In this embodiment, the value of the “root content name” corresponds to the class name in the case of a servlet or the like, and has a character string obtained by connecting the package name, class name, and method name with a period as the “caller information”. Therefore, when searching for “caller information” in the program execution environment execution history (600), it is necessary to perform processing such as decomposing a character string.

  Next, all objects related to the call starting from the object having the value of the “caller object ID” acquired in the step (1203) are identified, and information on the call relation of these objects is obtained as the program execution environment execution history. The “calling source information”, “calling destination information”, “calling destination attached data”, and “acquisition order” of the table (600) are stored in the memory (1204). In the present embodiment, step (1204) is realized in the following order (1) to (7).

  (1) The ID (the value of “caller object ID”) of the object that is the call origin obtained in step (1203) is stored in the memory area A.

  (2) Using the value of the object ID stored in the memory area A as a key, the “calling object ID” of the program execution environment execution history table (600) is searched, and the “call destination object” of the corresponding program execution environment execution history ID ”is acquired so as not to overlap, and stored in the memory area B.

  (3) Using the object ID stored in the memory area B as a key, the “calling object ID” of the program execution environment execution history table (600) is searched, and the “call destination object” of the corresponding program execution environment execution history is searched. ID ”is acquired so as not to overlap, and is added to the memory area B.

  (4) In the memory area B, the object ID stored in duplicate is deleted.

  (5) The object ID used for the key is added to the memory area A and deleted from the memory area B.

  (6) Repeat (3) to (5) until there is no object ID stored in the memory area B.

  (7) Using the object ID stored in the memory area A as a key, search for “caller object ID” in the program execution environment execution history table (600), and sequentially obtain the corresponding program execution environment execution history. Go.

  Next, in the list of program execution environment execution histories stored in (1204), if data with a hyphen symbol is input in “call destination attached data”, the data is used as a key in the DB access history table (700). The “connection ID” is searched, the corresponding DB access history is sequentially acquired, stored in the memory (1205), and this processing flow ends.

  FIG. 13A shows an example (1301) of history information related display data related to the client operation acquired in step (1201) of the processing flow shown in FIG. In this embodiment, “IP address”, “page name”, “operation type”, “operation object”, and “acquisition order” are listed. “IP address” corresponds to “IP address” in the client operation history list (1000). The “page name” corresponds to the “page name” in the client operation history list (1000). The “operation type” corresponds to the “operation type” in the client operation history list (1000). The “operation object” corresponds to the “operation object” in the client operation history list (1000). The “acquisition order” corresponds to the “acquisition order” in the client operation history list (1000).

  FIG. 13B is an example (1302) of history information related display data related to the program execution environment acquired in step (1204) of the processing flow described in FIG. In this embodiment, “calling source information”, “calling source attached data”, “calling destination information”, “calling destination attached data”, and “acquisition order” are listed. “Caller information” corresponds to “caller information” in the program execution environment execution history table (600). “Caller-attached data” corresponds to “caller-attached data” in the program execution environment execution history table (600). “Call destination information” corresponds to “call destination information” in the program execution environment execution history table (600). The “call destination attached data” corresponds to “call destination attached data” in the program execution environment execution history table (600). The “acquisition order” corresponds to the “acquisition order” in the program execution environment execution history table (600).

  FIG. 13C is an example (1303) of history information related display data related to DB access acquired in step (1205) of the processing flow described in FIG. In this embodiment, “connection ID”, “table name”, “SQL information”, and “acquisition order” are listed. The “connection ID” corresponds to the “connection ID” in the DB access history table (700). The “table name” corresponds to the “table name” of the DB access history table (700). “SQL information” corresponds to “SQL information” in the DB access history table (700). The “acquisition order” corresponds to the “acquisition order” in the DB access history table (700).

  FIG. 14 is an example (1400) of history information related display data processed with reference to the external library information table (800) in step (322) of the history information related display data acquisition unit (103), and the program execution environment A specific package is converted into an alias based on the history information related display data example (1302). In particular, “caller information” in the history information related display data (1401, 1402, 1403) relating to the program execution environment corresponds to the “package name” in the external library information table (800), and each of the external library information table (800). It has been converted to “Display Name”.

  FIG. 15 is a processing flow for displaying history information related display data in step (323) of the history information related display unit (103).

  This processing flow is activated when history information related display data is received from the history information related display data acquisition unit (102).

  Next, “page” and “operation target” are drawn based on the history information related display data (1301) regarding the client operation (1501), and “caller attached data” of the history information related display data (1302) regarding the program execution environment is drawn. "Package", "Class", and "Method" are drawn based on "Caller information" of the record that has a value in "" (1502), and an arrow connecting "Method" to the drawn "Operation target" is drawn (1503).

  Next, the record with the earlier “acquisition order” is selected from the history information related display data (1302) related to the program execution environment (1504), and the record is not drawn from the “caller information” and “callee information” of the record. “Package”, “class”, and “method” are added (1505), and an arrow from “method” indicated by “caller information” of the selected record to “method” indicated by “callee information” is drawn. If not, an arrow is drawn (1506).

  Next, if there is no value in the “call destination attached data” of the record of the history information related display data (1302) related to the program execution environment selected in step (1504), the record selected in step (1504) is stored. It is deleted from the memory area (1509). On the other hand, if a value is entered in “call destination attached data”, “connection ID” of the history information related display data (1303) related to DB access is searched using the value as a key, and the “connection ID” is If the “table” shown is not drawn, it is drawn (1507). If the arrow from “method” to “table” indicated by “caller information” in the record of the history information related display data (1302) relating to the program execution environment selected in step (1504) is not drawn, it is drawn (1508). ). Finally, the record of the history information related display data (1302) relating to the program execution environment selected in step (1504) is deleted from the memory (1509).

  Next, when a record remains in the history information related display data (1302) relating to the program execution environment, the process returns to step (1504), and when there is no record, the process flow ends.

  FIG. 16 shows a history information related display screen example (1600) in which history information related display data is displayed in another window by the history information related display tool in step (323) of the history information related display unit (103).

  “Page02” of the PC display type icon (1601) representing the page corresponds to “page name” of the history information related display data (1301) related to the client operation history. “Label002” of the rounded square icon (1602) corresponds to “operation target” of the history information related display data (1301). The upper label (1603) on the arrow from the rounded square icon corresponds to the “IP address” of the history information related display data (1301) related to the client operation history. The middle label (1604) on the arrow coming out of the rounded square icon corresponds to the “acquisition order” of the history information related display data (1301) related to the client operation history. The lower label (1605) on the arrow from the rounded square icon corresponds to the “operation type” of the history information related display data (). “P001” of a square icon (1606) having a square on the left shoulder represents a package name, and “calling source information” or “calling destination information” of history information related display data (1302) related to the program execution environment execution history. This corresponds to the first character string from the left among the character strings separated by two periods. “Servlet001” of the square icon (1607) represents a class name, and in the character string of “calling source information” or “calling destination information” of the history information related display data (1302) related to the program execution environment execution history, Corresponds to the second character string from the left, separated by two periods. “M001” of the elliptical icon (1608) represents a method name, and in the character string “calling source information” or “calling destination information” of the history information related display data (1302) related to the program execution environment execution history. Corresponds to the third character string from the left, separated by two periods. “Table001” of the square icon (1609) partitioned by the grid corresponds to “table name” of the history information related display data (1303) related to the DB access history. “SELECT” of the label (1610) on the arrow pointing to the square icon partitioned by the grid corresponds to “SQL information” of the history information related display data (1303) related to the DB access history. A maintenance worker who operates the history information related display tool closes the history information related display screen (1600) and displays another history information related display screen by an operation such as pressing the Close button (1611). You can move on to action.

  FIG. 17 shows a history information related display in which a specific package is converted by another name using the external library information DB (115) by the history information related display tool in step (323) of the history information related display unit (103). It is a history information related display screen example (1800) in which data is displayed in another window.

  Icons having “P801” and “P901” as package names on the history information related display screen example (1600) are grouped into icons having “Ext” as the package name on the history information related display screen example (1700). ing.

Claims (6)

A maintenance work support system that supports maintenance work by visualizing history information of a target Web system,
The history information tracking key is extracted from the history of the client system operation in the analysis target system, and the operation information of the specific client system is extracted from the history of the client system operation based on the history information tracking key. A history information tracking key extraction unit;
Based on the history information tracking key, information for identifying an object that is a starting point for calling an object in the program execution environment is extracted from the history of the Web container, and the program is extracted based on the information extracted from the history of the Web container. A history information related display data acquisition unit that extracts information on all objects related to the call from a specific object as a starting point from the history of the execution environment,
A maintenance work support system characterized by comprising: In the maintenance work support system according to claim 1,
Based on the history information tracking key, all the objects related to the call starting from a specific object, extracted from the client system operation information extracted from the client system operation history and the program execution environment history History information related display section for displaying the information of,
A maintenance work support system characterized by comprising: In the maintenance work support system according to claim 1,
The history information related display data acquisition unit
A maintenance work support system, which extracts database access information from a history of database connection APIs for object-oriented languages based on information on all objects related to a call originating from the specific object. In the maintenance work support system according to claim 3,
Based on the history information tracking key, the client system operation information extracted from the client system operation history and all calls related to the call starting from the specific object extracted from the program execution environment history. A history information related display unit for displaying object information and database access information extracted from the history of the database connection API group for the object-oriented language;
A maintenance work support system characterized by comprising: In the maintenance work support system according to claim 2,
Maintenance work characterized in that a history information related display unit restricts information of all objects related to a call starting from a specific object extracted from the history of the program execution environment with reference to external library information Support system. In the maintenance work support system according to claim 4,
The history information related display section
A maintenance work support system, which refers to the external library information and restricts information on all objects extracted from the history of the program execution environment and related to a call starting from a specific object.

Images