JP2005258501A - Obstacle influence extent analyzing system, obstacle influence extent analyzing method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To specify a task influence for any system failure occurring in a task system configured on a network. <P>SOLUTION: Each of a task cooperation information defining part 112, a computer base cooperation information defining part 115 and a task network path information defining part 118 generates information showing a relation between software, hardware and a network path included in a computer system and tasks for which they are used, and stores it in a configuration information repository 123, and when any system failure is generated in the computer system, a generation site information inputting part 142 inputs generation site information, and a task influence analyzing part 131 refers to the configuration information in the configuration information repository 123, and retrieves the software, hardware and network path having a cooperative and dependent relation with the generation site, and specifies any task to be affected by the system failure, and a task influence range display part 141 displays the specified task name. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an analysis technique for analyzing an influence range of a system failure when a system failure occurs in a computer system.

Conventionally, in order to identify and present the impact of a failure that occurred in each part of a business system on the business, associate the business flow with the actual computer using the definition information entered at the time of design. Management, it is possible to perform operational work from a business viewpoint (for example, Patent Document 1). In addition, in order to estimate the influence range due to a network failure, a management object is provided for each management target of the network, and it is possible to estimate the failure influence range of the multilayer network from the connection relation and inclusion relation between the management objects (for example, Patent Document 2).
JP-A-2002-49493, page 7, FIG. JP-A-2000-69003, pages 2 to 3, FIGS. 3 and 2

  Since the conventional program control information generation method (Patent Document 1) does not associate the configuration information of the network device with the business system, it is impossible to identify the influence of the failure of each device configuring the network on the business system. There was a problem. In addition, since the conventional network failure impact range estimation method (Patent Document 2) does not relate the business configuration to the network configuration when the business system is built on the network, it identifies the business impact on the failure that occurred. There was a problem that could not be done.

  The present invention has been made to solve the above-mentioned problems, and a first object is to identify the business impact on the system failure of each part occurring in the business system configured on the network. To obtain a method to do this.

  The second purpose is to manage the association of each part of the information system business, computer infrastructure, and network so that the configuration of the business system can be referred to. By making it visually identifiable, the time required for planning countermeasures against the failure is reduced.

  Furthermore, the third object is that each designer can define the association of each part separately for the information system business, computer infrastructure, and network, so that the operation for the information system configuration definition and the information system configuration It makes it easier to operate for changes.

The failure influence range analysis system according to the present invention is:
A failure impact range analysis system that analyzes the impact range of a system failure when a system failure occurs in a computer system,
A resource / theme definition information storage unit for storing resource / theme definition information for defining which work theme each of the resources included in the computer system is used;
When a system failure occurs in the computer system, an occurrence factor identifying unit that identifies an occurrence factor resource that has caused the system failure;
A work theme extraction unit that searches resource / theme definition information and extracts a work theme that uses the generation factor resource specified by the generation factor identification unit;
And a work theme output unit that outputs the work theme extracted by the work theme extraction unit as a system failure influence range.

  According to the present invention, when a system failure occurs in a computer system, it is possible to specify a work theme that the system failure affects, and it is possible to quickly take appropriate measures against the system failure.

