JP5475602B2 - Asynchronous processing service management system - Google Patents

Description

  The present invention relates to an operation management technology in an information processing system that provides various services to a user by cooperation of functions provided by a plurality of servers, and in particular, business applications of a plurality of servers cooperate with each other by asynchronous processing. The present invention relates to an effective technology applied to an asynchronous processing service management system that performs operation management in an information processing system that provides services.

  In recent years, many businesses (services) are provided by information processing in a computer system, and many server devices are often used at that time. These server devices are mainly operated and managed in facilities such as data centers. At this time, these server devices and facilities are not owned and operated and managed by the service provider, but operation management is often outsourced to an external vendor or the like by outsourcing. In recent years, there are cases where the cloud computing environment is used and constructed.

  In such a system form, an entity in charge of operation management of an information system including a server device and a business application running on the server device and a service providing entity realized by the business application are contracted by an SLA (Service Level). An agreement is concluded, and the operation management side guarantees a certain service level to the service provider.

  Therefore, the operation management side monitors the operating status of the system to understand the current service level, determines whether or not the system complies with the SLA, and does not comply with the SLA (or seems unable to comply). In other cases, a warning is issued, and system enhancement points, configuration change points, and the like required to comply with the SLA are extracted.

  For example, Japanese Patent Application Laid-Open No. 2006-252189 (Patent Document 1) discloses an application operation that flexibly controls service levels such as function, performance, and reliability according to changes in the business environment and SLA satisfaction. The technology related to the management method is described.

  In Patent Document 1, the entire business application or a part thereof is configured by a combination of software components that are parts, and each component is stored in a component DB and loaded into the operating environment as necessary. In addition, the service by the application is executed by managing the policy by the system operation policy management unit, the operation status of the application is monitored by the runtime application operation management unit for each component, and the result is accumulated as a monitoring history. The status of the business application is diagnosed by comparing the monitoring history with the system operation policy, and the components constituting the application are controlled based on the diagnosis result.

