JP2007133545A - Operation management program and operation management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an operation management program and an operation management method, capable of performing information transmission of operation with a cooperation system regardless of complication of the whole system even if the whole system is complicated. <P>SOLUTION: Event setting information is analyzed by a prepared event definition file, event notification information is notified to a cooperating server by analysis results, a measure completion notification related to an event from the cooperating server is obtained, and the event is executed. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to operation management of a system, and more specifically, notifies an event to a linked server related to an event based on event setting information input by a system administrator, and completes a measure accompanying event execution from the linked server The present invention relates to an operation management program and an operation management method for receiving event notification and executing event processing.

  The spread of personal computers and networks is remarkable, and users can receive many services in various places. In these systems, a plurality of systems cooperate with each other to provide services, and in each system, it is generally assumed that one or more servers share a role (multi-server). It has become. In response to user requests for service expansion, the system is increasing and distributed, and the system is becoming more complex as a whole.

  The person in charge of the department that manages the operation of the system (hereinafter referred to as the administrator) is required to take responsibility for the maintenance and failure of the system that it manages (hereinafter referred to as the own system). . For example, when it is necessary to apply a patch for an application in the local system immediately, it is necessary to stop the system. Announcement of the system stop to the user of the local system and other systems linked to the local system It is necessary to notify the administrator of the linked system). Then, work such as stopping related JOBs in the cooperative system or making announcements to users of the cooperative system is performed, and the work of the own system is performed upon receiving notification from the administrator of the cooperative system that the work has been completed. Is possible. When the operation of the own system is completed and the system is started up, the system restart transmission (communication to the user of the own system and the cooperation system) and the correspondence on the cooperation system side are required in the same flow.

  On the other hand, when work is performed on maintenance or failure in the cooperative system, if a notification is received from the administrator of the cooperative system, it is necessary to perform the above-described work on the cooperative system in the own system. Generally, telephones and electronic mails are used as these notification means.

In a system composed of a plurality of servers, there has been proposed a management apparatus that centrally manages events occurring in each server and automatically notifies the user. This is because a common storage means is provided in one of the servers, an event occurring in each server is detected, transmitted to the common storage means and stored, and this information is notified to the user. The purpose is to reduce the burden (for example, Patent Document 1).
Japanese Patent Laid-Open No. 10-247911

  As described above, it has become common that a system that provides a service cooperates with a plurality of systems, and each system includes one or more servers. Then, the system administrator needs to work with the administrator of the linked system in the event of maintenance or failure, and requires a great deal of man-hours as the system becomes more complex.

  Patent Document 1 proposed to deal with such a problem reduces the burden on the system administrator because notification to the user can be automated. However, it is necessary to keep track of the entire system for centralized management, and no consideration is given to system variations. For example, when the number of servers to be linked is increased, it is necessary to set each time, which is complicated. In particular, it can be difficult to grasp the whole system as the whole system becomes huge.

  SUMMARY OF THE INVENTION An object of the present invention is to provide an operation management program and an operation management method capable of transmitting operation information with a linked system regardless of the complexity of the entire system.

The operation management program and operation management method of the present invention are configured as follows.
(1) First invention In the first invention, an event server that needs to deal with an event such as maintenance or failure notifies the server linked to the server that there is an event, This is an operation management program that executes event processing after confirming the completion of measures associated with event implementation on the server side. Further, when a notification of an event executed on the server side is received from a linked server, a measure associated with the event execution is performed, and a completion notification is returned to the server.

  The principle will be described with reference to FIG. The first invention is an operation management program for a server (referred to as an event server) connected to one or more servers via a network. As shown in FIG. 1, the event information analysis procedure 10, the event notification procedure 20, and the action completion The notification reception order 30 and the event execution procedure 40 are used.

  The event information analysis procedure 10 analyzes event setting information describing event contents based on an event definition file prepared in advance. The event setting information includes, for example, an event ID, an event processing time, an event execution reason, and the like. In the event definition file, for example, the target service contents, processing contents, and linked server names are described for each event ID.

  The event notification procedure 20 creates event notification information for the cooperation server based on the analysis result of the event information analysis procedure 10, and notifies the information.

  The measure completion notification reception order 30 receives from the cooperation server a measure completion notification indicating that a measure to be dealt with on the cooperation server side is completed in accordance with the notified event. For example, when the event that notified the event notification information is a content that pauses an application that collects data, the linkage server that is sending data in cooperation with that application takes measures to pause the sending of data. It is necessary to take measures, and after the measure is taken, a notification of the measure completion is notified and the event server receives it.