Embodiment 1 FIG.
FIG. 1 is a system configuration diagram according to Embodiment 1 of the present invention.
In FIG. 1, reference numerals 170 to 179 denote computers for executing business, and are connected to the backbone network 500 through network relay apparatuses 151 and 152 to constitute a computer system. Each computer executes a plurality of tasks (work themes). The number of computers for executing business and the number of network relay devices for connecting the computers to the backbone network increase or decrease sequentially depending on business requirements and the number of business operations.

  Reference numeral 110 denotes a business cooperation information definition client, which includes an input device 164 for a business designer to input business cooperation information and a display device 160 that displays a definition screen. The business cooperation information definition unit 112 performs a business operation according to the input information. Cooperation information is generated and stored in the business cooperation information storage unit 111.

  A computer infrastructure linkage information definition client 113 includes an input device 165 for a computer infrastructure designer to input cooperation information of a part in the computer and a display device 161 for displaying a definition screen. Generates computer infrastructure linkage information according to the input information and stores it in the computer infrastructure linkage information storage unit 114.

  A business network route information definition client 116 includes an input device 166 for inputting network route information used by the network designer for business and a display device 162 for displaying a definition screen. The business network route information definition unit 118 includes: Business network route information is generated according to the input information and stored in the business network route information storage unit 117.

  A configuration information management server 120 includes a business configuration import unit 121 and a configuration information management unit 122, which synthesizes business cooperation information, computer infrastructure cooperation information, and business network route information and accumulates them in the configuration information repository 123.

  A business impact analysis server 130 includes a business impact analysis unit 131 and identifies a business impact range from business configuration information in the configuration information repository 123.

  Reference numeral 140 denotes a business impact display client. The business impact range display unit 141 for displaying the business impact range specified by the business impact analysis unit 131, a fault occurrence part (cause factor) input from a monitoring operator or a system administrator A generation site information input unit 142 for receiving information on the display device, a display device 163, and an input device 167.

  Further, the business linkage information definition client 110, the computer infrastructure linkage information definition client 113, the business network route information definition client 116, the configuration information management server 120, the business impact analysis server 130, and the business impact display client 140 are mutually connected by the network relay device 150. And connected to the backbone network 500.

  Further, in this specification, the range surrounded by the broken line in FIG. 1 corresponds to an example of the failure influence range analysis system, and the business linkage information definition unit 112 is an example of the linkage relationship information generation unit. 115 is an example of the dependency relationship information generation unit, the business network route information definition unit 118 is an example of the network route information generation unit, the configuration information repository 123 is an example of the resource / theme definition information storage unit, and the business impact analysis unit 131 is In the example of the work theme extraction unit, the work influence range display unit 141 corresponds to an example of a work theme output unit, and the occurrence site information input unit 142 corresponds to an example of an occurrence factor identification unit.

  Also, in this specification, business will be described as an example of a work theme. Further, as examples of resources included in the computer system, application programs, middleware, software such as operating systems, hardware such as hard disk drives, network paths, and the like will be described as examples.

  Next, the operation will be described with reference to FIGS. 1 to 6, FIG. 16, and FIG.

  In FIG. 1, the business designer uses the input device 164 and the display device 160 to define business applications and middleware, business applications and hardware, and cooperation between business applications for a specific business. The business cooperation information definition unit 112 generates business cooperation information from the input definition information and stores it in the business cooperation information storage unit 111 (step 1601 in FIG. 16). FIG. 2 is an example of the business cooperation information defined by the business designer displayed on the display device 160. In this example, the business application 200 in the business server 20 (denoted as business App in the figure) is dependent on the message communication middleware 202 (denoted as message communication in the figure) by an arrow 201. In the branch server 21, the business application 211 depends on the database 214 (denoted as DB in the figure) by an arrow 212 and depends on the message communication middleware 215 by an arrow 213. In the client 22, the business application 221 indicates that it depends on the printer 224 by an arrow 222 and depends on the browser 225 by an arrow 223. Furthermore, the thick line 23 in the figure indicates the cooperation between the business applications. Here, all of the business application 200 on the business server 20, the business application 211 on the branch server, and the business application 221 on the client operate. Indicates that the transaction for the business is established. The business cooperation information corresponds to an example of cooperation relation information.

  Next, in FIG. 1, the computer infrastructure designer uses the input device 165 and the display device 161 to define the dependency of the middleware, operating system, and hardware in the computer existing in the business system for each computer. The computer infrastructure cooperation information definition unit 115 generates computer infrastructure cooperation information from the input definition information and stores it in the computer infrastructure cooperation information storage section 114 (step 1602 in FIG. 16). FIG. 3 is an example of computer infrastructure linkage information defined by the computer infrastructure designer displayed on the display device 161. In this example, the message communication middleware 202 in the business server 20 depends on the operating system 302 (denoted as OS1 in the figure) by the arrow 300 and depends on the hard disk drive 306 (denoted by HDD1 in the figure) by the arrow 301. Indicates that Further, the operating system 302 indicates that it depends on the hardware 305 of the computer main body (denoted as main body 1 in the drawing) by an arrow 303 and depends on the hard disk drive 306 by an arrow 304. Further, the hardware 305 of the computer main body indicates that it depends on the network interface card 308 (denoted as NIC 1 in the drawing) by an arrow 307. In the DNS server 30, DNS middleware 309 (indicated as DNS in the figure) depends on an operating system 311 (indicated as OS2 in the figure) by an arrow 310, and the operating system 311 indicates hardware of the computer main body by an arrow 312. The hardware 313 of the computer main body depends on the network interface card 315 (denoted as NIC 2 in the figure) by an arrow 314. Further, in the branch server 21, the database 214 depends on the hard disk drive 324 (denoted as HDD2 in the figure) by an arrow 316 and depends on the operating system 320 (denoted by OS3 in the figure) by an arrow 317. It shows that. Further, the message communication middleware 215 indicates that it depends on the operating system 320 by an arrow 318 and depends on the hard disk drive 326 (denoted as HDD 3 in the drawing) by an arrow 319. Further, the operating system 320 depends on the DNS middleware 309 on the DNS server 30 by the arrow 321, depends on the hard disk drive 324 by the arrow 322, and hardware 325 of the computer main body by the arrow 323 (denoted as the main body 3 in the figure). Indicates that it depends on. Further, the hardware 325 of the computer main body indicates that it depends on the network interface card 328 (denoted as NIC 3 in the drawing) by an arrow 327. In the client 22, the browser 225 indicates that it depends on the operating system 330 (denoted as OS 4 in the drawing) by an arrow 329. Further, the operating system 330 is dependent on the printer 224 by an arrow 331 and is dependent on the hardware 333 of the computer main body (denoted as the main body 4 in the drawing) by an arrow 332. Further, the hardware 333 of the computer main body indicates that it depends on the network interface card 335 (denoted as NIC 4 in the figure) by an arrow 334. 2 that are the same as those in FIG. 2 are assigned the same reference numerals and redundant description is omitted. The computer infrastructure linkage information corresponds to an example of dependency relationship information.

  Next, in FIG. 1, the network designer uses the input device 166 and the display device 162 to define a network route for a specific task. The business network route information definition unit 118 generates business network route information from the input definition information and stores it in the business network route information storage unit 117 (step 1603 in FIG. 16). FIG. 4 is an example of business network route information defined by the network designer displayed on the display device 162. In this example, reference numerals 400 to 416 denote network repeaters, which are connected to network interface cards between the network repeaters and in the computer as indicated by thin lines in the figure. In this example, the operation of the business requires that the client 22, the branch server 21, the DNS server 30, and the business server 20 can communicate with each other, and the network path used by the business is as indicated by a bold line 40. It shows that it becomes. The network designer defines such a network route for each business. In addition, about the same component as FIG. 3, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted. The business network route information corresponds to an example of network route information.

  Next, each of the business designer, computer infrastructure designer, and network designer uses the business configuration import unit 121 on the configuration information management server 120 to transfer the configuration information repository 123 to the business cooperation information storage unit 111. Each of the stored business configuration information, computer infrastructure linkage information stored in the computer infrastructure cooperation information storage unit 114, and business network route information stored in the business network route information storage unit 117 is input (FIG. 16 steps 1604). At this time, the configuration information management unit 122 is a database management mechanism, and performs exclusive processing for data input into the configuration information repository and data combination processing. Finally, the data shown in the examples of FIGS. 2, 3, and 4 is stored in the configuration information repository as configuration information in the form shown in FIG. In FIG. 5, the elements in the figure are the same as the elements shown in FIGS. Note that the component element information corresponds to an example of resource / theme definition information.

  The above is the processing that should be performed before a failure occurs in the computer system.

  Next, when a failure occurs in the computer system (Yes in step 1701 in FIG. 17), the monitoring operator or system administrator uses the input device 167 and the display device 163 to obtain the occurrence site information regarding the occurrence site of the failure. The generated part information input unit 142 receives the generated part information (step 1702), and transmits it to the business effect analysis unit 131 on the business effect analysis server 130. Next, the business impact analysis unit 131 of the business impact analysis server 130 extracts a business name affected by the system failure (step 1703). Here, the contents of the processing in step 1703 will be described in detail with reference to the flowchart of FIG.

