System and method for managing multiple sever node clusters using a hierarchical configuration data structure

• US 8,601,099 B1
• Filed: 12/30/2003
• Issued: 12/03/2013
• Est. Priority Date: 12/30/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Zenz, Ingo, Semerdzhiev, Krasimir, Quang, Pham
• Primary Examiner(s): Lin, Kenny
• Assistant Examiner(s): Sciacca, Scott M
• Application Number:
  US10/750,043
• Time in Patent Office: 3,626 Days
• Field of Search: 707/8, 707/10, 707/103.R, 707/201, 709223-225, 709/228, 709/248
• US Class Current: 709/220
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]

Abstract

A system and method are described for managing a plurality of sever nodes. In one embodiment, the sever nodes are organized into groups referred to as “instances.” Each instance includes a group of redundant sever nodes and a dispatcher for distributing service requests to each of the sever nodes. In addition, a central message passing architecture is defined which allows the various instances to communicate with one another. In one embodiment, a hierarchical configuration data object is stored within a database and is centrally accessible by all of the servers from all of the instances. The hierarchical configuration data object organizes configuration data and binary data in a logical hierarchy which simplifies sever node management in an enterprise network.

Claims

1. A system comprising:

a plurality of server nodes communicatively coupled on an enterprise network, the plurality of server nodes comprising one or more application server instances, each application server instance comprising a dispatcher and a group of server nodes, the dispatcher executable by a processor to distribute service requests from clients to each of the server nodes based on loads of each of the server nodes, the server nodes configured to serve applications over the enterprise network to a plurality of clients; and

a hierarchical data object to store an indication of configuration data and binaries associated with each of the server nodes, the hierarchical data object comprising a global subhierarchy and a non-global sub-hierarchy, the global sub-hierarchy containing an indication of configuration data and binaries associated with all of the server nodes and the non-global subhierarchy containing an indication of configuration data and binaries associated with specified individual server nodes, the global sub-hierarchy including a dispatchers sub-hierarchy containing binaries and configuration data associated with each of the dispatchers and a servers sub-hierarchy containing binaries and configuration data associated with each of the servers;

wherein one or more of the server nodes is further configured to determine whether to invalidate a particular set of configuration data modified within a cache of another server node based on a location of the configuration data within the global subhierarchy.

2. The system as in claim 1 further comprising a central database for storing the hierarchical data object, configuration data and binaries.

3. The system as in claim 1 wherein the global sub-hierarchy includes a bootstrap sub-hierarchy containing binaries and configuration data for starting each of the server nodes.

4. The system as in claim 1 wherein the non-global sub-hierarchy includes an instance sub-hierarchy for each application server instance.

5. The system as in claim 4 wherein each instance sub-hierarchy includes an instance globals sub-hierarchy containing binaries and/or configuration data associated with each dispatcher and server within the respective instance.

6. The system as in claim 5 wherein each instance sub-hierarchy includes an individual servers sub-hierarchy containing binaries and/or configuration data associated with each individual dispatcher and server within the respective instance.

7. A method comprising:

storing binaries and configuration data associated with a plurality of sever nodes within a hierarchical data object, the hierarchical data object to store a representation of configuration data and binaries associated with each of the sever nodes, the hierarchical data object comprising a global sub-hierarchy and a non-global sub-hierarchy, the global sub-hierarchy containing configuration data and binaries associated with all of the sever nodes and the non-global sub-hierarchy containing configuration data and binaries associated with specified individual sever nodes, each application server instance comprising a dispatcher and a group of server nodes, the dispatcher executable by a processor to distribute service requests from clients to each of the server nodes based on loads of each of the server nodes, the server nodes configured to serve applications over the enterprise network to a plurality of clients.

8. The method as in claim 7 further comprising storing the hierarchical data object, configuration data and binaries within a central database, the central database accessible by the server nodes.

9. The method as in claim 7 wherein the global sub-hierarchy includes a bootstrap sub-hierarchy containing binaries and configuration data for starting each of the server nodes.

10. The method as in claim 7 wherein the global sub-hierarchy includes a dispatchers sub-hierarchy containing binaries and configuration data associated with each of the dispatchers and a servers sub-hierarchy containing binaries and configuration data associated with each of the servers.

11. The method as in claim 7 wherein the non-global sub-hierarchy includes an instance sub-hierarchy for each application server instance.

12. The method as in claim 11 wherein each instance sub-hierarchy includes an instance globals sub-hierarchy containing binaries and/or configuration data associated with each dispatcher and server within the respective instance.

13. The method as in claim 12 wherein each instance sub-hierarchy includes an individual servers sub-hierarchy containing binaries and/or configuration data associated with each individual dispatcher and server within the respective instance.

14. A method for updating configuration settings for a plurality of server nodes comprising:

modifying configuration data at a first server node in a group of server nodes associated with a dispatcher, the dispatcher configured to distribute service requests from clients to server nodes;

registering the modification within a hierarchical configuration data object stored within a central database, the hierarchical configuration data object to store a representation of configuration data associated with each of the server nodes and stored in a global sub-hierarchy including a dispatchers sub-hierarchy containing binaries and configuration data associated with one or more dispatchers and a servers sub-hierarchy containing binaries and configuration data associated with one or more servers;

communicating an indication of the modification to one or more other server nodes;

reading the hierarchical data object to identify the modified configuration data and determine if the configuration data stored on the other server nodes is out-of-date; and

downloading the modified configuration data from the central database to the other server nodes if the configuration data stored on the other server nodes is out-of-date.

15. The method as in claim 14 further comprising:

downloading the modified configuration data from the central database to the other server nodes if the indication of the modified configuration data is located within the global sub-hierarchy.

16. The method as in claim 14 further comprising:

if the indication of the modified configuration data is located within the non-global sub-hierarchy, then determining whether the modified configuration data is associated with all servers within a particular instance, and

if the modified configuration data is associated with all servers within a particular instance, then downloading the modified configuration data from the central database to all server nodes within the particular instance.

17. The method as in claim 14 further comprising:

acquiring a lock on the configuration data prior to modifying the configuration data at the first server node.

18. The method as in claim 17 further comprising:

releasing the lock on the configuration data after the configuration data has been updated at the central database and/or at each of the server nodes.