System and method for interfacing with existing system management products or software solutions

• US 7,346,647 B2
• Filed: 04/15/2003
• Issued: 03/18/2008
• Est. Priority Date: 04/19/2002
• Status: Active Grant

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Bodine, Gregory L., Kane, John P., Anderson, Andrew J.
• Primary Examiner(s): Vaughn; William
• Assistant Examiner(s): SHINGLES, KRISTIE D
• Application Number:
  US10/417,028
• Publication Number:
  US 20030200319A1
• Time in Patent Office: 1,799 Days
• Field of Search: 709/200, 709/223, 709/217, 709/227, 709/201, 709/202, 709/205, 709/206
• US Class Current: 709/201
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A system and method for providing a consistent interface with different system products or software solutions includes one or more system units or machines wherein the different system products or software solutions (instruments) reside. A service request can be made to an instrument gateway associated with a particular system unit or machine that includes an instrument that can service the request. The instrument gateway selects an instrument sponsor associated with that particular instrument to invoke the requested service from that particular instrument.

Claims

1. A computer-implemented method for providing a consistent interface between a client application and a plurality of software instruments, the method comprising the steps of:

receiving a generic request message from the client application at a particular instrument gateway, wherein the particular instrument gateway is coupled between the client application and the plurality of software instruments, wherein the particular instrument gateway is associated with the plurality of software instruments, wherein the request message includes a message payload corresponding to a transaction or a service request to be processed by a particular one of the plurality of software instruments;

sending from the particular instrument gateway to each of a plurality of instrument sponsors a request for a description of the instrument sponsor;

determining, by the particular instrument gateway, which one of the plurality of instrument sponsors is associated with the particular one of the plurality of software instruments, wherein the determining is based, at least in part, on the request message from the client application and the descriptions of the instrument sponsors, wherein each of the plurality of instrument sponsors provides an interface to at least one of the plurality of software instruments;

invoking, by the particular instrument gateway, the determined one of the plurality of instrument sponsors thereby exposing an interface to the particular one of the plurality of software instruments;

invoking, by the determined one of the plurality of instrument sponsors, the particular one of the plurality of software instruments;

providing the message payload to the particular one of the plurality of software instruments through the exposed interface thereby allowing the particular one of the plurality of software instruments to process the message payload; and

communicating, by the particular instrument gateway to the client application, a result provided by the particular one of the plurality of software instruments associated with the processed the message payload.

2. The method of claim 1, further comprising identifying, by the particular instrument gateway, the plurality of software instruments associated therewith upon the particular instrument gateway receiving the request message.

3. The method of claim 1, wherein the request message comprises an XML message including the message payload and an identifier that identifies the particular one of the plurality of software instruments.

4. The method of claim 1, wherein the determined one of the plurality of instrument sponsors serves as a knowledge provider.

5. The method of claim 1, wherein the client application is compatible with the particular one of the plurality of software instruments through the particular instrument gateway and the determined one of the plurality of instrument sponsors.

6. The method of claim 1, wherein the determined one of the plurality of instrument sponsors comprises an in-process application.

7. The method of claim 1, wherein the determined one of the plurality of instrument sponsors comprises an out-of-process application.

8. The method of claim 1, wherein the plurality of software instruments comprise a storage software instrument on a first platform and a security software instrument on a second platform.

9. A computer-implemented system that provides a consistent interface between a client application and a plurality of software instruments, the system comprising:

an instrument gateway that receives a generic request message from the client application, wherein the instrument gateway is coupled between the client application and the plurality of software instruments, wherein the instrument gateway is associated with the plurality of software instruments, wherein the request message includes a message payload corresponding to a transaction or a service request to be processed by a particular one of the plurality of software instruments;

