JP2008226017A - Log information generation device and method, log information management device and method, and log information management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To rapidly collect all pieces of log information related to a plurality of processing for attaining a certain function without needing a session information table or recursive processing as in the past. <P>SOLUTION: An ESB server (1) 103 receives calling of corresponding processing of a plurality of processing to be executed in linkage for attaining a series of functions, and generates additive information that is used in common among the plurality of processing and unique between a certain function and the other function when the received processing is processing for which the calling is received first of the plurality of processing. The ESB server (1) 103 adds the generated additive information to a message used to call the plurality of processing, calls other processing using the message, and generates log information related to the executed processing, including the additive information. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technique for collecting and managing log information relating to a plurality of processes executed in cooperation to realize a series of functions.

  Conventionally, log information has been taken in order to keep a record of computer usage status, error status, and the like. The contents recorded in the log information include various events from a message indicating the operation of the computer to an error message indicating an emergency, and are recorded in a normal time series for each system.

  In recent years, a series of functions have been realized by linking a plurality of systems and services. In this case, one piece of log information that a user can usually view at a time includes a part of history information in a series of processing flows that the user wants to see. Only. Therefore, in order for the user to grasp the history of a series of processes, all log information is obtained from all related servers, necessary information is extracted from the log information, and log information along the series of process flows. Work to integrate. However, it is considered impossible to collect and integrate logs in the case where a large number of services like the current ones are complexly linked.

  For example, Patent Document 1 discloses an idea of collecting log information from a plurality of systems. The invention disclosed in Patent Document 1 records session information that is included in log information held by a server and is assigned to each process using log information in a session information management table, and also includes sessions between different log information. Information correspondence is recorded in the session information correspondence table. By recursively searching the session information correspondence table from the session information instructed by the user through the display location input unit, a series of session information related to the process that the user is paying attention to is specified.

JP 2004-227360 A

  However, the invention disclosed in Patent Document 1 is provided with different unique session information for each server (Web server, AP server, DB server), and the related session information indicating the relationship with other servers and the unique session information. The association of session information is determined by associating with session information. As described above, in the invention disclosed in Patent Document 1, since related session information is associated with different session information, a session information correspondence table and a process using the session information are required, and time is reduced. Necessary recursive call processing is required.

  In the invention disclosed in Patent Document 1, in the Web system, since the same session ID is used as long as the session from login to logout is valid, the related log information is enormous. It becomes.

  Furthermore, in the invention disclosed in Patent Document 1, the session information necessary for the analysis of log information is systematic for cooperative operation between distributed systems, and the end user of the client can know it. Have difficulty.

  Therefore, an object of the present invention is to enable quick collection of log information related to a plurality of processes for realizing the function without requiring a session information table or recursive processing as in the prior art. .

  Another object of the present invention is to make it possible to easily analyze log information by limiting the collection target of related log information.

  Another object of the present invention is to make it easy to grasp the history of a plurality of related processes.