FIG. 6 is a flowchart showing the processing of the business impact analysis unit 131 in FIG. The business impact analysis unit 131 searches the configuration information repository for the input failure occurrence site, obtains whether or not the failure occurrence site is a network (step 601), and determines whether or not the failure has occurred in the network. (Step 602). If the failure location is a network, the business network path including the failed device is extracted from the configuration information repository (step 603), and the business name for the extracted business network path is extracted from the configuration information repository (step 604). ), And outputs the extracted business name to the business impact display client 140 (step 610). For example, when the network relay device 405 fails in the example of FIG. 5, the device becomes a network device used in the business network path 40, and therefore the business name corresponding to the business network path 40 is sent to the business impact display client 140. Is output. On the other hand, when the failure occurrence site is other than the network, the site that depends on the failure occurrence site is extracted from the configuration information repository (step 605), and the dependency source site is traced until the extracted site becomes a business application. Search (steps 606 and 607), extract the cooperation between the business applications corresponding to the extracted business application from the configuration information repository (step 608), and extract the business name corresponding to the cooperation between the business applications from the configuration information repository. (Step 609), and outputs the extracted business name to the business impact display client 140 (Step 610). For example, when a failure occurs in the DNS middleware 309 on the DNS server 30 in the example of FIG. 5, the operating system 320, the database 214, and the message communication middleware 215 on the branch server 21 are extracted, and finally the business application 211 is extracted. Thus, the link 23 between the business applications linked with the business application 211 is extracted, and the business name corresponding to the link 23 between the business applications is output to the business impact display client 140.
The business name output by the business impact analysis unit 131 in this way is displayed on the display device 163 by the business impact range display unit 141 of the business impact display client 140 (step 1704 in FIG. 17).

  As described above, the business configuration is defined on the network by associating the linkage information between business applications, the network path used by the business, and the middleware, operating system, and hardware dependencies that make up the computer. It is possible to specify the business impact on the system failure of each part that occurs in the configured business system. For this reason, it is possible to quickly take appropriate measures against a system failure.

  Also, by dividing the business configuration input into input by the business designer, input by the computer infrastructure designer, and input by the network designer, each designer can independently maintain and manage the configuration. Become.

  Further, it is possible to reduce the time required for the work for specifying the affected area for the failure that has been performed manually in the conventional system, and to reduce the number of people involved in the work for specifying the affected area.

  In the above description, the business linkage information definition client 110, the computer infrastructure linkage information definition client 113, the business network route information definition client 116, the configuration information management server 120, the business impact analysis server 130, which constitute the failure impact range analysis system, Although the business influence display client 140 is a separate device, it is also possible to make them a single computer. In this case, each process (steps shown in FIGS. 6, 16, and 17) of the above-described failure influence range analysis system is used as a program, and the function of the failure influence range analysis system is realized by the CPU reading this program. Is possible.

Embodiment 2. FIG.
In the first embodiment described above, the network designer specifies the network route used by each business. Next, the network configuration management server holds the connection information of the network device and the computer. In this embodiment, the network route used by each business is extracted from the information and defined.

  FIG. 7 is a system configuration diagram according to the present embodiment. In FIG. 7, reference numeral 70 denotes a network configuration management server, which holds network device and computer connection information as network connection information in the network connection information storage unit 71 in order to monitor network interfaces of network devices and computers. It is. The configuration information management server 120 includes a network topology import unit 72 and a business network route information extraction unit 73. In addition, about the same component as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Next, the operation will be described.
The network connection information storage unit 71 on the network configuration management server 70 stores connection information of network interfaces of network devices and computers. In the present embodiment, instead of the network administrator inputting the business network connection information, the network topology import unit 72 on the configuration information management server 120 receives the network interface and computer network interface connection information from the network connection information storage unit 71. Are imported into the configuration information repository 123. Further, the business network route information extraction unit 73 on the configuration information management server 120 stores the business cooperation information input by the business designer and stored in the configuration information repository 123 and the business cooperation information input by the computer infrastructure designer and stored in the configuration information repository 123. From the computer base linkage information, the computer used for the business is extracted, and the network interface card for the computer used is extracted. Further, the business network route information extraction unit 73 extracts a network route for communication with a plurality of extracted network interface cards from the network connection information imported into the configuration information repository, and accumulates it in the configuration information repository 123 as business network route information. . Subsequent operations are the same as those in the first embodiment.

  As described above, the network route used by each business is extracted from the existing information and stored. Therefore, it is possible to input the business configuration information to identify the business impact range when a failure occurs in the information system. The configuration input load of the network administrator with the highest load can be reduced.

