Method of administering software components using asynchronous messaging in a multi-platform, multi-programming language environment

• US 20050177827A1
• Filed: 04/05/2005
• Published: 08/11/2005
• Est. Priority Date: 03/24/2000
• Status: Active Grant

• Current Assignee: Kester Lijen Fong, Sreerupa Sen
• Original Assignee: Kester Lijen Fong, Sreerupa Sen
• Inventors: Sen, Sreerupa, Fong, Kester Lijen
• Granted Patent: US 7,069,551 B2
• Time in Patent Office: Days
• US Class Current: 717/171
• CPC Class Codes: G06F 9/4492 Inheritance

Abstract

A method for performing life cycle management of business software applications and their components across a multiple-platform, multiple-language network. The method takes advantage of the inheritance properties of object-oriented programming (OOP) by developing all components of a business application from a set of base classes, thus deploying a common set of methods across all application components. These methods enable monitoring by a Central Administrator element without interdependence between any of the business application components and the Central Administrator. The Central Administrator then determines when a need to reconfigure one or more components of the business application has arisen. The Central Administrator then modifies or replaces existing components of the business application or installs entirely new components over the network without end user interaction. In one embodiment of the present invention, the Central Administrator is aided by a set of Distributed Administrators located on each virtual node server/host computer of a business application operating over a network. The business application can thus reconfigured without terminating the application'"'"'s business function in a scaleable, extensible manner without regard to platform or language.

Claims

1. A method of managing software components, said method comprising:

monitoring a plurality of software components;

sending configuration information in an area in one of the software components; and

configuring the software component based upon the configuration information.

2. The method of claim 1, wherein the plurality of software components are deployed on at least one computer platform.

3. The method of claim 1, wherein said software components are monitored by an Administrator.

4. The method of claim 1, wherein said Administrator comprises one or more distributed administration programs and a central administration program.

5. The method of claim 1, wherein said monitoring comprises receiving health status messages each containing only changes in said health status since receipt of a last health status message.

6. An apparatus for managing software components, comprising:

an Administrator configured to monitor a plurality of software components, to send configuration information in an area in one of the software components, and to configure the software component based upon the configuration information.

7. The apparatus of claim 6, wherein the plurality of software components are deployed on at least one computer platform.

8. The apparatus of claim 6, wherein the plurality of software components are deployed on a plurality of computer platforms that are geographically separated.

9. The apparatus of claim 6, wherein said Administrator comprises one or more distributed administration programs and a central administration program.

10. The apparatus of claim 6, wherein said monitoring comprises receiving health status messages each containing only changes in said health status since receipt of a last health status message.

11-20. -20. (canceled)

21. An apparatus for managing software components, the apparatus comprising:

means for monitoring a plurality of software components, for sending configuration information in an area in one of the software components, and for configuring the software component based upon the configuration information.

22. An article of manufacture, comprising:

a machine-readable medium having stored thereon instructions to;

monitor a plurality of software components;

send configuration information in an area in one of the software components; and

configure the software component based upon the configuration information.