Automated discovery of a multitier compute infrastructure

• US 7,962,590 B1
• Filed: 03/17/2003
• Issued: 06/14/2011
• Est. Priority Date: 07/17/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Or, Yan, Koper, John, Bellur, Umesh, Chandler, Girard, Casier, Johan, Sundaresan, Vinu, Garimella, Krishna, Joshi, Shashank
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): Patel; Dhairya A
• Application Number:
  US10/391,124
• Time in Patent Office: 3,011 Days
• Field of Search: 709/223, 709/224, 709/225, 707/105
• US Class Current: 709/223
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/24 Object-oriented

Abstract

A topology of a multitier compute infrastructure is automatically discovered. Discovery can be roughly divided into two phases. In one phase, components and physical relationships are discovered. In the other phase, non-physical relationships between the components are deduced. The second phase typically is based in part on information obtained in the first phase. In one application, the components and relationships that are discovered/deduced are used to build a map of the multitier compute infrastructure.

Claims

1. A computer-implemented method implemented in modules of a computer apparatus for discovering a topology of a multitier compute infrastructure, the method comprising:

discovering components in the multitier compute infrastructure, including components in an application tier, compute tier, and network tier;

discovering physical relationships between components in the multitier compute infrastructure, including components in the application, compute, and network tiers and a containment of applications on hardware components;

generating an inventory of discovered components and the physical relationships, including a business services component table indicating business services, an application component table, and a network component table, wherein a business service defines relationship between components in the multitier compute infrastructure and business functions; and

deducing non-physical relationships between components in the inventory, based at least in part on information obtained in the operations of discovering components and discovering physical relationships, wherein the deduced non-physical relationships comprise at least one of transactional dependencies indicating connectivity between applications and service dependencies indicating services an application uses, and wherein the deduced non-physical relationships include at least a first relationship table identifying a containment relationship of the network components indicated in the network component table containing application components indicated in the application component table, and a second relationship table identifying business services and the application components indicated in the application component table that perform the business service functions;

generating the topology map of the multitier compute infrastructure to include information from the generated inventory and the deduced non-physical relationships.

2. The computer-implemented method of claim 1 wherein:

the multitier compute infrastructure includes network components, compute components and application components; and

the generating the inventory comprises generating the inventory including network components, compute components and application components.

3. The computer-implemented method of claim 2 wherein the discovering of the components in the multitier compute infrastructure comprises:

discovering application components in the multitier compute infrastructure; and

discovering version and configuration information for at least some of the discovered application components.

4. The computer-implemented method of claim 2 wherein the deducing non-physical relationships comprises:

deducing application-level relationships between components in the inventory.

5. The computer-implemented method of claim 1 wherein the discovering components is guided by input from a user.

6. The computer-implemented method of claim 1 wherein the discovering components comprises:

obtaining results for a series of inquiries, the inquiries triggered by results obtained for previous inquiries.

7. The computer-implemented method of claim 6 wherein the results are obtained for inquiries in an asynchronous, parallel manner.

8. The computer-implemented method of claim 7 wherein the obtaining results for a series of inquiries comprises:

requesting user intervention if an inquiry is blocked.

9. The computer-implemented method of claim 7 wherein:

the discovering components further comprises receiving intervention information before beginning the step of obtaining results for a series of inquiries; and

using the intervention information to avoid blocking of inquiries.

10. The computer-implemented method of claim 9 wherein the intervention information includes passwords for access to components.

11. The computer-implemented method of claim 1 further comprising:

building a multitier topology map based at least in part on the inventory of discovered components, the discovered physical relationships and the deduced non-physical relationships.

12. The computer-implemented method of claim 11 wherein:

the discovering components comprises obtaining results for a series of inquiries;

the series of inquiries is selected to match a structure of the multitier topology map; and

the building the multitier topology map comprises populating the multitier topology map with results for the inquiries.

13. The computer-implemented method of claim 11 wherein:

the multitier compute infrastructure includes at least two parts;