A first aspect of the log information generation device of the present invention is a reception unit that receives a call of a corresponding process among a plurality of processes that are executed in cooperation to realize a series of functions, and is called by the reception unit. Is the information that is used in common among the plurality of processes and is unique between the function and another function. The additional information generating means for generating additional information, and the additional information generated by the additional information generating means is added to a message used when calling the plurality of processes, and the message to which the additional information is added A process execution unit that executes the process including a process of calling another process using the log, and log information related to the process executed by the process execution unit. And having a log information generating means for generating including.
According to a second aspect of the log information generating apparatus of the present invention, a reception unit that receives a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions, and the plurality of processes When additional information that is used in common among the plurality of processes and additional information that is unique between the function and another function is added to the message used when calling, the call by the reception unit In response to acceptance, a process execution means for executing the process including a process for calling another process using the message to which the additional information is added, and a log relating to the process executed by the process execution means Log information generating means for generating information including the additional information.
The log information management device according to the present invention is used in common among a plurality of processes executed in cooperation to realize a series of functions, and is an additional information that is unique between the functions and other functions. Log information acquisition means for acquiring log information relating to the plurality of processes including information; and log information management means for managing log information relating to the plurality of processes acquired by the log information acquisition means. And
A first aspect of the log information generation method of the present invention is a log information generation method by a log information generation device, and the corresponding process among a plurality of processes executed in cooperation to realize a series of functions A reception step that accepts a call, and a process that accepts a call in the acceptance step is a process that accepts a call first among the plurality of processes, and is used in common among the plurality of processes, and the function An additional information generation step for generating additional information that is unique information between the function and other functions, and a message used when the additional information generated by the additional information generation step is called to the plurality of processes. A process execution step of executing the process including a process of calling another process using the message to which the additional information is added; Log information relating to the serial processing execution executed by step the process, characterized in that it comprises a log information generating step of generating including the additional information.
A second aspect of the log information generation method of the present invention is a log information generation method by a log information generation device, and corresponding processing among a plurality of processes executed in cooperation to realize a series of functions The reception step for accepting a call to the message and the message used when calling the plurality of processes are added in common between the plurality of processes and unique information between the function and the other functions When information is added, a process execution step of executing the process including a process of calling another process using the message to which the additional information is added in response to reception of a call by the reception step; A log information generation step for generating log information related to the processing executed in the processing execution step, including the additional information.
The log information management method of the present invention is a log information management method by a log information management device, and is used in common among a plurality of processes executed in cooperation to realize a series of functions. A log information acquisition step for acquiring log information related to the plurality of processes including additional information that is unique information with other functions;
And a log information management step for managing log information related to the plurality of processes acquired by the log information acquisition step.
A first aspect of the program of the present invention is a program for causing a computer to execute a log information generation method by a log information generation device, and a plurality of processes executed in cooperation to realize a series of functions. Of these, the reception step for receiving a call to the corresponding process, and the process that has received the call at the reception step is a process that has received a call first among the plurality of processes, and is used in common among the plurality of processes And an additional information generation step for generating additional information that is unique information between the function and another function, and when the additional information generated by the additional information generation step is called to the plurality of processes. Before including a process of adding another message to the message used for calling and calling another process using the message with the additional information added A process executing step of executing the process, log information relating to the processing performed is performed by step the process, characterized in that to execute a log information generating step of generating including the additional information to the computer.
A second aspect of the program of the present invention is a program for causing a computer to execute a log information generation method by a log information generation device, and a plurality of processes executed in cooperation to realize a series of functions. Among them, a reception step for receiving a call to the corresponding process and a message used when calling the plurality of processes are used in common between the plurality of processes and unique between the function and another function. When the additional information, which is a large amount of information, is added, the process including the process of calling another process using the message to which the additional information is added is executed in response to the reception of the call by the reception step. Log information for generating a process execution step and log information related to the process executed in the process execution step, including the additional information Characterized in that to execute the forming step in the computer.
A third aspect of the program of the present invention is a program for causing a computer to execute a log information management method by a log information management apparatus, and a plurality of processes executed in cooperation to realize a series of functions. Log information acquisition step for acquiring log information related to the plurality of processes including additional information that is used in common and unique information between the function and another function, and acquired by the log information acquisition step And a log information management step for managing log information related to the plurality of processes.

  In the present invention, when a call is received first among a plurality of processes executed in cooperation to realize a series of functions, the function is used in common between the plurality of processes, and Additional information that is unique to the function is generated. Then, another process is called using the message with the additional information added, and log information related to the process is generated including the additional information. As described above, since the other process is called using the message to which the additional information is added, log information relating to the other process can be generated including the additional information. Accordingly, since all log information related to the plurality of processes can be generated including additional information, by using this additional information, there is no need for a session information table or a recursive process as in the past. It is possible to quickly collect log information related to a plurality of processes for realizing the function.

  In addition, as described above, in the present invention, it is possible to add unique additional information for each function having a higher occurrence frequency than the session and collect log information based on the added additional information. The collection target is more limited, and log information can be easily analyzed.

  Furthermore, in the present invention, log information indicating the history of processing is collected instead of using session information that a general user cannot know as in the past. It becomes possible to grasp.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments to which the invention is applied will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram schematically showing an overall configuration of a log information collection system according to an embodiment of the present invention. As shown in FIG. 1, the log information collection system according to this embodiment includes a client PC 101, a screen AP server 102, a system A, a system B, and a log management system 110. In this embodiment, each server in the system A and the system B can cooperate to realize a series of functions. It should be noted that the system configuration shown in FIG. 1 is merely an example, and it goes without saying that various configurations can be adopted.

  The client PC 101 is a terminal operated by a user. By operating the client PC 101, the user can instruct the system A and the system B to execute the service and refer to the result on the screen of the client PC 101.

  The screen AP server 102 constructs screen information to be transmitted to the client PC 101, transmits instruction information input on the client PC 101 to the systems A and B and the log management system 110, Information received from the log management system 110 is transmitted to the client PC 101.

  The log management system 110 can acquire and manage access logs from the servers in the systems A and B, and can search and output an access log corresponding to a search key designated by the client PC 101. Similarly, the log management system 110 can acquire and output a detailed log from a server designated by the client PC 101.

  As shown in FIG. 1, the system A includes an ESB (Enterprise Service Bus) server (1) 103, a back AP server (1) 104, a back AP server (2) 105, and a gateway server (1) 106.

  The ESB server (1) 103 first receives a request from the client PC 101 via the screen AP server 102, and serves as an interface for calling a service executed by another server in the system A or a server in the system B. It is a server that fulfills

  The back AP server (1) 104 and the back AP server (2) 105 are one of servers that execute the main part of the service requested from the client PC 101. For example, when an order processing service is requested from the client PC 101, the back AP server (1) 104 executes a service for instructing execution of each service constituting the order processing service. The back AP server (2) 105 is a server that executes an order service, which is one of the main parts of the order processing service, and outputs the result as a response. Note that “service” in this description means processing by a computer and does not mean a human service.

  The gateway server (1) 106 is a server for controlling the network connection between the system A and the system B.

  The system B includes a gateway server (2) 107, an ESB server (2) 108, and a back system server (3) 109.

  The gateway server (2) 107 is a server for controlling the network connection between the system A and the system B.

  The ESB server (2) 108 is a server that calls the service of the back AP server (3) 109 in response to the service call from the system A via the gateway server (2) 107.

  The back AP server (3) 109 is one of servers that execute the main part of the service requested from the client PC 101. For example, when an order processing service is requested from the client PC 101, the back AP server (3) 109 is a server that executes an inventory service, which is one of the main parts of the order processing service, and outputs the result as a response. is there.

  The log management system 110 includes an access log collection storage unit 113, an access log storage table 114, a log display search unit 112, and a detailed log search acquisition unit 111.

  The access log collection storage unit 113 collects access logs from each server and stores them in the access log storage table 114.

  The log display retrieval unit 112 retrieves a corresponding access log from the access log storage table 114 using a footprint number described later as a key, and transmits the retrieval result to the client PC 101.

  The detailed log search acquisition unit 111 acquires a detailed log from a server designated by the client PC 101. Which server holds the detailed log is managed in a master table (not shown) in the log management system 110.

  FIG. 2-1 shows functional configurations of the ESB server (1) 103, the back AP server (1) 104, the back AP server (2) 105, the ESB server (2) 108, and the back AP server (3) 109. FIG.

  As shown in FIG. 2A, the ESB server (1) 103, the back AP server (1) 104, the back AP server (2) 105, the ESB server (2) 108, and the back AP server (3) 109 are , A reception unit 2101, a footprint number generation unit 2102, a digital signature generation unit 2103, a processing execution unit 2104, an access log generation unit 2105, an error detection unit 2106, and a notification unit 2107.

  The accepting unit 2101 accepts a process call message from another device. The footprint number generation unit 2102 generates a footprint number when the footprint number is not included in the message received by the reception unit 2101.

  The digital signature generation unit 2103 generates a digital signature using the footprint number generated by the footprint number generation unit 2102.

  If a footprint number is included in a message from another device, the process execution unit 2104 executes the process that received the call, and includes the footprint number in the message and calls the next target process. I do. On the other hand, if the footprint number is not included in the message from the other device, the received process is executed and the footprint number generated by the footprint number generation unit 2102 and the digital signature generation unit 2103 are generated. The digital signature is included in the message, and the target process is called next.

  The access log generation unit 2105 generates an access log that is history information related to the process executed by the process execution unit 2104.

  FIG. 2B is a block diagram illustrating a functional configuration of the gateway server (1) 106 and the gateway server (2) 107. As shown in FIG. 2B, the gateway server (1) 106 and the gateway server (2) 107 have the same configuration as 2101 to 2107 shown in FIG.

  The authentication unit 2108 performs an authentication process based on a digital signature included in a message from another device.

  3 shows ESB servers (1) to (2) 103, 108, gateway servers (1) to (2) 106, 107, back AP servers (1) to (3) 104, 105, 109, and logs. 2 is a block diagram illustrating a hardware configuration of a management system 110. FIG.

  In FIG. 3, the CPU 201 comprehensively controls each device and controller connected to the system bus. The ROM 203 and HD (hard disk) 209 have a BIOS (Basic Input / Output System) executed by the CPU 201, ESB servers (1) to (2) 103 and 108, gateway servers (1) to (2) 106 and 107, back The system AP servers (1) to (3) 104, 105, 109, and the log management system 110 store programs for executing processing described below.

  In particular, the detailed log search acquisition unit 111, the log display search unit 112, and the access log collection storage unit 113 of the log management system 110 are loaded with a program corresponding to the RAM 202 described later from the HD 209 according to an instruction from the CPU 201 and executed by the CPU 201. It is a function realized by doing. The access log storage table 114 is data stored in a partial storage area of the HD 209 or the RAM 202.

  In the example of FIG. 3, the HD 209 is configured to be disposed inside the device. However, as another embodiment, a configuration corresponding to the HD 209 may be configured to be disposed outside the device. The program may be recorded on a computer-readable recording medium such as a flexible disk (FD) or CD-ROM, and supplied from the recording medium, or supplied via a communication medium such as the Internet. It is good also as a structure to be made.

  The RAM 202 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program and data necessary for execution of processing into the RAM 202 and executing the program.

  The HD 209 and the FD 208 function as an external memory. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 202 and executing the program.

  The disk controller 207 controls access to external memories such as the HD 209 and the FD 208. The communication I / F controller 206 is connected to the Internet or a LAN, and controls communication with the outside by, for example, TCP / IP.

  The display controller 210 controls image display on the display 211.

  The KB controller 204 receives an operation input from the KB (keyboard) 205 and transmits it to the CPU 201. Although not shown, in addition to the KB 205, a pointing device such as a mouse is also applicable as a user operation means.

  FIG. 4 is a sequence chart showing an operation flow between the servers in the log information collection system according to the present embodiment. Here, a case where an order processing service is requested from the client PC 101 will be described as an example.

  When receiving the order processing service request from the client PC 101, the screen AP server 102 transmits the service request to the ESB server (1) 103 (step S301). This order processing service request includes a message.

  FIG. 8 is a diagram conceptually illustrating an example of the message. As shown in FIG. 8, the message includes a <common information> item and an <individual message: order> item.

  In the <common information> item, a footprint number, a digital signature, client information, and the like can be stored, but a message at the time of transmission from the screen AP server 102 to the ESB server (1) 103 includes: The footprint number and digital signature are not yet stored. The <individual message: order> item includes a <header> item and a <detail> item. The <header> item stores a reception order date, a customer name, and a customer order number. The <detail> item stores the item, quantity, delivery date, and delivery destination of each detail regarding the order.

  When the ESB server (1) 103 receives such a message from the screen AP server 102 by the receiving unit 2101, the ESB server (1) 103 adds a footprint number to the message shown in FIG. The footprint number includes a company identifier, a numbering system name, a date, a date and time, and a sequence number. The footprint number is a number that is commonly used among a plurality of processes for realizing the order processing service (the order processing function), and the order processing service (the order processing function) and other functions. It is a number that is assigned so that it is always unique.

  The company identifier is an identifier of the company of the system A to which the ESB server (1) 103 belongs. The numbering system name is the name of the system to which the footprint number is assigned, and here is the name of the numbering system in the ESB server (1) 103. The date and date / time are the date and date / time given with the footprint number. The sequence number is a sequence number in the ESB server (1) 103 that is updated each time the ESB server (1) 103 assigns a footprint number.

  The ESB server (1) 103 generates a digital signature by applying a hash function process and an encryption process using a secret key to the footprint number, and adds it to the message. The ESB server (1) 103 executes a service (Order Process Routing) that gives an instruction to call the back AP server (1) 104 using the message with the footprint number and the digital signature shown in FIG. (Steps S302 and S303). After steps S302 and S303, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

  When the back AP server (1) 104 receives a call from the ESB server (1) 103 by the accepting unit 2101, the back AP server (1) 104 uses the message shown in FIG. Process) is executed (steps S304 and S335). After steps S304 and S335, an access log related to these processes including the footprint number is generated in the back AP server (1) 104 by the function of the access log generation unit 2105.

  The ESB server (1) 103 receives an instruction for calling the order processing service from the receiving unit 2101, and also uses the message shown in FIG. 8 to call a service (Inventory Routing) that is one of the order processing services. ) Is executed (steps S305 and S306). Since the inventory service is a service executed by the back AP server (3) 109 of the system B, the call here is made to the gateway server (1) 106. After steps S305 and S306, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

  When the gateway server (1) 106 receives a call from the ESB server (1) 103 by the accepting unit 2101, the gateway server (1) 106 executes a service (Inventory GW) for calling the gateway server (2) 107 using the message shown in FIG. (Steps S307 and S308). After steps S307 and S308, an access log related to these processes including the footprint number is generated in the gateway server (1) 106 by the function of the access log generation unit 2105.

  When the gateway server (2) 107 receives a call from the gateway server (1) 106 by the accepting unit 2101, the gateway server (2) 107 executes a service (Inventory GW) for calling the ESB server (2) 108 using the message shown in FIG. (Steps S309 and S310). In step S309, the gateway server (2) 107 opens the digital signature in the message with the sender's public key held in advance, and hashes the hash value obtained by the opening and the footprint number in the message. Authentication is performed by checking the result of function processing. As a result of authentication, if both match, a service (Inventory GW) that calls the ESB server (2) 108 is executed. Further, after steps S309 and S310, an access log related to these processes including the footprint number is generated in the gateway server (2) 107 by the function of the access log generation unit 2105.

  When the ESB server (2) 108 receives a call from the gateway server (2) 107 by the accepting unit 2101, the service (Inventory Routing) calls the back AP server (3) 109 using the message shown in FIG. Are executed (steps S311 and S312). After steps S 311 and S 312, an access log related to these processes including the footprint number is generated in the ESB server (2) 108 by the function of the access log generation unit 2105.

  When the back AP server (3) 109 receives a call from the ESB server (2) 108 by the reception unit 2101, the back AP server (3) 109 executes an inventory service (Inventory Service) corresponding to the message shown in FIG. The message shown in FIG. 8 is transmitted to the ESB server (2) 108 together with the inventory service result (steps S313 and S314). After steps S313 and S314, an access log related to these processes including the footprint number is generated in the back AP server (3) 109 by the function of the access log generation unit 2105.

  When the ESB server (2) 108 receives a call from the back AP server (3) 109 by receiving the inventory service result and the message shown in FIG. 8 by the receiving unit 2101, the ESB server (2) 108 sends the inventory service result and the message shown in FIG. It transmits to the server (2) 107 (steps S315 and S316). After steps S315 and S316, an access log related to these processes including the footprint number is generated in the ESB server (2) 108 by the function of the access log generation unit 2105.

  When the gateway server (2) 107 receives a call from the ESB server (2) 108 by receiving the inventory service result and the message shown in FIG. 8 by the reception unit 2101, the gateway server (2) 107 sends the inventory service result and the message shown in FIG. 1) Transmit to 106 (steps S317 and S318). After steps S317 and S318, an access log related to these processes including the footprint number is generated in the gateway server (2) 107 by the function of the access log generation unit 2105.

  When the gateway server (1) 106 receives a call from the gateway server (2) 107 by accepting the inventory service result and the message shown in FIG. 8 by the accepting unit 2101, the gateway server (1) 106 sends the inventory service result and the message shown in FIG. 1) Transmit to 103 (steps S319 and S320). In step S319, upon receiving the inventory service result and the message shown in FIG. 8, the gateway server (1) 106 opens the digital signature with the public key of the sender held in advance, and the hash value obtained by opening The authentication is performed by comparing the footprint number in the message with the result of hash function processing. As a result of the authentication, if both match, the gateway server (1) 106 transmits the inventory service result and the message shown in FIG. 8 to the ESB server (1) 103. Further, after steps S319 and S320, an access log related to these processes including the footprint number is generated in the gateway server (1) 106 by the function of the access log generation unit 2105.

  The ESB server (1) 103 transmits the inventory service result and the message shown in FIG. 8 to the back AP server (1) 104 that has instructed the order processing service (steps S321 and S322). After steps S321 and S322, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

  When the back AP server (1) 104 receives a call from the ESB server (1) 103 by accepting the inventory service result and the message shown in FIG. 8 by the accepting unit 2101, the back AP server (1) 104 recognizes the inventory service result, as shown in FIG. The message is returned to the ESB server (1) 103 (steps S323 and S324). After steps S323 and S324, an access log related to these processes including the footprint number is generated in the back AP server (1) 104 by the function of the access log generation unit 2105.

  The ESB server (1) 103 executes a service (Order Routing) for calling an order service, which is one of the order processing services, using the message shown in FIG. 8 (Steps S325 and S326). Since the order service is a service executed by the back AP server (2) 105, the call here is directly made to the back AP server (2) 105. Further, after steps S325 and S326, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

  When the back AP server (2) 105 receives a call from the ESB server (1) 103 by the accepting unit 2101, the back AP server (2) 105 executes an order service (Order Service) corresponding to the message shown in FIG. The message shown in FIG. 8 is transmitted to the ESB server (1) 103 together with the order service result (steps S327 and S328). After steps S327 and S328, an access log related to these processes including the footprint number is generated in the back AP server (2) 105 by the function of the access log generation unit 2105.

  The ESB server (1) 103 transmits the order service result and the message shown in FIG. 8 to the back AP server (1) 104 that has instructed the order processing service (steps S329 and S330). After steps S329 and S330, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

