UNIVERSAL ARCHITECTURE FOR CLIENT MANAGEMENT EXTENSIONS ON MONITORING, CONTROL, AND CONFIGURATION

• US 20110099219A1
• Filed: 10/23/2009
• Published: 04/28/2011
• Est. Priority Date: 10/23/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ostler, Paul A., Chang, David Wei-Jye, Lee, Bilung
• Granted Patent: US 8,775,498 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/5011 Pool
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• 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

Abstract

Provided are techniques for, under control of an agent: receiving a request from a first database client to access a service from a set of services, wherein the agent is associated with the service; receiving a request from a second database client to access the service, wherein the agent is shared by the first database client and the second database client; combining information from the first database client and the second database client; and sending the combined information to the service using a single physical connection in a client-side Client Management Extension (CMX) connection, wherein the first database client and the second database client share the single physical connection.

Claims

1. A method, comprising:

under control of an agent running on a client computer including a processor;

receiving a request from a first database client to access a service from a set of services, wherein the agent is associated with the service;

receiving a request from a second database client to access the service, wherein the agent is shared by the first database client and the second database client;

combining information from the first database client and the second database client; and

sending the combined information to the service using a single physical connection in a client-side Client Management Extension (CMX) connection, wherein the first database client and the second database client share the single physical connection.

2. The method of claim 1, further comprising:

under control of the client-side CMX connection including a client-side core processor, one or more client-side management processors, and a client-side message queue;

using a generic protocol that is used for multiple management functionalities for communication with a server-side CMX connection.

3. The method of claim 2, wherein the management functionalities include monitoring, control, and configuration functionalities.

4. The method of claim 2, further comprising:

under control of the client-side CMX connection,

negotiating a version of a client-side management processor and a corresponding server-side management processor, wherein the client-side management processor and the server-side management processor correspond to the service, and wherein the negotiation includes sending a request with a client-side management processor version as an argument using the client-side core processor to the sever-side CMX connection; and

receiving from the server-side CMX connection a minimum between an actual version of the corresponding server-side management processor and the requested version of the client-side management processor, wherein the client-side management processor and the server-side management processor are marked as registered.

5. The method of claim 2, further comprising:

under control of the server-side CMX connection,

in response to receiving a synchronous message from the client-side CMX connection,

forwarding the synchronous message to a management processor of the server-side CMX connection, wherein the management processor generates a reply; and

returning the reply to the client-side CMX connection; and

in response to receiving an asynchronous message from the client-side CMX connection, forwarding the synchronous message to a management processor of the server-side CMX connection.

6. The method of claim 2, further comprising:

under control of the client-side CMX connection,

in response to receiving a synchronous message from the server-side CMX connection;

forwarding the synchronous message to a management processor of the client-side CMX connection, wherein the management processor generates a reply; and

returning the reply to the server-side CMX connection; and

in response to receiving an asynchronous message from the server-side CMX connection, forwarding the asynchronous message to a management processor of the client-side CMX connection.

7. The method of claim 2, wherein the client-side message queue accumulates and combines information from multiple agents.

8. The method of claim 1, wherein the agent accumulates and combines information from multiple agents.

9. A computer program product comprising a computer readable storage medium storing computer readable program code that, when run on a processor of a client computer, causes the computer to:

under control of an agent;

receive a request from a first database client to access a service from a set of services, wherein the agent is associated with the service;

receive a request from a second database client to access the service, wherein the agent is shared by the first database client and the second database client;

combine information from the first database client and the second database client; and

send the combined information to the service using a single physical connection in a client-side Client Management Extension (CMX) connection, wherein the first database client and the second database client share the single physical connection.

10. The computer program product of claim 9, wherein the computer readable program code, when run on the processor, causes the computer to:

under control of the client-side CMX connection including a client-side core processor, one or more client-side management processors, and a client-side message queue;

use a generic protocol that is used for multiple management functionalities for communication with a server-side CMX connection.

11. The computer program product of claim 10, wherein the management functionalities include monitoring, control, and configuration functionalities.

12. The computer program product of claim 10, wherein the computer readable program code, when run on the processor, causes the computer to:

under control of the client-side CMX connection,

negotiate a version of a client-side management processor and a corresponding server-side management processor, wherein the client-side management processor and the server-side management processor correspond to the service, and wherein the negotiation includes sending a request with a client-side management processor version as an argument using the client-side core processor to the sever-side CMX connection; and