The event execution procedure 40 executes event processing when it receives action completion notifications from all the linked servers that have notified the event information notification. In other words, the event server executes event processing after confirming that any of the cooperation servers has completed the measures associated with the event.
(2) Second invention In the second invention, when event notification information is received from a connected server, a measure is taken according to the event and a measure completion notification is returned.

  FIG. 2 shows the principle, and includes an event information analysis procedure 10, an event notification procedure 20, a measure completion notification reception order 30, an event execution procedure 40, and a linked event measure procedure 50.

  Since the event information analysis procedure 10 to the event execution procedure 40 are the same as those in the first invention and redundant descriptions are omitted here.

When the event notification information is received from one connected server, the linked event measure procedure 50 transfers the event notification information to a linked server related to the event of the event notification information on a server different from that server. Then, after taking measures associated with the event, the server receives a notification that the measures associated with the event on the cooperation server side have been completed from the cooperation server, and returns a measure completion notice to the server (the server that sent the event notification information). . That is, when the event notification information is received from the server A, if the servers B and C are linked servers related to the event, the event notification information is transferred to the servers B and C. In response to the notification that the measure on the C side has been completed, the measure completion notification is transmitted (returned) to the server A.
(3) Third invention In the third invention, in addition to the configuration of the first invention or the second invention, a restart notification of the event server is performed. FIG. 3 shows a configuration obtained by adding a restart notification configuration to the second invention, and includes an event information analysis procedure 10, an event notification procedure 20, an action completion notification reception procedure 30, an event execution procedure 40, a linked event action procedure 50, and The system restart notification procedure 60 is used.

  Since the event information analysis procedure 10 to the cooperative event measure procedure 50 have the same contents as those of the second invention, description thereof will be omitted.