Embodiment 3 FIG.
In the first embodiment, a business designer or a computer infrastructure designer defines business application placement information, middleware placement information, operating system placement information, and hardware placement information on a computer. Next, an embodiment in the case where these pieces of arrangement information are automatically collected and defined from within the management target computer will be described.
FIG. 8 is a system configuration diagram according to the present embodiment.
In FIG. 8, reference numeral 80 denotes a configuration information collection agent, which is a program that resides in a computer in order to acquire system configuration information in the computer. In the figure, it is described in the computer 170 for executing the business, but it is provided inside all the computers for executing the business of 171 to 179. The configuration information management server 120 includes a configuration information collection unit 81. In addition, about the same component as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Next, the operation will be described.
The configuration information collection unit 81 is activated by the system administrator, communicates with the configuration information collection agent 80 arranged in the computer for executing the business, and configures the business program, middleware, operating system, and hardware in the computer. Information is acquired and used as the business cooperation information and computer infrastructure cooperation information described in the first embodiment, and is stored in the configuration information repository 123 using the configuration information management unit 122. Subsequent operations are the same as those in the first and second embodiments.

  In this embodiment, the configuration information collection unit 81 generates business cooperation information (cooperation relationship information) and computer infrastructure cooperation information (dependency relationship information), and the configuration information collection unit 81 generates the cooperation relationship information. Software and hardware included in the computer system via the configuration information collection agent 80, which corresponds to an example of a generation unit and dependency relationship information generation unit, and a configuration information collection unit 81 corresponding to a linkage relationship information generation unit and dependency relationship information generation unit The system configuration information is detected and business linkage information and computer infrastructure linkage information are generated.

  As described above, the business designer in the computer to execute the business, middleware, operating system, hardware configuration information is automatically collected and defined, so when the business designer defines the business linkage information, And when the computer infrastructure designer defines the computer infrastructure linkage information, the configuration information on the actual computer is acquired, so input errors of the business designer and computer infrastructure designer are reduced. Further, the operation load when the business designer defines the business cooperation information and when the computer infrastructure designer defines the computer infrastructure cooperation information is also reduced.

Embodiment 4 FIG.
In the first embodiment, business cooperation information and computer infrastructure cooperation information are defined for a business system actually constructed by a business designer and a computer infrastructure designer. An embodiment in which a base designer defines such information at the time of system design will be described.

  FIG. 9 shows an example of the contents (input command) of the business cooperation information defined by the business designer when designing the system. In FIG. 9, reference numeral 90 denotes a constituent part, which describes a layer 91 of the constituent part and a name 92 of the constituent part. Reference numeral 93 denotes a site of dependence.

  FIG. 10 shows an example of the contents (input command) of the computer infrastructure linkage information defined by the computer infrastructure designer at the time of system design. In FIG. 10, reference numeral 1000 denotes a constituent part, which describes a layer 1001 of the constituent part and a name 1002 of the constituent part. Reference numeral 1003 indicates a site of dependence.

  In the table of FIG. 9, the business designer describes the configuration part for the definition of the business itself (layer = business, name = business A in the example in the figure), and the business application on which the business depends (Business App1, Business App2, Business App3 in the example shown in the figure). Further, for the business application, a component part is described (in the example of the figure, layer = business App, name = business App1), and a component part on which the business application depends is described (message communication in the example of the figure).

  In addition, the computer infrastructure designer describes the components constituting the computer as a layer (middleware or operating system or hardware) in the table of FIG. 10 at the time of system design, and identifies the components that the component depends on. Describe by name.

  The table described in this way is used as the input of business cooperation information and computer infrastructure cooperation information in the first embodiment. Subsequent operations are the same as those in the first and second embodiments.

  As described above, by making it possible to input business linkage information and computer infrastructure linkage information using a table with the row direction as the component part and the column direction as the component part, the business linkage information and the computer infrastructure linkage information can be input during system design. It becomes possible to describe, and the operational load when defining business cooperation information and computer infrastructure cooperation information is reduced.

Embodiment 5 FIG.
In the first embodiment, business designers, computer infrastructure designers, and network designers enter business cooperation information, computer infrastructure cooperation information, and business network route information. An embodiment in which these pieces of information are combined and displayed will be described.

  FIG. 11 is a system configuration diagram according to the present embodiment. In FIG. 11, reference numeral 1100 denotes a business configuration search / display unit provided in the business impact display client 140. In the present embodiment, the business configuration search / display unit 1100 corresponds to an example of a resource extraction output unit by work theme. In addition, about the same component as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Next, the operation will be described.
In FIG. 11, when a monitoring operator or system administrator designates a business name using the input device 167, the business configuration search / display unit 1100 communicates with the configuration information management unit 122 of the configuration information management server 120, and the configuration information repository The computer base linkage information and the business network route information of the business name specified from 123 are integrated and extracted. The extraction result is data in the form as shown in FIG. 5, and the business configuration search / display unit 1100 displays the extraction result on the display device 163 in the same format as in FIG.

  As described above, the monitoring operator or system administrator visually displays the information that integrates the business linkage information, computer infrastructure linkage information, and business network route information for a specific job, so that the definition contents of these information It is possible to confirm the legitimacy, and to increase the accuracy of identifying the business influence range.

  In addition, when a business system failure occurs, the business impact range is specified, and when the affected business name is obtained, information that integrates the business linkage information, computer infrastructure linkage information, and business network route information for the specific job is visualized. By displaying them visually, the configuration of the affected work is clarified visually, and it becomes possible to improve the efficiency of the work planning for handling the failure.