JP 2006-252189 A

  In the current information system environment, a single service is often realized and provided to users as a whole by cooperation of business application programs running on a plurality of servers and functions realized thereby. For example, in a stock trading system via the Internet, assuming a series of services such as selling stocks you own and purchasing other stocks with the funds you obtain, sell stocks, contracts, deposits and withdrawals, A series of processes are performed in cooperation with componentized business applications that implement a plurality of independent general-purpose functions such as stock purchases, and realized as a service.

  At this time, for example, from the viewpoint of compliance with SLA and the response to inquiries regarding service levels from customers, the service level in the service is not an individual business application unit, but a whole series of processes or a part thereof. It is necessary to grasp TAT (Turn Around Time), processing time, and the like as indices. For example, in the above service example, in order to purchase the next stock, it is assumed that the customer receives an inquiry such as “when is the amount of the sold stock deposited in the account?”. It is also assumed that a guaranteed value of processing time required for such processing is defined in the SLA as a service level.

  Here, if the cooperation of each server (function) in the series of processes related to the service is performed in the synchronous process, the control of the series of processes among the plurality of servers is finally controlled by the server that started the process. Come back. Therefore, it is easy to grasp the end point of a series of synchronization processing, and it is easy to calculate TAT.

  However, when the cooperation of each server (function) is performed by asynchronous processing, after a server calls another server for cooperation, it does not know how the processing is performed after that. It is difficult to trace the flow of processing, and it is difficult to grasp the end timing of a service consisting of a series of processing and the processing time required for the whole. Therefore, it is basically impossible to guarantee the service level in a service consisting of a series of asynchronous processes, but when there is an inquiry about the service level from the customer as described above, the processing time etc. is answered with a certain degree of accuracy. There is a desire to be able to do it.

  Also, in the case of asynchronous processing, the processing path is not always a straight line unlike synchronous processing, and the processing path between multiple servers branches depending on the processing content, and processing is performed simultaneously on different servers. May also occur.

  However, the person in charge of operation management of server devices that perform these processes is fundamentally different from the developer of business applications, so it is possible to grasp details such as linkage between servers (functions) and processing paths. In some cases, it is impossible to operate in a black box. In this situation, for example, even if you can see which business application is output from which server by looking at the log output from the server, this function is called from which function of which server. It is difficult for the operation manager to grasp the processing configuration of asynchronous processing such as which function is called next.

  Note that the above-described problems are not particularly taken into consideration in the conventional technique in the operation monitoring of the system including Patent Document 1 and the like.

  Therefore, an object of the present invention is to enable tracking of the cooperation of each server or each business application in asynchronous processing in a system that provides services by asynchronous processing by business applications running on a plurality of servers, thereby processing asynchronous processing. An object is to provide an asynchronous processing service management system for visualizing the configuration. Another object of the present invention is to provide an asynchronous processing service management system for acquiring processing time information in the whole or part of a series of asynchronous processing related to a service.

  The above and other objects and novel features of the present invention will be apparent from the description of this specification and the accompanying drawings.

  Of the inventions disclosed in this application, the outline of typical ones will be briefly described as follows.

  An asynchronous processing service management system according to a representative embodiment of the present invention is an asynchronous processing service management system that manages a service provided by cooperation by asynchronous processing in each business application respectively running on a plurality of business servers. It has the following characteristics.

  That is, the asynchronous processing service management system can be connected to each business server via a network, and has a management server that grasps and manages the operating status of each business application that runs on each business server, When a business application running on the business server calls a business application on another business server by asynchronous processing, the business server is requested for each asynchronous process by a request from the business application running on the business server. An asynchronous processing transaction ID issuing unit that issues an identifiable asynchronous processing transaction ID, and a log output unit that can record log information in a log recording device in response to a request from a business application running on the business server.

  When the first business application operating on the first business server is called from the second business application operating on the second business server by asynchronous processing, the third business application is further processed by asynchronous processing. When the third business application running on the business server is called, the information related to the first asynchronous processing transaction ID issued by the first business server is issued by the second business server that is the call source. The first log output unit on the first business server outputs the information to the first log recording device in association with the second asynchronous processing transaction ID.

  The management server collects log information recorded in the log recording device of each business server and records the log information in the collection log recording device; and log information recorded in the collection log recording device. Analyzing and tracking cooperation between the business applications in a series of asynchronous processes for providing the service based on the information on the association of the asynchronous process transaction ID, and acquiring information related to the processing configuration of the asynchronous process And a configuration analysis unit.

  Further, in the asynchronous processing service management system according to the representative embodiment of the present invention, the management server further provides the business application in the whole or a part of a series of asynchronous processing for providing the service. Analyzing the log information recorded in the log collection unit, tracking the cooperation between the business applications based on the association information of the asynchronous processing transaction ID, and obtaining the processing time information It has the part.

  Among the inventions disclosed in the present application, effects obtained by typical ones will be briefly described as follows.

  According to a typical embodiment of the present invention, in a system that provides services by asynchronous processing by business applications running on a plurality of servers, it is possible to track the cooperation of each server or each business application in asynchronous processing, This makes it possible to visualize the processing configuration of asynchronous processing. In addition, it is possible to acquire information on the processing time in the entire series of asynchronous processes related to the service or a part thereof.

It is the figure which showed the outline | summary about the structural example of the asynchronous processing service management system which is one embodiment of this invention. It is the figure which showed the outline | summary about the example of the process structure of the asynchronous process in one embodiment of this invention. It is the figure which showed the outline | summary about the example of the process structure of a synchronous process. It is the figure which showed the outline | summary about the example of the process structure of an asynchronous process.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted. In the following, in order to make the features of the present invention easier to understand, the description will be made in comparison with the prior art.