The system restart notification procedure 60 restarts the system of the event after executing the event in the event execution procedure, and notifies the cooperation server, the administrator of the cooperation server, and the user of the event server of the system restart.
(4) 4th invention 4th invention is the event notification procedure of 1st invention-4th invention, while notifying event notification information to a cooperation server, the administrator of a system of a cooperation server, and own event This notifies the server user of the contents of the event notification information.
(5) Fifth Invention The fifth invention is the operation management method of the first invention.

  According to the first invention, when event setting information for maintenance or failure is created, a notification is made to the linked server related to the event, and an event is executed on the event server by checking an answer from the linked server. It is possible to provide an operation management program that reduces the man-hours required to contact and confirm the administrator. Further, the operation management program can cope with event processing depending on the contents of the event even when the administrator of the cooperation server is absent.

  According to the second invention, if each connected server implements the operation program of the second invention, and the event server notifies only the linked server that is directly linked, all of the servers related to the event Since the notification is sent to and a measure for that is taken, it is only necessary to be aware of only the directly linked servers, so that the burden on the administrator is reduced. That is, even if a server related to an event is added at the end of the cooperation server, there is no need to be aware of it.

  According to the second invention, since the notification of the event is automatically notified to the administrator of the related cooperative server and the user of the own event server, the operation management program for reducing the man-hour required for the contact of the administrator is provided. Can do.

  According to the third invention, the notification of system restart after event execution is automatically notified to the associated server, its administrator, and the user of the event server, thereby reducing the man-hours required for contact of the administrator. Management program can be provided.

  According to the fourth aspect of the invention, notification to related parties (cooperation server administrator, event server user) is automatically performed at the time of event execution. Therefore, an operation management program for reducing the man-hours of the event server administrator is provided. Can do.

  According to the fifth invention, it is possible to provide an operation management method capable of reducing the man-hours required for contact and confirmation of the manager as in the first invention.

  An embodiment of the present invention will be described with reference to FIGS.

  First, the relationship between the event server and the cooperation server will be described with reference to FIG. In FIG. 4, it is assumed that the systems A to E are connected as shown in the figure. The systems A, B, D, and E are composed of one system and one server, and the system C is composed of one system and two servers. Server A of system A is connected to servers B, C1, and D (connections are indicated by thick lines in FIG. 4), and when server A needs to perform an event, server A is designated as an event server. In other words, if the event is to be processed in relation to the server B and the server C1, the server B and the server C1 are referred to as a linkage server (the server indicated by a halftone dot in FIG. 4 is a linkage server). . Although the server D is connected to the server A, the server D does not perform processing in relation to the event at this time, so it is not called a linkage server. Even if this event is further related to the server E via the server B, it is not said to be a linked server. Each server has a flat relationship, and server B may be an event server and server A may be a linked server. It is assumed that an operation management program is installed in each server.

  FIG. 5 shows a configuration example of the event server 100. The CPU 110 controls programs, data, and input / output devices, the communication control unit 120 controls communication with a server connected via the network 121, and the keyboard 131. And an input / output control unit 130 that controls the display 132, an event definition information storage unit 140 that describes event definitions, a history information storage unit 150 that stores various types of history information associated with event execution, and an operation management program 160.

  The operation management program 160 includes an event setting unit 161, an event setting information analysis unit 162, an event notification unit 163, a measure completion notification reception unit 164, an event execution unit 165, and a linked event measure unit 166. An overview of these individual programs is described next.

  The event setting unit 161 has an editor function for creating event setting information, supports the system administrator, and stores the created information in a predetermined storage area. The event setting information is created by, for example, XML (eXtensible Markup Language).

  The event setting information analysis unit 162 analyzes the event setting information created by the event setting unit 161 with reference to the event definition information storage unit 140. Acquire the linked server to be notified by analysis and the email address of the administrator.

  The event notification unit 163 creates event notification information and notifies the acquired linked server, its manager, and the user of the server itself. For the cooperation server, it communicates with the operation management program installed in the cooperation server, and automatically sends an e-mail to the administrator or user. Then, a notification table (not shown) in which the notified linked server name is set is created.

  The measure completion notification receiving unit 164 receives a measure completion notification of measures associated with an event on the linked server side from the notified linked server. The cooperation server is one or more servers, and receives the action completion notification transmitted by the servers. When the measure completion notification is received, a completion flag indicating that the measure is completed is set in the corresponding linked server name in the notification table.

  When the completion flag is set for all linked server names in the notification table, the event execution unit 165 notifies the administrator of the own server of the completion of preparation for event execution. Then, the event is executed at the set time.

  The cooperation event measure unit 166 receives event notification information from the cooperating server, and analyzes the event notification information with reference to the event definition information storage unit 140. Based on the analysis result, the measures associated with the event are executed. When there is a server that further cooperates with the event, the received event notification information is transferred to the server. Upon completion of the execution of the measure accompanying the event of the own server and reception of the measure completion notification from the transferred linked server, the measure completion notification is returned to the server that transmitted the event notification information.

  Next, an example of event setting information created by the event setting unit 161 will be described. FIG. 6 shows an example of event setting information generated by the server A of FIG. This event setting information is created by XML and includes a tag and information for the tag. The server identifies the information based on this tag, and acquires event definition information described later. First, <event> is a tag indicating event setting information, and information written between <event> and </ event> is setting information for an event. <event-id> is information for identifying the event, <event type> is a classification of the event, and <status> is a tag indicating what state is to be obtained by event execution. Furthermore, <execution time> is a tag representing an administrator's comment, such as the time when the event is performed, and <comment> is the reason for event execution. The information in Fig. 6 shows that the event with the identification number 0001 is classified as maintenance and cannot be used during the event. The event is scheduled to be held from 0:00 to 5:00 on September 1, 2005. However, a specific event indicates that a database patch is applied.

  Next, event notification information created to notify the cooperation server will be described with reference to FIG. The example of FIG. 7 is event notification information notified from the server A to the linked servers B and C1, and is created based on the event setting information of FIG. 6 and event definition information described later. Compared to FIG. 6, tags of <event server> and <person in charge> are added, and <event server> is a server name on which an event is performed, in this case, server A. <person in charge> is the name and e-mail address of the administrator of server A where the event is executed. The cooperation server can know that the event is performed on the server A and if it is necessary to contact, it is only necessary to contact the person in charge, Fuji Taro.

  Next, a data example of the event definition information storage unit 140 will be described with reference to FIG. The event definition information is composed of the following fields. An “event ID” that stores an ID for identifying an event described in the event setting information, a “target service” that stores a service that is a target of the event, a “date limit” that indicates the limitation and contents of the operation time, "Day of the week restriction" and "Time zone", "User" that stores the file name that stores the user name and email address, "Linked server" that stores the server name related to the event target service, “Cooperation server target service” for storing the target service, “administrator notification destination” for storing the mail address of the administrator of the cooperation server, and “processing” for storing the execution contents of the event. In this example, for the event with the event ID “0001”, the target service is a database service, the operation time zone is from 0 o'clock to 23:59, and there are no restrictions on the date and day of the week. The name and e-mail address of the user who receives this database service are in a file named USER-A, and the cooperation server is server B and server C1, and the services targeted by the server are data acquisition and data provision, respectively. The notification destinations of each administrator are jiro@jp.aa.com and hana@jp.bb.com. The processing contents of the event are as shown in FIG. 8, and the program name, version, storage address, etc. to be processed are designated. The event is executed based on this processing content.

  Next, the processing flow of the event server will be described using FIG. 9 and FIG.

  FIG. 9 shows a flow in which the event server transmits event notification information to the linkage server, and confirms the completion of the action on the linkage server from the linkage server and executes the event. First, event setting information created by the event server administrator is read. Then, the event definition information storage unit 140 is referenced based on the event ID described in the event setting information, and the corresponding event definition information is extracted (S100, S110).

  The extracted event definition information is checked, and if there is a linked server related to the set event, it is determined that notification is necessary, and event notification information is created and transmitted to the linked server. The event notification information is notified to all linkage servers set in the event definition information. After notification, create a notification table. The notification table is a table indicating that notification of event notification information from the event server to the linkage server has been received, and that the linkage server has received notification of the completion of the action associated with the event. Any flag can be set. If notification to the coordination server is not required (when the coordination server is not set in the event definition information), the processing proceeds to the next step without performing these processes (notification of event notification information and creation of the notification table) ( S120-S140).

  Next, it is checked whether notification to the user is necessary. If the user notification destination file name is stored in the user notification destination field of the event definition information, it is determined that it is necessary, and the content of the event setting information is sent to the user's email address described in that file. Send with. If notification to the user is unnecessary, the process proceeds to the next step (S150, S160).

  Here, the event server waits for a measure completion notification from the cooperation server that transmitted the event notification information first. When the measure completion notification transmitted from the cooperation server is received, a completion flag is set in the name of the cooperation server that has transmitted the measure completion notification in the notification table. The notification is waited until a measure completion notification is received from all the linked servers (S170-S190).

  When the action completion notification is received from all the linked servers (which can be determined by referring to the completion flag in the notification table), the action associated with the event of the linked server is completed for the event server administrator, and the event execution preparation is completed. Notification of completion. The event server may automatically send an e-mail to the administrator.

  When the set time comes, event processing is executed based on the content set in the event definition information processing. This process may be processed automatically by the event server, or may require some input from the administrator. In the latter case, for example, the event server performs processing up to the necessary input stage and waits in a state waiting for input. When the event processing is completed and the target service is restarted, the event server transmits a restart notification to the cooperation server. In addition, the restart of the cooperation server administrator and the event server user is also notified (S200-S220).

  Next, the processing flow of the cooperation service when the cooperation server receives event notification information from the event server will be described with reference to FIG.

  First, event notification information is received from a connected event server. Then, the event definition information storage unit 140 is referenced based on the event ID described in the event notification information, and the corresponding event definition information is extracted (S300, S310).

  Check the linked server of the extracted event definition information, and notification is necessary if the linked server has a linked server other than the event server (in order to distinguish it from the linked server of this processing flow, here it is called the second linked server) The event notification information is transferred to the second linkage server. After notification, create a notification table. The notification table only needs to be able to set the second linked server name and the completion flag. When notification to the second linkage server is not required (when the linkage server is not set in the event definition information), the process proceeds to the next step (S320-S340).

  Next, it is checked whether notification to the user is necessary. If the user notification destination file name is stored in the user notification destination field of the event definition information, it is determined that it is necessary, and the content of the event notification information is sent to the user's email address described in that file. Send with. If notification to the user is not required, proceed to the next step. The user here is a user of a service related to the event in the cooperation server (S350, S360).

  The cooperation server automatically transmits the contents of the event notification information to the administrator of the cooperation server by e-mail. Subsequently, a measure associated with the event is executed. For example, the service program targeted by the event is stopped (S370, S380).

  Here, the linkage server waits for a measure completion notification from the second linkage server that has previously transferred the event notification information. When the measure completion notification transmitted from the second linkage server is received, a completion flag is set in the name of the second linkage server that transmitted the measure completion notification in the notification table. It waits for notification until it receives notification of completion of measures from all the second linked services that have notified (S390-S410).

  When the action completion notification is received from all the second linkage servers (determined by referring to the completion flag in the notification table), the action completion notice is transmitted to the event server (S420).

  Subsequently, the cooperation server waits for a restart notification from the event server, and upon receiving the notification, for example, launches a program of the service that has been stopped due to the event measure, and sends an email of the restart notification to the user (S430, S440).

  In the flow described with reference to FIGS. 9 and 10, the server becomes an event server or a linkage server from the standpoint at that time, so both programs are implemented on each server.

  FIG. 11 shows an example of event notification information and action completion notification notified by the event server and the cooperation server in the flow described in FIG. FIG. 11 shows an example in which the event server and the linkage server in FIG. 5 are notified. Event notification information is notified from the server A, which is an event server, to the cooperation servers B and C1, and an action completion notification is sent from the cooperation servers B and C1 to the event server. Although not shown, event notification and resumption notification are also sent by e-mail to the administrator of each system. In addition, notification of service stop or restart is also sent by e-mail to users of respective systems not shown.

  Although not described in the flow of FIGS. 9 and 10, the operation management program stores the history of event setting information, event notification information, measure completion notification, executed event, etc. in the history storage unit 150 at an appropriate timing. Yes. This history information is used, for example, as problem analysis information or work history information when a problem occurs on the day after the event is executed.