Embodiment 6 FIG.
In the fifth embodiment, information obtained by integrating business cooperation information, computer infrastructure cooperation information, and business network route information for a specific business is extracted and displayed. An embodiment in which the information is displayed is shown.
The explanatory diagram in the present embodiment is the same as that in FIG.

Next, the operation will be described.
In the first embodiment and the sixth embodiment, when a failure occurs in the business system, in FIG. 11, the monitoring operator or the system administrator uses the input device 167 and the display device 163 to identify the failure occurrence site as a business impact analysis server. At this time, the failure occurrence part is also transmitted to the job configuration search / display unit 1100 on the job influence display client 140. The business configuration search / display unit 1100 communicates with the configuration information management unit 122 of the configuration information management server 120, and the computer base linkage information and business network of the business name (the business in the scope of influence of the failure) designated from the configuration information repository 123 The route information is integrated and extracted, and the content is displayed. At this time, the display portion 163 is displayed on the display device 163 with the display color changed. FIG. 12 is a display example of the content displayed on the display device 163. In this example, it is shown that a failure of the DNS server operating system (indicated as OS2 in the figure) 1200 affects the business. In FIG. 12, the same components as those in FIG.

  As described above, when a business system failure occurs, the business impact range is specified and the affected business name is obtained, and the information that integrates the business linkage information, computer infrastructure linkage information, and business network route information for the specific job In addition to the configuration of the affected work, the failure location is visually clarified and the work planning for the failure can be made more efficient.

Embodiment 7 FIG.
In the first embodiment, when the system failure occurs and the business influence range is specified, the monitoring operator or the system administrator inputs the failure occurrence part. Next, when the system failure occurs Fig. 5 shows an embodiment in which the business influence range is automatically specified.

  FIG. 13 is a system configuration diagram according to the present embodiment. In FIG. 13, reference numeral 1300 denotes a failure monitoring server, which includes a system failure monitoring unit 1301. The system failure monitoring unit 1301 corresponds to an example of an occurrence factor detection unit. Reference numeral 1302 denotes a failure monitoring agent, which is a program that resides in a computer in order to monitor a system failure in the computer. In the figure, it is described in the computer 170 for executing the business, but it is provided inside all the computers for executing the business of 171 to 179. In addition, a failure content receiving unit 1303 for receiving a notification from the system failure monitoring unit 1301 is provided in the business impact analysis server 130. In the present embodiment, the system failure monitoring unit 1301 corresponds to an example of an occurrence factor detection unit, and the failure content reception unit 1303 corresponds to an example of an occurrence factor identification unit. In addition, about the same component as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Next, the operation will be described.
When a system failure occurs, the system monitoring agent 1302 in the computer detects the location where the failure has occurred and notifies the system failure monitoring unit 1301 in the failure monitoring server 1300 of the failure. The system fault monitoring unit 1301 notifies the fault content receiving unit 1303 in the business impact analysis server 130 of the site where the fault has occurred, and the fault content receiving unit 1303 inputs the faulted site to the business impact analyzing unit 131. Subsequent operations are the same as those in the first embodiment.

  As described above, when a system failure occurs, the location of the failure is automatically notified to the business impact analysis unit, so it is possible to automatically identify the business impact range immediately after the failure occurs. The system administrator's work to deal with the failure is speeded up, and when the failure occurs in the system, the work can be immediately performed. Therefore, the recovery time of the system failure is shortened.

Embodiment 8 FIG.
In the first to seventh embodiments, the business influence range is specified based only on the information on the fault occurrence site. Next, the business influence range is notified in consideration of the importance of the fault. An embodiment of the case is shown.
The explanatory diagram in the present embodiment is the same as that in FIG.

Next, the operation will be described.
When a system failure occurs, the system monitoring agent 1302 in the computer detects the location where the failure has occurred and notifies the system failure monitoring unit 1301 in the failure monitoring server 1300. At this time, the importance of the failure (for example, High / Medium / Low) is also notified to the system failure monitoring unit 1301. The system failure monitoring unit 1301 notifies the failure content receiving unit 1303 in the business impact analysis server 130 together with the location where the failure has occurred and the importance of the failure, and the failure content receiving unit 1303 reports the location of the failure and the importance of the failure. Is input to the business impact analysis unit 131. The subsequent operations are the same as in the first embodiment, but the business impact analysis unit 131 outputs the business severity affected by the failure and the importance of the failure, and the business impact range display unit 141 displays the business name affected by the failure. And the severity of the fault.

  As described above, regarding the business impact range display when a system failure occurs, by simultaneously displaying the importance of the failure, it is possible to prioritize the response to the system failure, and to efficiently deal with the failure.

Embodiment 9 FIG.
In the third embodiment, a configuration information collection agent is provided on a computer for executing business, and configuration information of business programs, middleware, operating systems, and hardware in the computer is automatically acquired. However, an embodiment in which the configuration change of the computer is automatically detected and the business configuration information is updated when these configurations on the computer are changed will be described.

  FIG. 14 is a system configuration diagram according to the present embodiment. In FIG. 14, 1400 is a configuration change management agent, which is a program for detecting changes in system configuration information in the computer and recording the changed contents. In the figure, it is described in the computer 170 for executing the business, but it is provided inside all the computers for executing the business of 171 to 179. In addition, about the same component as FIG. 8, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Next, the operation will be described.