<Overview>
In the case of a configuration that realizes service provision by each business application through synchronous processing, TAT for a series of processing related to the service from the viewpoint of one of the items specified in the SLA or in response to an inquiry from a customer It is easy to get.

  FIG. 3 is a diagram showing an outline of an example of the processing configuration of the synchronization processing. FIG. 3 shows an example in which four business servers 10 (business server A (10a) to business server D (10d)) perform processing related to service provision in cooperation by synchronization processing. For example, the business application (APL) A (15a) running on the business server A (10a) is executed as the first of a series of processes, and the business APL B (15b) running synchronously on the business server B (10b) therefrom Is called. Further, during the processing of the business APL B (15b), the business APLC (15c) operating on the business server C (10c) is called synchronously. Furthermore, during the processing of the business APLC (15c), the business APLD (15d) operating on the business server D (10d) is called synchronously.

  When the processing in the business APLD (15d) is completed, the control of the processing returns to the business APLC (15c) that is the calling source. Further, when the processing in the business APLC (15c) is completed, the control of the processing returns to the business APPL B (15b) that is the calling source. Similarly, when the process in the business APL B (15b) is completed, the control of the process returns to the business APL A (15a) that is the calling source. When the process in the business APL A (15a) is completed, a series of processes related to the provision of the service is completed.

  At this time, each business server 10 generally has, as a log related to processing in the business APL 15 (business APL A (15a) to business APL D (15d)), for example, a log 14 ( Records are output to log A (14a) to log D (14d)). Therefore, in the series of processes described above, a series of processing start and end logs of the business APL A (15a) recorded in the log A (14a) on the business server A (10a) is referred to, so that The processing time (TAT) of the synchronization process can be acquired. In addition, by obtaining statistical information from the log stored and recorded in the log A (14a), the SLA compliance status can be confirmed, and the expected time required for processing can be answered in response to inquiries from customers. It becomes possible to do.

  On the other hand, FIG. 4 is a diagram showing an outline of an example of a processing configuration of asynchronous processing. In FIG. 4, similar to FIG. 3 described above, the four business servers 10 cooperate to perform processing related to service provision through a series of processing from the business server A (10a) to the business server D (10d). In this example, the business APL 15 operating on each business server 10 cooperates by asynchronous processing.

  When the business APL 15 calls another business APL 15 by asynchronous processing, for example, a cooperation queue is provided in each business APL 15 (or business server B), and a processing request message is added to or inserted into this queue. Each business APL 15 extracts a message from the corresponding queue, and starts processing based on parameters or the like specified in the message. In the example of FIG. 4, the business APL A (15a) adds a processing request message to the queue 16b of the business server B (10b) (or business APL B (15b)). The business APL B (15b) retrieves a processing request message from the queue 16b as needed and starts processing. Furthermore, the business APL B (15b) adds a processing request message to the queue 16c of the business server C (10c) (or business APLC (15c)). The business APLC (15c) similarly retrieves a processing request message from the queue 16c as needed and starts processing.

  In the asynchronous process as shown in the example of FIG. 4, unlike the synchronous process, the end of the series of processes is not the business APL A (15a) that started the process, but the business APL 15 called at the end of the cooperation. For this reason, even if the log A (14a) on the business server A (10a) that started the processing is analyzed, the end timing of the series of processing cannot be grasped.

  In addition, since the processing is asynchronous, for example, the business APL B (15b) of the business server B (10b) calls the business APL C (15c) of the business server C (10c) in parallel (that is, the business server B (10b)). It is also possible to call the business APLD (15d) of the business server D (10d) regardless of whether or not the processing in the APLC (15c) is completed. For example, when the processing configuration is unknown and the log D (14d) of the business server D (10d) is referred to, it can be understood that the business APLD (15d) is called and executed. Whether this is called in parallel with calling the business APLC (15c) from the business APL B (15b) or whether it is called from the business APLC (15c) cannot be grasped (from the business APL A (15a)) (There is a possibility that it has been called, or it may have been called from the client terminal 50 for the first time).

  Therefore, it is very difficult to specify a series of processes, track and grasp the process path, and calculate the time required for the process. For example, business APL A, such as an answer to an inquiry such as “When is the amount of shares sold (by business APL A (15a)) deposited in an account (by business APL D (15d)?”) When calculating the processing time required from the processing in (15a) to the processing in the business APLD (15d), the average processing time of the business APL15 in each business server 10 is acquired from the log 14 and accumulated. The method of calculating cannot be taken.

  Therefore, in the asynchronous processing service management system according to an embodiment of the present invention, every time asynchronous processing occurs in each business server, this may be described as asynchronous processing transaction ID (hereinafter referred to as “ATxID”). ) And output this to the log 14 or journal. Based on this ATxID, it is possible to track the cooperation by associating the processing in each business server 10 (business APL 15) in a series of asynchronous processing, thereby visualizing the processing configuration of the asynchronous processing and the entire series of processing related to the service. Alternatively, it is possible to acquire processing time information in a part of the information.