In addition to the above examples, the following additional notes are disclosed.
(Appendix 1)
An event server operation management program in which one or more servers are connected via a network,
In the event server,
An event analysis procedure for analyzing event setting information in which event details executed by the event server are described based on an event definition file prepared in advance;
Based on the result of the analysis, an event notification procedure for creating and notifying event notification information in a linked server related to the event among the one or more servers;
A measure completion notification receiving procedure for receiving a measure completion notification indicating that a measure to be dealt with on the linked server side in accordance with the event is completed from the linked server;
An event execution procedure for executing processing of the event when the action completion notification is received from all the linked servers that have notified the event information notification;
Operation management program to execute
(Appendix 2)
When the operation management program further receives event notification information from the one or more servers, the operation management program transfers the event notification information to a linked server related to the event of the event notification information on a server different from the server, Receiving a notification that the measure associated with the event at the cooperation server has been completed after taking the measure associated with the event, and returning a measure completion notification to the server;
The operation management program according to supplementary note 1, characterized in that:
(Appendix 3)
The operation management program further restarts the system of the event after executing the event in the event execution procedure, and notifies the cooperation server, the administrator of the cooperation server, and the user of the system restart notification procedure. When,
The operation management program according to supplementary note 1 or supplementary note 2, characterized by comprising:
(Appendix 4)
The event notification procedure includes:
Based on the result of the analysis, event notification information is created and notified to the cooperation server related to the event in the one or more servers, and the administrator of the cooperation server and the user of the event server To notify the contents of the event notification information to
The operation management program according to appendix 1 to appendix 3, wherein
(Appendix 5)
An event server operation management method in which one or more servers are connected via a network,
The event server is
An event analysis procedure for analyzing event setting information in which event details executed by the event server are described based on an event definition file prepared in advance;
Based on the result of the analysis, an event notification procedure for creating and notifying event notification information to a cooperative server related to the event among the one or more servers;
A measure completion notification receiving procedure for receiving a measure completion notification indicating that a measure to be dealt with on the linked server side in accordance with the event is completed from the linked server;
An event execution procedure for executing processing of the event when the action completion notification is received from all the linked servers notified of the event information notification;
When event notification information of an event executed on the server side is received from the one or more servers, the event notification information is transferred to a cooperation server related to the event by a server different from the server, and the event A coordinated event action procedure for notifying the server that sent the event notification information after taking the action associated with the action completion notice;
An operation management method characterized by comprising:
(Appendix 6)
An event server operation management apparatus in which one or more servers are connected via a network,
Event analysis means for analyzing event setting information in which event details executed by the event server are described based on an event definition file prepared in advance;
Based on the result of the analysis, event notification means for creating and notifying event notification information to a linked server related to the event among the one or more servers;
A measure completion notification receiving means for receiving a measure completion notification indicating that a measure to be dealt with on the linked server side is completed in association with the event;
Event execution means for executing processing of the event when the action completion notification is received from all the linked servers notified of the event information notification;
When event notification information of an event executed on the server side is received from the one or more servers, the event notification information is transferred to a cooperation server related to the event by a server different from the server, and the event A coordinated event measure means for notifying the server that has sent the event notification information after taking measures associated with the action completion notification;
An operation management apparatus comprising:

(Appendix 7)
In the event execution procedure, when the action completion notification is received from all the linked servers to which the event information notification has been notified, the event server administrator notifies the event server administrator that the event can be executed. In addition, the operation management program according to any one of supplementary notes 1 to 4, wherein the event processing is executed.

(Appendix 8)
The server operation management program further includes:
A history storage procedure for storing the event setting information, the event notification information, the measure completion notification and a history of executed events;
The operation management program according to appendix 1 to appendix 4, characterized by comprising:

It is a principle diagram of the first invention. It is a principle diagram of the second invention. It is a principle diagram of the third invention. It is an example of an event server and a cooperation server. There is a configuration example of an event server. It is an example of event setting information. It is an example of event notification information. Data example of event definition information. There is a processing flow example of the event server. It is a processing flow example of a cooperation server. It is an example of notification between an event server and a cooperation server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Event information analysis procedure 20 Event notification procedure 30 Measure completion notification reception procedure 40 Event execution procedure 50 Cooperation event measure procedure 60 System restart notification procedure 100 Event server 110 CPU
DESCRIPTION OF SYMBOLS 120 Communication control part 121 Network 130 Input / output control part 131 Keyboard 132 Display 140 Event definition information storage part 150 History information storage part 160 Operation management program 161 Event setting part 162 Event setting information analysis part 163 Event notification part 164 Action completion notification receiving part 165 Event execution part 166 Cooperation event measure part