The configuration change management agent 1400 resides in a computer that executes business, and monitors changes in configuration information of business programs, middleware, operating systems, and hardware in the computer. When there is a change in the configuration information, the change content is notified to the configuration information collection unit 81 (corresponding to the cooperation relationship information generation unit and the dependency relationship information generation unit) of the configuration information management server 120. The configuration information collection unit 81 that has received the notification updates the configuration information repository 123 using the configuration information management unit 122 for the notification contents. Subsequent operations are the same as those in the first and second embodiments.

  As described above, since the system configuration of the computer is automatically followed, even if the configuration of the computer changes, it is possible to maintain the specific accuracy of the work influence range without any manual intervention. It is also possible to prevent an erroneous change of the business configuration definition due to human error.

Embodiment 10 FIG.
In the third embodiment, the configuration information of the business program, middleware, operating system, and hardware in the computer is automatically acquired. An embodiment in which consistency with designed information is confirmed will be described.

  FIG. 15 is a system configuration diagram according to the present embodiment. In FIG. 15, reference numeral 1500 denotes a computer infrastructure design holding unit for inputting a computer infrastructure design and storing it in the computer infrastructure design value information storage unit 1501. Both the computer infrastructure design holding unit 1500 and the computer infrastructure design value information storage unit 1501 are provided on the configuration information management server 120. In the present embodiment, the computer infrastructure linkage information definition unit 115 corresponds to an example of a first dependency relationship information generation unit, the configuration information collection unit 81 corresponds to an example of a second dependency relationship information generation unit, The computer base design holding unit 1500 corresponds to an example of an extracted value comparison unit. Moreover, the same components as those in FIG.

Next, the operation will be described.
The computer infrastructure designer generates computer infrastructure linkage information by the same method as in the first embodiment. That is, the computer infrastructure linkage information definition unit 115 receives input from a computer infrastructure designer via the input device 165 and generates computer infrastructure linkage information. Next, the computer infrastructure designer uses the computer infrastructure design holding unit 1500 on the configuration information management server 120 to extract only the design values of the middleware, operating system, and hardware from the computer infrastructure linkage information, and the computer infrastructure design value information. Saved in the storage unit 1501. The design value extracted from this computer infrastructure linkage information corresponds to the first extracted value. Further, as shown in the third embodiment, the configuration information collection unit 81 separately generates computer infrastructure cooperation information based on the configuration information acquired from the configuration information collection agent 80, and further, this computer infrastructure cooperation information. The middleware, operating system, and hardware setting values in the computer for executing the business are extracted from and stored in the configuration information repository 123. This set value corresponds to the second extracted value. Next, the computer infrastructure design holding unit 1500 stores the middleware, operating system, and hardware setting values (second extracted values) stored in the configuration information repository 123 by the configuration information collection unit 81 and computer infrastructure design value information. The contents of the design value (first extracted value) stored in the unit 1501 are compared to check the consistency. If the values are different, the computer base designer using the computer base design holding unit 1500 is notified. .

  As described above, it is possible to collate the design value at the time of system design with the actual setting value on the computer, and it is saved in the configuration information repository by preventing the design time information from differing from the actual setting value. Therefore, it is possible to maintain a certain accuracy of the business influence range when a system failure occurs. In addition, it is possible to prevent the computer from being configured as designed due to a setting error, which contributes to stable operation of the information system.

  Here, the characteristics of the failure influence range analysis system shown in the above embodiment will be described below.

The failure influence range analysis system shown in the above embodiment has the following means:
(A) Business linkage information definition means that enables a business designer who designs business applications and workflows to define linkages between business applications and middleware, business applications and hardware, and business applications. (B) Operating in the computer Computer infrastructure designers who can design system, middleware, and hardware, and which can set up their linkages. (C) Network designers who design business networks are networks that support specific tasks. Business network route information definition means for defining a route (d) Business cooperation information defined by the business cooperation information definition means (a), computer infrastructure cooperation information defined by the computer infrastructure cooperation information definition means (b), and business network route Defined by the information definition means (c) Configuration information database that holds network route information for a specific job in cooperation (e) When a system failure occurs in any of the parts constituting the information system, the location of the failure is specified and the configuration information database (d) Business impact analysis means to identify the impact range on business (d) is characterized by the fact that (a), (b), and (c) are held in cooperation, and the impact range of business can be identified by this database search It is characterized by becoming.

  Also, a network management server and business network route extraction means are provided, and network configuration information is specified by using the network connection information held by the network management server and extracting the network communication route between specific computers using the business network route extraction means. It is characterized by defining the network route for business and identifying the scope of business impact.

  In addition, a configuration information collection agent must be provided in the managed computer to automatically collect the operating system, middleware, and hardware configuration information in the computer, and to enable computer infrastructure linkage based on the collected configuration information. It is characterized by.

  Further, it is characterized in that input of business cooperation information and computer infrastructure cooperation information is input by a separate designer from a graphical user interface (GUI).

  Further, a table is provided in which the row direction is a component part and the column direction is a component part, and business cooperation information and computer infrastructure cooperation information are input using the table as an input.

  In addition, business configuration search / display means is provided, and the computer infrastructure linkage information is displayed on a computer basis for the identified business impact range, and the business linkage information is displayed superimposed on the display, and further superimposed on these displays. The business network route is displayed.

  In addition, in the business configuration display means, in addition to displaying the computer infrastructure linkage information, the business linkage information, and the business network path, the location of the fault location is clearly indicated, and the business impact range for the fault that has occurred is displayed superimposed on the business linkage information It is characterized by that.

  Further, the present invention is characterized in that failure content receiving means is provided, and the business influence range is automatically identified immediately after the occurrence of the failure by notifying the received work content to the work influence analyzing means.

  Also, by assigning importance to the failure content received by the failure content receiving means, adding the importance to the received failure content and notifying the business impact analysis means, the degree of business impact according to the importance of the failure can be determined. It is characterized by displaying.

  In addition, a configuration change management agent is provided in the management target computer in addition to the configuration information collection agent, and the configuration change of the computer is automatically detected and reflected in the business configuration.

  In addition, a computer base design value holding means is provided, and the design information designed by the computer base designer is collated with the automatically collected configuration information to check the consistency between the design value and the set value.