When the back AP server (1) 104 receives a call by receiving the order service result and the message shown in FIG. 8 from the ESB server (1) 103 by the receiving unit 2101, the back AP server (1) 104 recognizes the order service result and shows the result shown in FIG. Along with the message, the order processing service result information reflecting the inventory service result and the order service result is returned to the ESB server (1) 103 (steps S331 and S332). After steps S331 and S332, an access log related to these processes including the footprint number is generated in the back AP server (1) 104 by the function of the access log generation unit 2105.

  The ESB server (1) 103 transmits the result information of the order processing service to the screen AP server 102 (steps S333 and S334). After steps S333 and S334, an access log related to these processes including the footprint number is generated in the ESB server (1) 103 by the function of the access log generation unit 2105.

  The screen AP server 102 generates screen information based on the result information of the order processing service and transmits it to the client PC 101. The client PC 101 displays screen information, and the user can refer to the result information of the order processing service.

  FIG. 5 is a flowchart showing a flow of footprint number numbering processing by the servers 103 to 109.

  The servers 103 to 109 determine whether or not the footprint number is included in the message received by the receiving unit 2101 (step S401). If the footprint number is included (step S401 / NO), the real numbering process ends. On the other hand, when the footprint number is not included (step S401 / YES), the footprint number generation unit 2102 generates a footprint number composed of the company identifier, the numbering system name, the date, the date and time, and the sequence number. The footprint number is stored in the message by the function of the execution unit 2104 (steps S402 and S403). At the same time, the servers 103 to 109 generate a hash value using the hash function of the footprint number generated in step S402 by the function of the digital signature generation unit 2103, encrypt the generated hash value with a secret key, and encrypt the hash Generate the value as a digital signature. And it stores in a message by the function of the process execution part 2104 (step S404, S405, S406). As a result, a message as shown in FIG. 8 is generated.

  FIG. 6 is a flowchart showing the flow of message authentication processing based on a digital signature. In this embodiment, this process is a process executed by the gateway servers (1), (2) 106, 107 between the systems A and B.

  The gateway servers 106 and 107 determine whether or not a digital signature is included in the message received by the receiving unit 2101 (step S501). If the digital signature is not included (step S501 / NO), the message is authenticated and the authentication process is terminated. On the other hand, when the digital signature is included (step S501 / YES), the gateway servers 106 and 107 open the digital signature with the public key of the sender held in advance by the function of the authentication unit 2108, and open the digital signature. It is determined whether or not the obtained hash value matches the hash value obtained by performing the hash function process on the footprint number in step S503 (steps S502 and S504). If both hash values match (step S504 / YES), the message is authenticated and the authentication process ends. On the other hand, if the two hash values do not match (step S504 / NO), the message is rejected and the authentication process is terminated.

  As described above, in the authentication process according to the present embodiment, when a call is received from a server belonging to another system, the server that has received the call performs the authentication process. This makes it possible to prevent falsification and impersonation that occur in the process of multiple systems when, for example, systems deployed between different companies call processing, and the original client (client It is possible to accurately transmit the intention of the user of the PC 101.

  FIG. 9 is a diagram for explaining an operation when the log management system 110 collects access logs generated by the servers 103 to 109.

  The access log is history information of the process generated every time the corresponding server executes the process. Further, these access logs are generated in a format including footprint numbers in received messages. Each of the servers 103 to 109 includes a transmission agent that is software for transmitting an access log. The transmission agent selects only the data required by the log management system 110 from the access log generated in a format unique to the server, and generates an access log for transmission to the log management system 110. Then, the transmission agent transmits the generated transmission access log to the log management system 110 as needed. At this time, the access log once transmitted is stored in a recording area different from the untransmitted access log so as not to transmit the same access log to the log management system 110 repeatedly.

  When the access collection storage unit 113 of the log management system 110 receives an access log from the transmission agents of the servers 103 to 109, the access collection storage unit 113 stores the received access log in the access log storage table 114.

  FIG. 10 is a diagram conceptually showing the structure of the access log stored in the access log storage table 114.

  As shown in FIG. 10, the access log stored in the access log storage table 114 includes a time stamp, a log system ID, a footprint number, a service name, an operation name, a transmission / reception category, and a BODY category.

  The time stamp is the date and time when the access log is generated in the corresponding server. The log system ID is identification information of the system that generated the access log. The footprint number is information configured by the ESB server (1) 113 in this embodiment, which includes a company identifier, a numbering system name, a date, a date, and a sequence number. The service name is a name of a service executed in the corresponding server. The operation name is the name of an operation that is actually executed in the service indicated by the service name. The transmission / reception classification indicates whether the operation indicated by the operation name is an operation for response (response) or an operation for request (request). In the BODY category, “Fault” is recorded when an error occurs due to the operation.

  FIG. 10 illustrates an access log group extracted from the access log storage table 114 using one footprint number (Company-SystemA-20061128-13253200-324) as a key. In the actual access log storage table 114, FIG. Stores an access log group of various footprint numbers.

  When the log management system 110 receives a footprint number as a search key from the client PC 101, the log management system 110 searches for an access log that matches the footprint number, and transmits the search result to the screen AP server 102. The screen AP server 102 performs image processing so that the search result can be referred to on the client PC 101, and transmits the image-processed data to the client PC 101. Thereby, the client PC 101 can display the search result of the access log in a state that the user can visually recognize.

  In addition, each server 103 to 109 detects an error in a process to be executed in response to a call by using the function of the error detection unit 2106. When the error detection unit 2106 detects the occurrence of an error, the notification unit 2107 notifies the client PC 101 of the footprint number in the message used for calling the process in which the error has occurred. When the user refers to the footprint number notified by the client PC 101 and wants to trace the cause of the error, the user designates the footprint number on the log display search screen to be described later, and a series of functions (FIG. In the example of 4, it is possible to refer to access logs related to a plurality of processes executed in cooperation in order to realize an order processing service.

  FIG. 11 is a diagram illustrating an example of a log display search screen that displays an access log group displayed on the client PC 101.

  As a method of using the log display search screen, the user operates the operation means of the client PC 101 and inputs a footprint number as a search key in the footprint number input field 1001. When a search button 1002 is pressed after a footprint number is entered in the footprint number input field 1001, the entered footprint number is transmitted to the log management system 110 via the screen AP server 102. The log management system 110 searches for an access log corresponding to the received footprint number.

  FIG. 7 is a flowchart showing the flow of access log search processing by the log management system 110.

  The log management system 110 determines whether or not the footprint number transmitted from the client PC 101 has been received (step S601). When the footprint number is received (step S601 / YES), the process proceeds to step S602. On the other hand, when the footprint number has not been received (step S601 / NO), the determination process of step S601 is repeatedly executed until the footprint number is received.

  In step S602, the log management system 110 selects one target access log from the access log storage table 114. First, the access log of the first record in the access log storage table is selected.

  Next, the log management system 110 determines whether or not the footprint number in the access log matches the footprint number received in step S601 (step S603). If both footprint numbers match (step S603 / YES), the log management system 110 extracts the access log and stores it in the RAM 202 (step S604), and the process proceeds to step S605. On the other hand, when the footprint numbers do not match (step S603 / NO), the log management system 110 advances the processing to step S605 without executing step S604.

  In step S605, the log management system 110 determines whether the access log is the last access log in the access log storage table 114, that is, the access log stored in the last record of the access log storage table 114. It is determined whether or not there is.

  When the access log is the last access log (step S605 / YES), the process proceeds to step S606. On the other hand, when the access log is not the last access log (step S605 / NO), the log management system 110 selects the access log stored in the next record in step S602, and performs the above-described processing from step S603. Run again.

  In step S606, the log management system 110 sorts the access log groups extracted in step S604 in order of the date and time of the time stamp, and transmits them to the client PC 101.

  In the example of FIG. 11, “Company1-SystemA-20061128-13253200-324” is specified as the footprint number that is the search key, and the access log group that matches this footprint number is displayed in the access log search result display field 1003. ing. That is, the access log group transmitted in step S606 is displayed in the access log search result display column 1003. The access log search result display column 1003 includes detailed log items in addition to the time stamp, log system ID, service name, operation name, transmission / reception category, and BODY category, which are components of the access log.

  In the detailed log item, a circle corresponding to the log system ID of the log system generating the detailed log is indicated. Whether or not the detailed log exists is determined by referring to a master table held by the log management system 110 itself. In step S606, by transmitting this determination result together with the access log group, a circle mark is displayed at the corresponding position on the screen of FIG. Further, as described above, in the master table, it is managed whether the log system in each of the servers 103 to 109 generates a detailed log. The detailed log includes information on the cause of error occurrence, information on the location of error occurrence, information on error occurrence data, and the like.

  When the user designates a location for which a detailed log is to be acquired in the detailed log item and presses the detailed log acquisition button 1004, designation information including a log system ID corresponding to the designated location is log-managed from the client PC 101. Sent to system 110. The log management system 110 acquires a detailed log from a server having a log system with a log system ID indicated in the designation information.

  The acquired detailed log is transmitted from the log management system 110 to the client PC 101 via the screen AP server 102. On the client PC 101, the detailed log is displayed in the detailed log display field 1005 of the log display search screen. As a result, more detailed log analysis is possible, and the cause of the error occurrence can be traced in detail.

  The access log search result and the detailed log display screen specify a desired footprint number by operating the operating means of the log management system 110 by the system administrator who is the user of the log management system 110, and log management It may be displayed on the screen of the system 110.

  In the above-described embodiment, when a call is received first among a plurality of processes executed in cooperation to realize a series of functions, the function is used in common among the plurality of processes and the function And a footprint number that is unique information between and other functions. Then, another process is called using the message with the footprint number added, and an access log related to the process is generated including the footprint number. Further, another process is called using the message with the footprint number added, and an access log related to the other process is generated including the footprint number. Therefore, all the access logs related to the plurality of processes include the footprint number, and by specifying the footprint number, the function can be realized without requiring a session information table or a recursive process as in the past. Therefore, it is possible to quickly collect all access logs related to a plurality of processes.

  In the embodiment described above, all access logs related to a plurality of processes for realizing a series of functions are collected. However, as another embodiment, a plurality of logs for realizing a series of functions are provided. Only log information related to some of the processes may be collected. This can be realized by collecting access logs by specifying other conditions such as a server name in addition to the footprint number.

  Also, in this embodiment, a unique footprint number is added to each function that occurs more frequently than the session, and access logs can be collected based on the unique footprint number. It is more limited, and the access log can be easily analyzed.

  Furthermore, in the present embodiment, instead of using session information that a general user cannot know as in the past, the access log indicating the history of processing is collected, so the history of a plurality of related processing is displayed. It becomes possible to grasp easily.

1 is a diagram schematically showing an overall configuration of a log information collection system according to an embodiment of the present invention. It is a block diagram which shows the function structure of an ESB server (1), a back system AP server (1), a back system AP server (2), an ESB server (2), and a back system AP server (3). It is a block diagram which shows the function structure of a gateway server (1) and a gateway server (2). It is a block diagram which shows the hardware constitutions of ESB server (1)-(3), gateway server (1)-(2), back type | system | group AP server (1)-(3), and a log management system. It is a sequence chart which shows the flow of operation | movement between each server in the log information collection system which concerns on embodiment of this invention. It is a flowchart which shows the flow of the numbering process of the footprint number by each server. It is a flowchart which shows the flow of the authentication process of the message based on a digital signature. It is a flowchart which shows the flow of the search process of the access log by a log management system. It is a figure which shows an example of a message notionally. It is a figure for demonstrating the operation | movement at the time of collecting the access log produced | generated by each server with a log management system. It is a figure which shows notionally the structure of the access log stored in an access log storage table. It is a figure which shows an example of the log display search screen which displays the access log group displayed on client PC.

Explanation of symbols

101: Client PC
102: Screen AP server 103: ESB server (1)
104: Back AP server (1)
105: Back AP server (2)
106: Gateway server (1)
107: Gateway server (2)
108: ESB server (2)
109: Back AP server (3)
110: Log management system 111: Detailed log search acquisition unit 112: Log display search unit 113: Access log collection storage unit 114: Access log storage table

Claims (14)

An accepting unit that accepts a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When the process that has received a call by the receiving unit is a process that has received a call first among the plurality of processes, the process is used in common between the plurality of processes, and between the function and another function. Additional information generating means for generating additional information that is unique information;
Including a process of adding the additional information generated by the additional information generating unit to a message used when calling the plurality of processes and calling another process using the message to which the additional information is added. Processing execution means for executing the processing;
A log information generation device, comprising: log information generation means for generating log information relating to the processing executed by the processing execution means including the additional information. An accepting unit that accepts a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When additional information that is used in common between the plurality of processes and unique information between the function and another function is added to the message used when calling the plurality of processes, A process execution unit that executes the process including a process of calling another process using the message to which the additional information is added in response to reception of the call by the reception unit;
A log information generation device, comprising: log information generation means for generating log information relating to the processing executed by the processing execution means including the additional information.   The log information generating apparatus according to claim 1, further comprising authentication information generating means for generating authentication information used for authentication processing when calling another processing in the message. If the authentication information is included in the message, further comprising authentication means for performing an authentication process based on the authentication information,
The log information generating apparatus according to claim 3, wherein the processing execution unit executes the processing when authentication is obtained by the authentication unit.   5. The log information according to claim 4, wherein the authentication unit executes an authentication process based on the authentication information when the process is called from a system different from a system to which the log information generation apparatus belongs. Generator. An error detection means for detecting the occurrence of an error;
The log according to any one of claims 1 to 5, further comprising notification means for notifying occurrence of an error together with corresponding additional information when occurrence of an error is detected by the error detection means. Information generator. It relates to the plurality of processes including additional information that is used in common among a plurality of processes executed in cooperation to realize a series of functions and is unique between the functions and other functions. Log information acquisition means for acquiring log information;
A log information management apparatus comprising log information management means for managing log information relating to the plurality of processes acquired by the log information acquisition means. Search means for searching log information corresponding to designated additional information from log information managed by the log information management means;
8. The log information management apparatus according to claim 7, further comprising output means for outputting log information searched by the search means. A log information generation method by a log information generation device,
A reception step for receiving a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When the process that accepted the call in the accepting step is the process that accepted the call first among the plurality of processes, it is used in common between the plurality of processes, and between the function and another function. An additional information generation step for generating additional information that is unique information;
Including a process of adding the additional information generated by the additional information generation step to a message used when calling the plurality of processes and calling another process using the message to which the additional information is added. A process execution step for executing the process;
A log information generation method, comprising: a log information generation step for generating log information related to the process executed in the process execution step including the additional information. A log information generation method by a log information generation device,
A reception step for receiving a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When additional information that is used in common between the plurality of processes and unique information between the function and another function is added to the message used when calling the plurality of processes, A process execution step of executing the process including a process of calling another process using the message to which the additional information is added in response to reception of the call by the reception step;
A log information generation method, comprising: a log information generation step for generating log information related to the process executed in the process execution step including the additional information. A log information management method by a log information management device,
It relates to the plurality of processes including additional information that is used in common among a plurality of processes executed in cooperation to realize a series of functions and is unique between the functions and other functions. A log information acquisition step for acquiring log information;
And a log information management step for managing log information related to the plurality of processes acquired by the log information acquisition step. A program for causing a computer to execute a log information generation method by a log information generation device,
A reception step for receiving a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When the process that accepted the call in the accepting step is the process that accepted the call first among the plurality of processes, it is used in common between the plurality of processes, and between the function and another function. An additional information generation step for generating additional information that is unique information;
Including a process of adding the additional information generated by the additional information generation step to a message used when calling the plurality of processes and calling another process using the message to which the additional information is added. A process execution step for executing the process;
A program for causing a computer to execute a log information generation step of generating log information related to the processing executed in the processing execution step including the additional information. A program for causing a computer to execute a log information generation method by a log information generation device,
A reception step for receiving a call to a corresponding process among a plurality of processes executed in cooperation to realize a series of functions;
When additional information that is used in common between the plurality of processes and unique information between the function and another function is added to the message used when calling the plurality of processes, A process execution step of executing the process including a process of calling another process using the message to which the additional information is added in response to reception of the call by the reception step;
A program for causing a computer to execute a log information generation step of generating log information related to the processing executed in the processing execution step including the additional information. A program for causing a computer to execute a log information management method by a log information management device,
It relates to the plurality of processes including additional information that is used in common among a plurality of processes executed in cooperation to realize a series of functions and is unique between the functions and other functions. A log information acquisition step for acquiring log information;
A program for causing a computer to execute a log information management step for managing log information related to the plurality of processes acquired by the log information acquisition step.

Images