Claims (5)

An event server operation management program in which one or more servers are connected via a network,
In the event server,
An event analysis procedure for analyzing event setting information in which event details executed by the event server are described based on an event definition file prepared in advance;
Based on the result of the analysis, an event notification procedure for creating and notifying event notification information in a linked server related to the event among the one or more servers;
A measure completion notification receiving procedure for receiving a measure completion notification indicating that a measure to be dealt with on the linked server side in accordance with the event is completed from the linked server;
An event execution procedure for executing processing of the event when the action completion notification is received from all the linked servers that have notified the event information notification;
Operation management program to execute When the operation management program further receives event notification information from the one or more servers, the operation management program transfers the event notification information to a linked server related to the event of the event notification information on a server different from the server, Receiving a notification that the measure associated with the event at the cooperation server has been completed after taking the measure associated with the event, and returning a measure completion notification to the server;
The operation management program according to claim 1, wherein: The operation management program further restarts the system of the event after executing the event in the event execution procedure, and notifies the cooperation server, the administrator of the cooperation server, and the user of the system restart notification procedure. When,
The operation management program according to claim 1 or 2, characterized by comprising: The event notification procedure includes:
Based on the result of the analysis, event notification information is created and notified to the cooperation server related to the event in the one or more servers, and the administrator of the cooperation server and the user of the event server To notify the contents of the event notification information to
The operation management program according to any one of claims 1 to 3. An event server operation management method in which one or more servers are connected via a network,
The event server is
An event analysis procedure for analyzing event setting information in which event details executed by the event server are described based on an event definition file prepared in advance;
Based on the result of the analysis, an event notification procedure for creating and notifying event notification information to a cooperative server related to the event among the one or more servers;
A measure completion notification receiving procedure for receiving a measure completion notification indicating that a measure to be dealt with on the linked server side in accordance with the event is completed from the linked server;
An event execution procedure for executing processing of the event when the action completion notification is received from all the linked servers notified of the event information notification;
When event notification information of an event executed on the server side is received from the one or more servers, the event notification information is transferred to a cooperation server related to the event by a server different from the server, and the event A coordinated event action procedure for notifying the server that sent the event notification information after taking the action associated with the action completion notice;
An operation management method characterized by comprising:

Images