<System configuration>
FIG. 1 is a diagram showing an outline of a configuration example of an asynchronous processing service management system according to an embodiment of the present invention. Asynchronous processing service management system 1 is constructed at a site that operates and manages a plurality of business servers 10 such as a data center. 30 has a configuration connected to an internal network 41 such as a LAN (Local Area Network). The business server 10 is configured to be accessible by a plurality of client terminals 50 such as PCs via a network 42 such as the Internet.

  The business server 10 is a server device that provides a service to a user via the client terminal 50 alone or in cooperation with another business server 10. For example, the base unit 11, the ATxID issuing unit 12, and the log output unit 13. , And the business application (APL) 15 software, and a log 14 composed of a database, a file, and the like.

  The base unit 11 includes various middleware such as an OS (Operating System), a Web server program, and a database management program, and provides the base function of the business server 10. The ATxID issuing unit 12 is called from a business APL 15 described later, and issues an ATxID assigned to the business APL 15 when the business APL 15 calls another business APL 15 by asynchronous processing. The ATxID format is not particularly limited, but at least it is possible to identify which business APL 15 (or business server 10) has issued the request, and the same business by the sequence number or the like. It is necessary to be able to identify each issued by a request from the APL 15.

  The log output unit 13 is called from the business APL 15, receives a log output request accompanying processing in the business APL 15, and outputs this to the log 14. The log output unit 13 may be incorporated and implemented in the business APL 15. The business APL 15 executes processing related to provision of a service to the user in cooperation with, for example, the business APL 15 of another business server 10. For cooperation with other business servers 10, either synchronous processing or asynchronous processing may be used. Note that the business APL 10 does not necessarily have to be directly accessible to the function from the client terminal 50, and may have a function that is called and used only from another business APL 10.

  As described above, the business APL 15 receives and acquires an ATxID issued by the ATxID issuing unit 12 when calling another business APL15 by asynchronous processing. The acquired ATxID information is output to the log 14 via the log output unit 13. To this extent, in order to make each business APL 15 a management target in the asynchronous processing service management system 1 of the present embodiment, it is necessary to implement such a function by modification or from the beginning of initial development.

  On the other hand, the management server 20 is a server device that grasps and manages the operating status of each business APL 15 by collecting, analyzing, and totaling the logs 14 of each business server 10, and includes, for example, a base unit 21, a log collection unit 22, a processing time calculation unit 24, a configuration analysis unit 25, and software of the display unit 26, and a collection log 23 including a database, a file, and the like. The management server 20 tracks the cooperation between the business APLs 15 in the asynchronous processing service provided by each business APL 15, grasps and visualizes the processing configuration, and in the entire series of processes related to the service or a part thereof. Acquires processing time information (service level).

  Similarly to the base unit 11 of the business server 10, the base unit 21 includes various middleware such as an OS, a Web server program, and a database management program, and provides the base function of the management server 20. The log collection unit 22 collects log data from the log 14 of each business server 10 and stores it in the collection log 23. The collection timing and method can be appropriately set according to the requirements. For example, the log collection unit 22 periodically extracts and collects corresponding log data from the log 14 of each business server 10 via the log output unit 13, or conversely, the log output unit 13 of each business server 10. May be configured to transmit logs to the log collection unit 22 of the management server 20 almost in real time.

  The processing time calculation unit 24 analyzes the log data stored in the collection log 23, and in accordance with an instruction from an operation person or the like via the operation terminal 30, the entire series of processes related to the specified service or a part thereof It is possible to acquire information on the processing time in Here, processing time information for a single business process (transaction) can be acquired, and statistical information can be calculated by aggregating each processing time information for business processes executed multiple times. You may make it usable for the confirmation of the SLA compliance status as a whole.

  The configuration analysis unit 25 analyzes the log data stored in the collection log 23, tracks the cooperation between the business APLs 15 in a series of asynchronous processing for providing services, and acquires the processing configuration of the asynchronous processing. For example, for a series of asynchronous processes related to an arbitrary service, information on the correspondence between the calling source and the calling destination of each business APL 15 and the order thereof is acquired. With this information, the person in charge of operation, for example, even when the operation configuration of asynchronous processing is received from the person in charge of development in a state where the processing configuration of the asynchronous processing is made into a black box, Information related to the processing configuration can be grasped, that is, logically visualized.

  Furthermore, the display unit 26 visualizes and displays this on the graphical interface of the operation terminal 30 based on the processing configuration information acquired by the configuration analysis unit 25. Thereby, the processing configuration of asynchronous processing can be physically visualized. In the display unit 26, for example, any entity (in this embodiment, business APL15 or business server 10) related (in this embodiment, calling the business APL15) is linked with a line segment, an arrow, or the like. Thus, it is possible to use an existing technique for displaying the data for display on a Web browser or the like on the operation terminal 30.