a plurality of instrument sponsors, one of which is associated with the particular one of the plurality of software instruments, wherein the instrument gateway sends to each of the plurality of instrument sponsors a request for a description of the instrument sponsor and determines the one of the plurality of instrument sponsors that is associated with the particular one of the plurality of software instruments, wherein the determination is based, at least in part, on the request message from the client application and the descriptions of the instrument sponsors, wherein each of the plurality of instrument sponsors provides an interface to at least one of the plurality of software instruments;

wherein the instrument gateway invokes the determined one of the plurality of instrument sponsors thereby exposing an interface to the particular one of the plurality of software instruments;

wherein the determined one of the plurality of instrument sponsors invokes the particular one of the plurality of software instruments;

wherein the message payload is provided to the particular one of the plurality of software instruments through the exposed interface thereby allowing the particular one of the plurality of software instruments to process the message payload; and

wherein the instrument gateway communicates a result to the client application, the result provided by the particular one of the plurality of software instruments associated with the processed the message payload.

10. The system of claim 9, wherein the instrument gateway identifies the plurality of software instruments associated with the instrument gateway when the instrument gateway receives the request message.

11. The system of claim 9, wherein the request message comprises an XML message including the message payload and an identifier that identifies the particular one of the plurality of software instruments.

12. The system of claim 9, wherein the determined one of the plurality of instrument sponsors serves as a knowledge provider.

13. The system of claim 9, wherein the client application is compatible with the particular one of the plurality of software instruments through the instrument gateway and the determined one of the plurality of instrument sponsors.

14. The system of claim 9, wherein the determined one of the plurality of instrument sponsors comprises an in-process application.

15. The system of claim 9, wherein the determined one of the plurality of instrument sponsors comprises an out-of-process application.

16. The system of claim 9, wherein the plurality of software instruments comprises a storage software instrument on a first platform and a security software instrument on a second platform.

17. Software for providing a consistent interface between a client application and a plurality of software instruments, the software comprising computer executable instructions resident on computer readable media and operable to:

receive a generic request message from the client application at a particular instrument gateway, wherein the particular instrument gateway is coupled between the client application and the plurality of software instruments, wherein the particular instrument gateway is associated with the plurality of software instruments, wherein the request message includes a message payload corresponding to a transaction or a service request to be processed by a particular one of the plurality of software instruments;

send from the particular instrument gateway to each of a plurality of instrument sponsors a request for a description of the instrument sponsor;

determine, using the particular instrument gateway, which one of the plurality of instrument sponsors is associated with the particular one of the plurality of software instruments, wherein the determination is based, at least in part, on the request message from the client application and the descriptions of the instrument sponsors, wherein each of the plurality of instrument sponsors provides an interface to at least one of the plurality of software instruments;

invoke, using the particular instrument gateway, the determined one of the plurality of instrument sponsors thereby exposing an interface to the particular one of the plurality of software instruments;

invoke, using the determined one of the plurality of instrument sponsors, the particular one of the plurality of software instruments;

provide the message payload to the particular one of the plurality of software instruments through the exposed interface thereby allowing the particular one of the plurality of software instruments to process the message payload; and

communicate, using the particular instrument gateway to the client application, a result provided by the particular one of the plurality of software instruments associated with the processed the message payload.

18. The software of claim 17, wherein the computer executable instructions are further operable to identify, using the particular instrument gateway, the plurality of software instruments associated therewith upon the particular instrument gateway receiving the request message.

19. The software of claim 17, wherein the request message comprises an XML message including the message payload and an identifier that identifies the particular one of the plurality of software instruments.

20. The software of claim 17, wherein the determined one of the plurality of instrument sponsors serves as a knowledge provider.

21. The software of claim 17, the client application is compatible with the particular one of the plurality of software instruments through the particular instrument gateway and the determined one of the plurality of instrument sponsors.

22. The software of claim 17, wherein the determined one of the plurality of instrument sponsors comprises an in-process application.

23. The software of claim 17, wherein the determined one of the plurality of instrument sponsors comprises an out-of-process application.

24. The software of claim 17, wherein the plurality of software instruments comprise a storage software instrument on a first platform and a security software instrument on a second platform.