Configuration management architecture

• US 20050080811A1
• Filed: 08/17/2004
• Published: 04/14/2005
• Est. Priority Date: 10/10/2003
• Status: Abandoned Application

• Current Assignee: Cendura Corp. (Broadcom, Inc.)
• Original Assignee: Cendura Corp. (Broadcom, Inc.)
• Inventors: Talla, Venkateshwar, Bullis, Charles A., Duncan, David B., Speeter, Thomas H., Framba, Marco G.
• Application Number:
  US10/920,600
• Publication Number:
  US 20050080811A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

A system is for managing an application enterprise, wherein the application enterprise includes a plurality of distributed instances of a plurality of applications. The system includes a plurality of application blueprints, each application blueprint modeling a separate application. An enterprise data store is to hold enterprise data, representative of one or more states of the instances, according to the application blueprints. An application enterprise bus provides a standard interface to the enterprise data. A plurality of enterprise data access tools that each access the enterprise data via the application enterprise bus and provide a view of the current state of the application enterprise based thereon.

Claims

1. A system for managing an application enterprise, wherein the application enterprise includes a plurality of distributed instances of a plurality of applications, comprising:

a plurality of application blueprints, each application blueprint modeling a separate application;

an enterprise data store to hold enterprise data, representative of one or more states of the instances, according to the application blueprints;

an application enterprise bus providing a standard interface to the enterprise data; and

a plurality of enterprise data access tools that each access the enterprise data via the application enterprise bus and provide a view of the current state of the application enterprise based thereon.

2. The system of claim 1, wherein the enterprise data access tools include organizational tools for managing the applications and the application instances.

3. The system of claim 2, wherein:

the application enterprise bus defines a plurality of objects, each object characterized by a separate data model view of the application enterprise bus; and

the enterprise data access tools operate on the objects.

4. The system of claim 2, wherein:

the organization tools include a tool to communicate at least one image of the application instances between the system and processes outside the system.

5. The system of claim 4, wherein:

the tool to communicate the at least one image communicates the at least one image in a portable data format.

6. The system of claim 3, wherein:

the enterprise data access tools operating on the objects collectively accomplish management of the application enterprise.

7. The system of claim 1, wherein:

at least one of the applications includes at least one associated component;

the at least one associated component is modeled by a component blueprint.

8. The system of claim 7, wherein:

the component blueprint is referred to by the application blueprint modeling the application including the component.

9. The system of claim 1, wherein:

the application blueprints identify host types, and each host type is characterized by at least one associated component.

10. The system of claim 9, wherein:

the application blueprints further include rules characterizing interactions between the components.

11. The system of claim 9, wherein:

the at least one associated component being modeled by a component blueprint includes the component blueprint providing a data model of the associated component.

12. The system of claim 11, wherein:

the component blueprint includes categorizations and weights associated with the data elements in the associated component data model.

13. The system of claim 2, further comprising:

means for discovering installed components and applications on computational devices.

14. The system of claim 13, wherein:

the discovering means includes at least one agent process.

15. The system of claim 14, wherein:

wherein the at least one agent process is associated with at least one of the computational devices and, based on rules in the component blueprints, is configured to provide information about the components for that at least one associated computational device.

16. The system of claim 15, further comprising:

a discovery process configured to interact with the at least one agent process to coordinate execution of the at least one agent process and to correlate information provided by the at least one agent process to generate an image of the application instances.

17. The system of claim 16, wherein:

the discovery process is configured to search for components in the application enterprise based on at least one of the application blueprints.

18. The system of claim 17, wherein:

the at least one of the application blueprints includes component blueprints, and

searching for components in the application enterprise includes locating and verifying components based on the component blueprints included in the at least one of the application blueprints.

19. The system of claim 16, wherein:

the discovery process is configured to

search for and find components in the application enterprise without regard for particular applications to which the components belong; and

in addition to generating the image of the application instances, build at least one application blueprint based on the found components.

20. The system of claim 16, further comprising:

a refresh process configured to search for changes in the components of the application enterprise from an execution of a previous refresh process or discovery process.

21. The system of claim 16, further comprising:

an archive process configured to archive the image of the application images as a snapshot image.

22. The system of claim 2, further comprising:

a compare process configured to compare a first image of the application instances to a second image of the application instances.