<Method of grasping the processing configuration of asynchronous processing>
FIG. 2 is a diagram showing an overview of an example of a processing configuration of asynchronous processing in the present embodiment. In the present embodiment, as described above, when the business APL 15 calls another business APL 15 as an asynchronous process, the ATxID issuance unit 12 issues an ATxID and outputs it to the log 14. For example, in the business server A (10a) in the figure, when the business APL A (15a) calls the business APL B (15b) of the business server B (10b) as an asynchronous process, the ATxID issuing unit 12 sets ATxID = "A001". "Is issued, and the transaction APL B (15b) is called by adding a processing request message with this information added to the queue 16b.

  At this time, the business APL A (15a) records in the log A (14a) that the asynchronous process has been called (started) with this ATxID = "A001". In the present embodiment, for example, the ATxID adds a sequence number (“001”, “002”,...) To a character string (“A”, “B”,...) That can identify each business APL 15. The format is used.

  In the business server B (10b), the business APL B (15b) retrieves a processing request message from the queue 16b as needed and starts processing. In this process, since the business APL B (15b) calls the business APL C (15c) of the business server C (10c) as an asynchronous process, the business request message is sent to the business server C (10c) (or business APL C). (15c)) is added to the queue 16c. At this time, ATxID = “B001” is issued by the ATxID issuing unit 12 of the business server B (10b), and the fact that asynchronous processing is called (started) by this ATxID is recorded in the log B (14b).

  Furthermore, in order to call the business APLD (15d) of the business server D (10d) as an asynchronous process, a message for an asynchronous processing request is also sent to the queue 16d of the business server D (10d) (or the business APL D (15d)). to add. At this time, ATxID = "B002" is issued by the ATxID issuing unit 12 of the business server B (10b), and the fact that asynchronous processing is called (started) by this ATxID is recorded in the log B (14b).

  Note that when the fact that the asynchronous process is called is recorded in the log B (14b), the ATxID (the business server B (10b in FIG. 2) of the process that has called the caller so that the relation of cooperation with the caller can be grasped. In the example of (), the information of the caller ATxID = “A001”) is added and associated. By referring to the ATxID information of the process that is the caller, it is possible to trace the cooperation of the processes between the business APLs 15 in the target business process.

  Thereafter, when the business APL B (15b) terminates the asynchronous processing called from the business APL A (15a), the fact is recorded in the log 14b. At that time, the information of ATxID = “A001” of the process is also recorded. The above processing is the same for the business APLC (15c) and the business APL D (15d) called by the asynchronous processing.

  Here, for example, in response to an inquiry about a service level, such as “When is the amount of stock sold (by business APL A (15a)) deposited in an account (by business APLD (15d)?”) To obtain the processing time (statistical information) from the start of the processing in the business APL A (15a) until the end of the processing in the business APL D (15d) called by cooperation by asynchronous processing There is a need to.

  Various methods for calculating the processing time can be considered. For example, the processing time calculation unit 24 of the management server 20 refers to the collection log 23, and firstly, at the end of the asynchronous processing cooperation related to the target service. The start / end log corresponding to the process (business APLD (15d) in this example) is acquired and the processing time is calculated. In addition, the end log of the asynchronous process output in the process is retrieved from the collection log 23 and acquired. In the example of FIG. 2, an end log of ATxID = “B002” output to the log 14d of the business server D (10d) can be acquired.

  Next, the target process is traced and the start log of ATxID = “B002” is retrieved from the collection log 23 and acquired. In the example of FIG. 2, the start log of ATxID = “B002” output to the log 14b of the business server B (10b) can be acquired. Here, the processing time of the business process corresponding to the start log (the process in the business APL B (15b)) is calculated based on the start / end log of the business process.

  In the example of FIG. 2, information indicating that the caller is a process of ATxID = “A001” is added to the start log. Therefore, it is understood that the business process is further called by an asynchronous process from the caller process (ATxID = “A001”).

  In this embodiment, the information of the caller's ATxID is associated with the start log by adding the information, but the transaction process corresponding to the start log is further called from another business APL 15 by asynchronous processing. In this case, in the series of logs of the transaction process, an end log of the asynchronous process of the caller (in the example of FIG. 2, the end log of ATxID = “A001” in the log 14b) should be output. . Therefore, it is possible to determine whether or not the transaction process is called as an asynchronous process by searching for the presence / absence thereof (that is, included in a series of logs of the transaction process). , Implied by that).

  Next, going back further about the target process, the start log of ATxID = “A001” is retrieved from the collection log 23 and acquired. In the example of FIG. 2, the start log of ATxID = “A001” output to the log 14a of the business server A (10a) can be acquired. Here, the processing time of the business process corresponding to the start log (the process in the business APLA (15a)) is calculated based on the start / end log of the business process. Here, since the business APL A (15a) is the first process in a series of asynchronous processes for which the processing time is to be obtained, the tracking of cooperation ends here.

  At this time, each processing server 10 in the cooperation in a series of asynchronous processing is obtained by adding the processing times in the business APL D (15d), the business APL B (15b), and the business APL A (15a) calculated above. Total processing time can be obtained.

  In the processing time calculation method as described above, the total time actually processed in the business server 10 can be obtained. However, in a system environment where the processing load is high, the processing in each business server 10 is performed. It may take a long time, and there may be a case where a processing request message stays in each queue 16. At this time, the processing time calculation method as described above does not include the time during which the processing request message stays in the queue 16. Therefore, in the above example, a log of the end of the last business process (process in the business APLD (15d)) in the cooperation of a series of asynchronous processes is obtained, the cooperation of the asynchronous processes is traced, and the first business process is traced. It is possible to obtain a log of the start of processing (processing in the business APL A (15a)) and calculate the total processing time based on the difference between the time stamps of these logs.

  For example, by obtaining the difference between the total processing time and the total processing time in each business server 10 (business APL 15), it is possible to grasp the time during which the processing request remains in the queue 16. It is also possible to grasp the residence time in each queue 16 for each asynchronous process by analyzing the difference in the log time stamp in each business process. Thus, it is possible to analyze the presence or absence of a bottleneck in a series of asynchronous processes, the location thereof, and the like.

  The configuration analysis unit 25 of the management server 20 tracks, for example, a series of asynchronous processing linkages from the collection log 23 without limiting the target range for various business processes (services) by the same procedure as described above. By recording the relationship, information relating to the processing configuration of asynchronous processing for each service can be obtained. Further, based on the information obtained by the configuration analysis unit 25, the display unit 26 displays, for example, each business APL 15 (or the business server 10) and the cooperation relationship for each service in the form of a flow diagram. Visualize by such as.

  As described above, according to the asynchronous processing service management system 1 which is an embodiment of the present invention, an ATxID is issued for each asynchronous processing that occurs in each business server 10 (business APL 15). This is output to the log 14 or journal. When further asynchronous processing occurs in the called business server 10 (business APL 15), the newly issued ATxID is associated with the ATxID information issued by the calling business server 10 (business APL 15) in the log 14 Output to.

  By collecting, analyzing and aggregating these log information in the management server 20, it is possible to track the cooperation of each business server 10 (business APL 15) in a series of asynchronous processing, thereby visualizing the processing configuration of asynchronous processing. At the same time, it is possible to acquire information on the processing time in the entire series of processes or a part of the processes.

  This makes it possible for the operation staff to grasp the SLA compliance status to some extent from an application perspective. In addition to the processing time in each business APL 15, information on the residence time in the queue during asynchronous processing Based on the above, it is also possible to grasp performance and capacity tuning points (bottleneck).

  In addition, when each of the existing business APLs 15 calls another business APL 15 by asynchronous processing, the ATxID issuing unit 12 is requested to obtain an ATxID and is acquired, and a log including this is output to the log 14. It can be easily managed by the asynchronous processing service management system 1, and the impact on the existing processing of each business APL 15 and the workload of developers and operators can be minimized. Is possible.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiment. However, the present invention is not limited to the embodiment, and various modifications can be made without departing from the scope of the invention. Needless to say.

  The present invention can be used in an asynchronous processing service management system that performs operation management in an information processing system in which business applications of a plurality of servers cooperate in asynchronous processing to provide services as a whole.

