Universal architecture for client management extensions on monitoring, control, and configuration

• US 8,775,498 B2
• Filed: 10/23/2009
• Issued: 07/08/2014
• Est. Priority Date: 10/23/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chang, David Wei-Jye, Lee, Bilung, Ostler, Paul Arnold
• Primary Examiner(s): SERRAO, RANODHI N
• Application Number:
  US12/605,205
• Publication Number:
  US 20110099219A1
• Time in Patent Office: 1,719 Days
• Field of Search: 709/202, 709/227, 707/617, 370/421
• US Class Current: 709/202
• 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 computer program product comprising a non-transitory medium comprising computer readable program code executable by a processor to:

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

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 a 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 a server-side CMX connection, wherein a generic protocol that is used for multiple management functionalities is used for communication with the server-side CMX connection;

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

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 asynchronous message to a management processor of the server-side CMX connection.

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

3. The computer program product of claim 1, wherein the computer readable program code is executable by the processor 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.

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

5. The computer program product of claim 1, wherein an agent accumulates and combines information from multiple agents.

6. 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;

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

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 a 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 a server-side CMX connection, wherein a generic protocol that is used for multiple management functionalities is used for communication with the server-side CMX connection;

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

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 asynchronous message to a management processor of the server-side CMX connection.

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

8. The client computer of claim 6, 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.

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

10. The client computer of claim 6, wherein an agent accumulates and combines information from multiple agents.