Cluster architecture communications

• US 20050270973A1
• Filed: 06/07/2004
• Published: 12/08/2005
• Est. Priority Date: 06/07/2004
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Raev, Kaloyan V., Mueller, Jochen, Stanev, Georgi, Petev, Petio G., Minov, Jasen O.
• Application Number:
  US10/863,123
• Publication Number:
  US 20050270973A1
• Time in Patent Office: Days
• US Class Current: 370/218
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• 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 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168

Abstract

A cluster includes a plurality of application server instances, a central services instance that includes a message server, and a database. The application server instances each include a dispatcher, a plurality of redundant server nodes, and a socket connection between the dispatcher and each of the server nodes for handling communications relating to processing a client request. A separate socket connection between the message server and each of the server nodes is provided for handling internal communications between the server nodes. Additionally, a third socket connection may be established directly between server nodes.

Claims

1. A system comprising:

a message server;

a plurality of application server instances, each application server instance having a dispatcher, a plurality of redundant server nodes, and a socket connection between the dispatcher and each of the server nodes for handling communications relating to processing a client request, and

a separate socket connection between the message server and each of the server nodes for handling internal communications between the server nodes.

2. The system of claim 1, further comprising the separate socket connection between the message server and each of the dispatchers for handling internal communications between the dispatchers and the server nodes.

3. The system of claim 1, wherein internal communications between the server nodes includes communications indicating one or more of:

a change in state in the system, an addition of a server node to the system, a loss or removal of a server node from the system, a change in state of a server node, a change in state of services provided by a server node, and a change in state of a server node to communicate with other server nodes in the system.

4. The system of claim 3, wherein internal communications between the server nodes includes communications between server nodes in separate application server instances.

5. The system of claim 1, wherein each application server instance runs on a physical server.

6. The system of claim 4, wherein multiple application server instances run on the same physical server.

7. The system of claim 2, wherein the dispatcher provides for opening a new socket connection between the dispatcher and a respective server node if the socket connection between the dispatcher and the server node fails, unless the message server provides for sending an internal communications message over the separate socket connection between the message server and the dispatcher that a new socket connection cannot be opened to the server node.

8. The system of claim 1, further comprising a third socket connection directly between two of the server nodes.

9. The system of claim 8, wherein the third socket connection directly between two of the server nodes provides for handling internal communications between the two server nodes instead of via the separate socket connections between each of the two server nodes and the message server.

10. The system of claim 9, wherein the third socket connection provides for handling internal communications between the two server nodes if such communication is or would become prohibited via the separate socket connections between each of the two server nodes and the message server.

11. The system of claim 10, wherein such communication is or would become prohibited depending on a data transfer rate threshold.

12. The system of claim 11, wherein the third socket connection is established when the data transfer rate would be exceeded by such communications.

13. The system of claim 12, wherein the third socket connection is terminated in favor of internal communications via the separate socket connections between each of the two server nodes and the message server after the data transfer rate is no longer exceeded.

14. The system of claim 8, wherein each of the two server nodes resides in a different application server instance.

15. The system of claim 8, wherein each of the two server nodes resides in a different Java 2 Enterprise Edition (J2EE) application server instance.

16. The system of claim 1, wherein the system provides for one of the server nodes to transmit an internal communications message to the message server via the separate socket connection between the server node and the message server, and the message server to replicate and transmit the message to the other server nodes via the respective separate socket connections between the message server and the other server nodes.

17. The system of claim 16, wherein the message server provides for sending an acknowledgement message over the separate socket connection to a server node in response to a message received from the server node over the separate socket connection.

18. The system of claim 17, wherein upon failure of the message server to send the acknowledgement message to the server node, the server node provides for resending the message.

19. The system of claim 18, wherein the server node provides for resending the message after receiving an indication from the message server that the message server can receive messages.

20. A article of manufacture, comprising:

an electronically accessible medium providing instructions that, when executed by an apparatus, cause the apparatus to implement;

a message server;

a plurality of application server instances, each application server instance having a dispatcher, a plurality of redundant server nodes, and a socket connection between the dispatcher and each of the server nodes for handling communications relating to processing a client request, and

a separate socket connection between the message server and each of the server nodes for handling internal communications between the server nodes.

21. The article of manufacture of claim 20, wherein the electronically accessible medium further comprises instructions that, when executed by the apparatus, cause the apparatus to implement a separate socket connection between the message server and each of the dispatchers for handling internal communications between the dispatchers and the server nodes.

22. The article of manufacture of claim 20, wherein the electronically accessible medium comprises instructions that, when executed by an apparatus, cause the apparatus to implement internal communications between server nodes in separate application server instances.

23. The article of manufacture of claim 21, wherein the electronically accessible medium comprises instructions that, when executed by an apparatus, cause the dispatcher to open a new socket connection between the dispatcher and a respective server node if the socket connection between the dispatcher and the server node fails, unless the message server provides for sending an internal communications message over the separate socket connection between the message server and the dispatcher that a new socket connection cannot be opened to the server node.

24. The article of manufacture of claim 20, wherein the electronically accessible medium comprises instructions that, when executed by an apparatus, cause the apparatus to implement a third socket connection directly between two of the server nodes.

25. The system of claim 24, wherein the third socket connection directly between two of the server nodes provides for handling internal communications between the two server nodes instead of via the separate socket connections between each of the two server nodes and the message server.

26. The system of claim 25, wherein the third socket connection provides for handling internal communications between the two server nodes if such communication is or would become prohibited via the separate socket connections between each of the two server nodes and the message server.

27. The article of manufacture of claim 20, wherein the electronically accessible medium comprises instructions that, when executed by an apparatus, cause one of the server nodes to transmit an internal communications message to the message server via the separate socket connection between the server node and the message server, and the message server to replicate and transmit the message to the other server nodes via the respective separate socket connections between the message server and the other server nodes.