1 ... Asynchronous processing service management system,
10 (10a to d) ... business servers (A to D), 11 ... base part, 12 ... asynchronous processing transaction ID (ATxID) issuing part, 13 ... log output part, 14 (14a to d) ... log (A to D) ), 15 (15a to d) ... business application (APL) (A to D), 16 (16a to d) ... queue,
DESCRIPTION OF SYMBOLS 20 ... Management server, 21 ... Base part, 22 ... Log collection part, 23 ... Collection log, 24 ... Processing time calculation part, 25 ... Configuration analysis part, 26 ... Display part,
30: Operation terminal,
41 ... Internal network, 42 ... Network,
50: Client terminal.

Claims (4)

Asynchronous processing service management system that manages services provided by cooperation by asynchronous processing in each business application running on multiple business servers,
A management server that is connectable to each business server via a network, and that grasps and manages the operational status of each business application running on each business server;
The business server is
When a business application running on the business server calls a business application on another business server by asynchronous processing, an asynchronous process can be identified for each asynchronous process by a request from the business application running on the business server An asynchronous process transaction ID issuing unit for issuing a transaction ID;
A log output unit capable of recording log information in a log recording device in response to a request from a business application running on the business server;
When the first business application operating on the first business server is called from the second business application operating on the second business server by asynchronous processing, the third business application is further processed by asynchronous processing. When the third business application running on the business server is called, the information related to the first asynchronous processing transaction ID issued by the first business server is issued by the second business server that is the call source. In association with the second asynchronous processing transaction ID, the first log output unit on the first business server outputs to the first log recording device,
The management server
A log collection unit that collects log information recorded in the log recording device of each business server and records it in the collection log recording device;
The log information recorded in the collected log recording device is analyzed, and the linkage between the business applications in a series of asynchronous processing for providing the service is traced based on the information on association of the asynchronous processing transaction ID And an asynchronous processing service management system comprising: a configuration analysis unit that acquires information related to a processing configuration of asynchronous processing. In the asynchronous processing service management system according to claim 1,
The management server further analyzes the log information recorded in the log collection unit for each business application in the whole or a part of a series of asynchronous processes for providing the service, and performs the asynchronous processing transaction. An asynchronous processing service management system comprising: a processing time calculation unit that tracks cooperation between the business applications based on ID association information and obtains processing time information. In the asynchronous processing service management system according to claim 1 or 2,
The management server further includes a display unit for visualizing and displaying the information on an operation terminal based on information related to a processing configuration of a series of asynchronous processes for providing the service acquired by the configuration analysis unit. An asynchronous processing service management system comprising: In the asynchronous processing service management system according to claim 2,
The processing time calculation unit of the management server includes a time stamp difference in the log information recorded in the log collection unit for each business application in the whole or a part of a series of asynchronous processes for providing the service. The asynchronous processing service management system is characterized in that a residence time in a queue used for a call between the business applications is obtained by analyzing