1 is a system configuration diagram according to Embodiment 1. FIG. FIG. 6 is a diagram illustrating an example of business cooperation information according to the first embodiment. FIG. 3 is a diagram showing an example of computer infrastructure linkage information according to the first embodiment. FIG. 4 is a diagram showing an example of business network route information according to the first embodiment. FIG. 4 is a diagram illustrating an example of configuration information according to the first embodiment. FIG. 4 is a flowchart showing a processing example of a business impact analysis unit according to the first embodiment. FIG. 4 is a system configuration diagram according to the second embodiment. FIG. 6 is a system configuration diagram according to Embodiment 3. FIG. 10 is a diagram illustrating an example of an input command according to the fourth embodiment. FIG. 10 is a diagram illustrating an example of an input command according to the fourth embodiment. FIG. 10 is a system configuration diagram according to the fifth embodiment. FIG. 18 shows a display example according to Embodiment 6; FIG. 18 is a system configuration diagram according to the seventh embodiment. FIG. 10 is a system configuration diagram according to the eighth embodiment. FIG. 18 is a system configuration diagram according to the tenth embodiment. FIG. 4 is a flowchart showing a processing example according to the first embodiment. FIG. 4 is a flowchart showing a processing example according to the first embodiment.

Explanation of symbols

  70 network configuration management server, 71 network connection information storage unit, 72 network topology information import unit, 73 business network route information extraction unit, 80 configuration information collection agent, 81 configuration information collection unit, 110 business linkage information definition client, 111 business linkage Information storage section, 112 Business cooperation information definition section, 113 Computer infrastructure cooperation information definition client, 114 Computer infrastructure cooperation information storage section, 115 Computer infrastructure cooperation information definition section, 116 Business network path information definition client, 117 Business network path information storage section 118 Business network route information definition unit, 120 Configuration information management server, 121 Business configuration import unit, 122 Configuration information management unit, 123 Configuration information repository, 130 Business impact analysis server, 1 31 business impact analysis unit, 140 business impact display client, 141 business impact range display unit, 142 occurrence site information input unit, 150 network relay device, 151 network relay device, 160 display device, 161 display device, 162 display device, 163 display Device, 164 input device, 165 input device, 166 input device, 170 computer, 171 computer, 172 computer, 173 computer, 174 computer, 175 computer, 176 computer, 177 computer, 178 computer, 179 computer, 500 backbone network, 1100 business Configuration search / display unit, 1300 fault monitoring server, 1301 system fault monitoring unit, 1302 system fault monitoring agent, 1303 fault content receiving unit, 1400 configuration change management agent, 1500 Machine foundation design holding unit, 1501 Computer infrastructure design value information storage unit.

Claims (18)