receive from the server-side CMX connection a minimum between an actual version of the corresponding server-side management processor and the requested version of the client-side management processor, wherein the client-side management processor and the server-side management processor are marked as registered.

13. The computer program product of claim 10, wherein the computer readable program code, when run on the processor, causes the computer to:

under control of the server-side CMX connection,

in response to receiving a synchronous message from the client-side CMX connection,

forward the synchronous message to a management processor of the server-side CMX connection, wherein the management processor generates a reply; and

return the reply to the client-side CMX connection; and

in response to receiving an asynchronous message from the client-side CMX connection, forward the synchronous message to a management processor of the server-side CMX connection.

14. The computer program product of claim 10, wherein the computer readable program code, when run on the processor, causes the computer to:

under control of the client-side CMX connection,

in response to receiving a synchronous message from the server-side CMX connection;

forward the synchronous message to a management processor of the client-side CMX connection, wherein the management processor generates a reply; and

return the reply to the server-side CMX connection; and

in response to receiving an asynchronous message from the server-side CMX connection, forward the asynchronous message to a management processor of the client-side CMX connection.

15. The computer program product of claim 10, wherein the client-side message queue accumulates and combines information from multiple agents.

16. The computer program product of claim 9, wherein the agent accumulates and combines information from multiple agents.

17. A client computer, comprising:

a processor;

memory; and

circuitry implementing an agent running on the client computer, wherein the circuitry performs operations, the operations comprising;

receiving a request from a first database client to access a service from a set of services, wherein the agent is associated with the service;

receiving a request from a second database client to access the service, wherein the agent is shared by the first database client and the second database client;

combining information from the first database client and the second database client; and

sending the combined information to the service using a single physical connection in a client-side Client Management Extension (CMX) connection, wherein the first database client and the second database client share the single physical connection.

18. The client computer of claim 17, wherein the circuitry performs operations, the operations comprising:

under control of the client-side CMX connection including a client-side core processor, one or more client-side management processors, and a client-side message queue;

using a generic protocol that is used for multiple management functionalities for communication with a server-side CMX connection.

19. The client computer of claim 18, wherein the management functionalities include monitoring, control, and configuration functionalities.

20. The client computer of claim 18, wherein the circuitry performs operations, the operations comprising:

under control of the client-side CMX connection,

negotiating a version of a client-side management processor and a corresponding server-side management processor, wherein the client-side management processor and the server-side management processor correspond to the service, and wherein the negotiation includes sending a request with a client-side management processor version as an argument using the client-side core processor to the sever-side CMX connection; and

receiving from the server-side CMX connection a minimum between an actual version of the corresponding server-side management processor and the requested version of the client-side management processor, wherein the client-side management processor and the server-side management processor are marked as registered.

21. The client computer of claim 18, wherein the circuitry performs operations, the operations comprising:

under control of the server-side CMX connection,

in response to receiving a synchronous message from the client-side CMX connection,

forwarding the synchronous message to a management processor of the server-side CMX connection, wherein the management processor generates a reply; and

returning the reply to the client-side CMX connection; and

in response to receiving an asynchronous message from the client-side CMX connection, forwarding the synchronous message to a management processor of the server-side CMX connection.

22. The client computer of claim 18, wherein the circuitry performs operations, the operations comprising:

under control of the client-side CMX connection,

in response to receiving a synchronous message from the server-side CMX connection;

forwarding the synchronous message to a management processor of the client-side CMX connection, wherein the management processor generates a reply; and

returning the reply to the server-side CMX connection; and

in response to receiving an asynchronous message from the server-side CMX connection, forwarding the asynchronous message to a management processor of the client-side CMX connection.

23. The client computer of claim 18, wherein the client-side message queue accumulates and combines information from multiple agents.

24. The client computer of claim 17, wherein the agent accumulates and combines information from multiple agents.

25. A system comprising:

a client-side Client Management Extension (CMX) connection, wherein the client-side CMX connection includes a message queue, a core processor, management processors, an outgoing message reader thread, an incoming message reader thread, and a physical connection;

a server-side CMX connection coupled to the client-side CMX connection, wherein the server-side CMX connection includes a message queue, a core processor, management processors, an outgoing message reader thread, an incoming message reader thread, and a physical connection; and

wherein the client-side CMX connection and the server-side CMX connection communicate with each other using a generic protocol that is used for multiple management functionalities.