the discovering components, discovering physical relationships between components, generating an inventory of discovered components and deducing non-physical relationships between components are performed separately for each part; and

the building the multitier topology map is based at least in part on the inventory of discovered components, the discovered physical relationships and the deduced non-physical relationships for the parts.

14. The computer-implemented method of claim 1 further comprising:

receiving user-defined components based on the components in the inventory and/or receiving user-defined relationships between components.

15. The computer-implemented method of claim 14 wherein the user-defined components include business application packages and/or business services.

16. The computer-implemented method of claim 1 wherein the discovering components, discovering physical relationships between components and generating an inventory of discovered components occurs separately in time from the deducing non-physical relationships between components.

17. The computer implemented method of claim 1, further comprising:

receiving user input manually defining higher-level components and relationships comprising business application packages and business services, wherein the generated topology indicates the user defined higher-level components.

18. An interface module implemented in a computer apparatus having a processor, wherein the processor executes the interface module to discover a topology of a multitier compute infrastructure, the interface module comprising:

a discovery builder for discovering components in the multitier compute infrastructure, for discovering physical relationships between components in the multitier compute infrastructure, including components in an application, compute, and network tiers and a containment of applications on hardware components, and for generating an inventory of discovered components and the physical relationships, including a business services component table, and a network component table, wherein a business service defines relationship between components in the multitier compute infrastructure and business functions;

a dependency builder for deducing non-physical relationships between discovered components, based at least in part on information discovered by the discovery builder, wherein the deduced non-physical relationships comprise at least one of transactional dependencies indicating connectivity between applications and service dependencies indicating services an application uses, and wherein the deduced non-physical relationships include at least a first relationship table identifying a containment relationship of the network components indicated in the network component table containing application components indicated in the application component table, and a second relationship table identifying business services and the application components indicated in the application component table that perform the business service functions; and

a topology manager for building a multitier topology map of the multitier compute infrastructure based at least in part on information discovered by the discovery builder on the dependency builder.

19. The interface module of claim 18 wherein the dependency builder is further for deducing application-level relationships between components.

20. The interface module of claim 18 further comprising:

an update module for performing incremental updates to the multitier topology map.

21. The interface module of claim 18 wherein the interface module is based on 100% Java.

22. The interface module of claim 18 wherein the interface module is implemented as a distributed software application.

23. The interface module of claim 18 further comprising:

a scope manager for defining a boundary of the multitier compute infrastructure.

24. The interface module of claim 18 wherein:

the multitier compute infrastructure implements a J2EE software component architecture having entity Java beans (EJBs); and

the components of the multitier compute infrastructure include EJBs from the J2EE software component architecture.

25. The interface module of claim 18, further comprising:

a user interface for receiving user input manually defining higher-level components and relationships comprising business application packages and business services, wherein the generated topology indicates the user defined higher-level components.

26. A dependency builder implemented in a computer apparatus having a processor, wherein the processor executes the dependency builder for deducing non-physical relationships between components in an inventory for a multitier compute infrastructure, the dependency builder comprising:

a plurality of agents, each agents for deducing a specific non-physical relationship, wherein the deduced non-physical relationships comprise at least one of transactional dependencies indicating connectivity between applications and service dependencies indicating services an application uses, wherein the deduced non-physical relationships are determined from an inventory of discovered components in the multitier compute infrastructure and discovered physical relationships between the components in the multitier compute infrastructure, including components in an application tier, compute tier, and network tier, wherein the inventory includes a business services component table indicating business services, an application component table, and a network component table, wherein a business service defines relationship between components in the multitier compute infrastructure and business functions, and wherein the deduced non-physical relationships include at least a first relationship table identifying a containment relationship of the network components indicated in the network component table containing application components indicated in the application component table, and a second relationship table identifying business services and the application components indicated in the application component table that perform the business service functions; and

a dependency manager for dispatching the agents and communicate with a topology manager to maintain a multi-tier topology map.

27. The dependency builder of claim 26 wherein the dependency manager dispatches the agents in a predetermined order.