A failure impact range analysis system that analyzes the impact range of a system failure when a system failure occurs in a computer system,
A resource / theme definition information storage unit for storing resource / theme definition information for defining which work theme each of the resources included in the computer system is used;
When a system failure occurs in the computer system, an occurrence factor identifying unit that identifies an occurrence factor resource that has caused the system failure;
A work theme extraction unit that searches resource / theme definition information and extracts a work theme that uses the generation factor resource specified by the generation factor identification unit;
A failure influence range analysis system comprising: a work theme output unit that outputs a work theme extracted by the work theme extraction unit as a system failure influence range. The resource / theme definition information storage unit
Shows the linkage / dependency between software and hardware included in the computer system, and defines which work theme each of software and hardware is used based on the linkage / dependency between software and hardware Stores resource and theme definition information,
The work theme extraction unit
When the generation factor resource is specified as one of software and hardware included in the computer system by the generation factor identification unit, software or hardware that is linked or dependent on the generation factor software or hardware The failure influence range analysis system according to claim 1, wherein a work theme that uses software or hardware as a cause of occurrence is extracted. The resource / theme definition information storage unit
Storing resource theme definition information that defines which work theme each network path between computers included in the computer system is used for;
The work theme extraction unit
The work theme that uses the network path of the generation factor is extracted when the generation factor resource is specified as one of the network paths included in the computer system by the generation factor specifying unit. The failure influence range analysis system according to 1. The failure influence range analysis system is:
Analyzing the impact range of system failures for computer systems used for business,
The resource / theme definition information storage unit
Stores resource / theme definition information that defines in which business each resource included in the computer system is used,
The work theme extraction unit
Search the resource / theme definition information, extract the work that uses the cause resource specified by the cause determination part,
The work theme output unit
The failure influence range analysis system according to claim 1, wherein the work extracted by the work theme extraction unit is output as an influence range of a system failure. The failure influence range analysis system further includes:
Defines the linkage between application programs, middleware and hardware included in the computer system, and uses the application program, middleware and hardware for any work theme based on the linkage between application programs, middleware and hardware A linkage information generation unit that generates linkage information that defines what is to be done,
The resource / theme definition information storage unit
The failure influence range analysis system according to claim 2, wherein cooperation relation information generated by the cooperation relation information generation unit is stored as resource / theme definition information. The failure influence range analysis system further includes:
A dependency information generating unit for generating dependency information defining a dependency relationship between middleware, operating system and hardware included in the computer system;
The resource / theme definition information storage unit
6. The resource / theme definition information, wherein the association information generated by the association information generation unit and the dependency information generated by the dependency information generation unit are stored in association with each other. The failure impact range analysis system described. The failure influence range analysis system further includes:
A network path information generating unit that generates network path information that defines which work theme each network path between computers included in the computer system is used for;
The resource / theme definition information storage unit
6. The resource / theme definition information, wherein the association information generated by the association information generation unit and the network route information generated by the network route information generation unit are stored in association with each other. The failure impact range analysis system described. The network route information generation unit
8. The fault influence range analysis system according to claim 7, wherein network path information is generated using network connection information indicating a connection state between a computer and a network path included in the computer system. At least one of the cooperation relationship information generation unit and the dependency relationship information generation unit is:
The fault influence range analysis system according to claim 6, wherein the fault influence range analysis system according to claim 6, wherein the configuration of software and hardware included in the computer system is detected to generate at least one of linkage relationship information and dependency relationship information. At least one of the cooperation relationship information generation unit and the dependency relationship information generation unit is:
One of the resources of the application program, middleware, operating system, and hardware is indicated in the row direction, and any of the application program, middleware, operating system, and hardware that is linked or dependent on the resource indicated in the row direction 7. The failure influence range analysis system according to claim 6, wherein an input command in a tabular format shown in a column direction is accepted. The failure influence range analysis system further includes:
It is characterized by analyzing resource / theme definition information, extracting resource information used by a specific work theme from resource / theme definition information, and having a resource extraction / output section by work theme that outputs the extracted resource information. The failure influence range analysis system according to claim 1. The resource extraction output unit by work theme is
Information on all resources used by the work theme that uses the cause resource is extracted from the resource / theme definition information, and when the extracted resource information is output, the cause resource is output to be clearly indicated The failure influence range analysis system according to claim 11, wherein: The failure influence range analysis system further includes:
The computer system is monitored, and when a failure occurs in the computer system, an occurrence factor resource is detected, and an occurrence factor detection unit that notifies the occurrence factor identification unit to the detected occurrence factor resource,
The occurrence factor identifying unit is
The failure influence range analysis system according to claim 1, wherein an occurrence factor resource is specified based on a notification from the occurrence factor detection unit. The occurrence factor detector is
When a failure occurs in the computer system, the occurrence factor resource is detected, the importance of the failure is determined, the occurrence factor resource and the importance of the failure are notified to the occurrence factor identifying unit,
The work theme output unit
The work theme extracted by the work theme extraction unit is output as an influence range of a system failure, and the importance level of the failure notified from the generation factor detection unit to the generation factor identification unit is output. Item 14. The fault influence range analysis system according to Item 13. At least one of the cooperation relationship information generation unit and the dependency relationship information generation unit is:
7. When there is a change in the configuration of software and hardware included in the computer system, the change in the configuration is detected and at least one of the linkage relationship information and the dependency relationship information is updated. Fault impact range analysis system described in 1. The dependency relationship information generation unit
A first dependency information generating unit that receives input related to dependency between middleware, operating system, and hardware included in the computer system from a predetermined input destination, and generates dependency information;
A second dependency relationship information generation unit that detects a configuration between middleware, operating system, and hardware included in the computer system and generates dependency relationship information;
The failure influence range analysis system further includes:
A first extraction value extracted from the dependency relationship information generated by the first dependency relationship information generation unit and a second extraction extracted from the dependency relationship information generated by the second dependency relationship information generation unit When the first extracted value and the second extracted value are different from each other when the first extracted value and the second extracted value are different from each other, the first dependency relationship information indicates that the first extracted value and the second extracted value are different from each other. The failure influence range analysis system according to claim 6, further comprising an extraction value comparison unit that notifies an input destination of the generation unit. A failure impact range analysis method for analyzing the impact range of a system failure when a system failure occurs in a computer system,
A resource / theme definition information generating step for generating resource / theme definition information for defining which work theme each of the resources included in the computer system is used;
When a system failure occurs in the computer system, an occurrence factor identifying step for identifying an occurrence factor resource that has caused the system failure;
A work theme extraction step of searching for resource / theme definition information and extracting a work theme that uses the generation factor resource identified in the generation factor identification step;
A failure influence range analysis method comprising: a work theme output step of outputting the work theme extracted in the work theme extraction step as a system failure influence range. When a system failure occurs in a computer system, this is a program that causes a computer to analyze the range of influence of a system failure,
A resource / theme definition information generation process for generating resource / theme definition information that defines which work theme each of the resources included in the computer system is used;
When a system failure occurs in the computer system, an occurrence factor specifying process for specifying an occurrence factor resource that has caused the system failure; and
A search for resource / theme definition information, and a work theme extraction process for extracting a work theme that uses the cause resource identified by the cause determination process;
A program for causing a computer to execute a work theme output process for outputting a work theme extracted by the work theme extraction process as an influence range of a system failure.

Images