23. The system of claim 22, wherein:

the first image of the application instances and the second images of the application instances are image of the same application instances, at different times.

24. The system of claim 22, wherein:

the first image of the application instances and the second image of the application instances are images of different application instances.

25. The system of claim 22, wherein:

the compare process is configured to compare images of application instances across space.

26. The system of claim 2, further comprising:

a compare process configured to compare a first portion of an image of the application instances to a second portion of the same image of the application instances.

27. The system of claim 22, wherein:

the component blueprint includes an indication of weighting and categories usable to tune the comparison.

28. The system of claim 22, wherein:

the component blueprint is configured to indicate relative importance of differences found during execution of the compare process.

29. The system of claim 28, wherein:

the differences are weighted and categorized according to the component blueprint configuration.

30. The system of claim 2, further comprising:

a process configured to discover elements of a deployment and to generate an image of the application instances based thereon; and

a verification process configured to process the image of the application instances to verify compliance with a plurality of rules.

31. The system of claim 30, wherein:

the rules define constraints on the deployment.

32. The system of claim 31, wherein:

the constraints on the deployment include limitations on values of characteristics of the deployment.

33. The system of claim 32, wherein:

the constraints on the deployment include limitations on a particular value of a characteristic relative to values of other characteristics.

34. The system of claim 31, wherein:

the rules are characterized by a severity level.

35. The system of claim 30, wherein:

the rules are defined in at the component blueprint.

36. The system of claim 35, wherein:

at least some of the rules are defined by implication based on restrictions and specifications in the component blueprint.

37. The system of claim 2, further comprising:

a process to export an image of the application instances from the system.

38. The system of claim 2, further comprising:

communication tools configured to provide multiple users access to addressable portions of an image of the application instances.

39. The system of claim 38, wherein:

the communication tools include e-mail configured to include a link to the addressable portions of the image of the application instances.

40. The system of claim 38, wherein:

the communications tools include tools to correspond notes and rules to addressable portions of the image of the application instances.

41. The system of claim 2, further comprising:

a process configured to process an image of the application instances to provide a view of the application enterprise configured to a particular user.

42. The system of claim 41, wherein:

the process configured to process the image of the application instances to provide a view of the application enterprise includes processing to control access to particular portions of the image of the application instances based on predetermined functional constraints.

43. The system of claim 42, wherein:

the functional constraints are based on characteristics associated with a particular user.

44. The system of claim 42, wherein:

the functional constraints are based on characteristics associated with a particular function.

45. The system of claim 2, further comprising:

an integrated process configured to process the image of the application instances according to a standard interface.

46. The system of claim 45, wherein:

the integrated process is configured to provide data to the image of the application instances.

47. The system of claim 45, wherein:

the integrated process is configured to accept data from the image of the application instances.

48. The system of claim 42, wherein:

the processing to control access to particular portions of the image of the application instances is driven by data in an enterprise directory.

49. The system of claim 2, further comprising:

a process for accomplishing transactions across the application enterprise.

50. The system of claim 49, wherein:

the process for accomplishing transactions includes a process to accomplish a replication operation.

51. The system of claim 50, wherein:

the replication operation is based on an image of the application instances.

52. The system of claim 51, wherein:

the replication operation being based on an image of the application instances includes the replication operation being based on differences determined as a result of a comparison between at least two images of the application instances.

53. The system of claim 49, wherein:

the process for accomplishing transactions includes a process to accomplish a repair operation.

54. The system of claim 53, wherein:

the repair operation is based on an image of the application instances.

55. The system of claim 54, wherein:

the repair operation being based on an image of the application instances includes the repair operation being based on non-compliance to rules associated with the application blueprints.

56. The system of claim 49, wherein:

the process for accomplishing transactions includes a process to accomplish an installation operation.

57. The system of claim 56, wherein:

the installation operation is based on the application blueprints.

58. The system of claim 49, wherein:

the process for accomplishing transactions includes a process to change parameters associated with the applications.

59. The system of claim 58, wherein:

the process to change parameters associated with the applications is an update transaction.

60. The system of claim 59, wherein:

the update transaction operates based on a patch blueprint.

61. The system of claim 49, wherein:

the process to change parameters associated with applications is a tuning transaction.

62. The system of claim 61, wherein:

the tuning transaction operations to change configuration parameters only.