Method, system, and article of manufacture for generating device specific requests

• US 7,587,421 B2
• Filed: 01/30/2004
• Issued: 09/08/2009
• Est. Priority Date: 01/30/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schaefer, Thorsten, Jancke, Karsten, Hwang, Hai-Yann, Wang, Xin, Zhou, Cindy, Bonilla, Sergio P.
• Primary Examiner(s): Alam; Hosain T
• Assistant Examiner(s): HARPER, ELIYAH STONE
• Application Number:
  US10/769,684
• Publication Number:
  US 20050171953A1
• Time in Patent Office: 2,048 Days
• Field of Search: 707/104.1, 707/100, 707/10, 707/1, 707/5, 707/3
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

Provided are a method, system and article of manufacture for managing devices, wherein in certain embodiments a request implemented via at least one device independent class is received. A class hierarchy database is traversed to determine at least one device specific class that corresponds to the at least one device independent class, wherein the class hierarchy database stores a class hierarchy and associations between classes. The received request is modified, wherein in the modified request the least one device independent class has been translated to the at least one device specific class.

Claims

1. A method for managing devices, the method comprising:

receiving a request implemented via at least one device independent class;

traversing a class hierarchy database to determine at least one device specific class that corresponds to the at least one device independent class, wherein the class hierarchy database stores a class hierarchy and associations between classes;

modifying the received request, wherein in the modified request the least one device independent class has been translated to the at least one device specific class;

generating a device specific request in a device specific language; and

sending the device specific request in the device specific language to a managed device, wherein

(i) in the class hierarchy database, a first base class at a higher level in the class hierarchy is connected to a second base class and a third base class that are at a lower level in the class hierarchy, wherein the second and third base classes are connected via a base association;

(ii) in the class hierarchy database, the second base class is connected to a first specific class that corresponds to the first base class, the third base class is connected to a second specific class that corresponds to the second base class, wherein the first specific class and the second specific class are connected by a specific association;

(iii) in response to a request for specific association instances based on providing a source class corresponding to the second base class and a requested class corresponding to the third base class, deriving one class supported by the managed device via the specific association.

2. The method of claim 1, further comprising:

mapping at least one device independent class attribute to at least one device specific class attribute in the modified request;

mapping at least one device independent property to at least one device specific property in the modified request;

generating the device specific request from the modified request, in response to mapping the at least one device independent class attribute and the at least one device independent property; and

sending the device specific request to the managed device, wherein a proxy couples a plurality of hosts to a plurality of managed devices that includes the managed device.

3. The method of claim 1, further comprising:

further modifying the received request to include at least one association between device specific classes in the class hierarchy.

4. The method of claim 1, wherein the received request indicates the source class and the requested class, the method further comprising:

determining one specific association between a first device specific class that corresponds to the source class and a second device specific class that corresponds to the specific class, wherein the one specific association corresponds to the managed device.

5. The method of claim 1, wherein the source class represents storage pools and the requested class represents storage volumes corresponding to a storage pool.

6. The method of claim 1, wherein the received request indicates the source class and the base association, the method further comprising:

determining a first device specific class from the class hierarchy database, wherein the first device specific class has one specific association with a second device specific class that corresponds to the indicated source class, and wherein the one specific association corresponds to the base association.

7. The method of claim 1, wherein the request is received from a Common Information Model application, and wherein the at least one device independent class is specified by a Common Information Model schema.

8. The method of claim 1, wherein the request comprises a command that is part of an object oriented management schema for managing non-homogeneous devices in a network environment.

9. The method of claim 8, wherein the management schema comprises the Common Information Model.

10. The method of claim 1, wherein the managed device is coupled to a proxy, wherein the proxy is a computational device, and wherein the receiving, the traversing, the modifying and the generating are performed by the proxy.

11. The method of claim 10,

wherein the request is received at the proxy from a Common Information Model (CIM) application, and wherein the request is implemented via CIM classes;

and

wherein the traversing of the class hierarchy database is performed by a traversal application in a CIM Object Manager (CIMOM) of the proxy to determine all specific subclasses of a CIM superclass that has a specific class corresponding to the managed device.

12. A computer readable storage medium, wherein code stored in the computer readable storage medium when executed by a processor causes operations, the operations comprising:

receiving a request implemented via at least one device independent class;

traversing a class hierarchy database to determine at least one device specific class that corresponds to the at least one device independent class, wherein the class hierarchy database stores a class hierarchy and associations between classes;

modifying the received request, wherein in the modified request the least one device independent class has been translated to the at least one device specific class;

generating a device specific request in a device specific language; and

sending the device specific request in the device specific language to a managed device, wherein

(i) in the class hierarchy database, a first base class at a higher level in the class hierarchy is connected to a second base class and a third base class that are at a lower level in the class hierarchy, wherein the second and third base classes are connected via a base association;

(ii) in the class hierarchy database, the second base class is connected to a first specific class that corresponds to the first base class, the third base class is connected to a second specific class that corresponds to the second base class, wherein the first specific class and the second specific class are connected by a specific association;

(iii) in response to a request for specific association instances based on providing a source class corresponding to the second base class and a requested class corresponding to the third base class, deriving one class supported by the managed device via the specific association.

13. The computer readable storage medium of claim 12, the operations further comprising:

mapping at least one device independent class attribute to at least one device specific class attribute in the modified request;

mapping at least one device independent property to at least one device specific property in the modified request;

generating the device specific request from the modified request, in response to mapping the at least one device independent class attribute and the at least one device independent property; and

sending the device specific request to the managed device, wherein a proxy couples a plurality of hosts to a plurality of managed devices that includes the managed device.

14. The computer readable storage medium of claim 12, the operations further comprising:

further modifying the received request to include at least one association between device specific classes in the class hierarchy.

15. The computer readable storage medium of claim 12, wherein the received request indicates the source class and the requested class, the operations further comprising:

determining one specific association between a first device specific class that corresponds to the source class and a second device specific class that corresponds to the specific class, wherein the one specific association corresponds to the managed device.

16. The computer readable storage medium of claim 12, wherein the source class represents storage pools and the requested class represents storage volumes corresponding to a storage pool.

17. The computer readable storage medium of claim 12, wherein the received request indicates the source class and the base association, the operations further comprising:

determining a first device specific class from the class hierarchy database, wherein the first device specific class has one specific association with a second device specific class that corresponds to the indicated source class, and wherein the one specific association corresponds to the base association.

18. The computer readable storage medium of claim 12, wherein the request is received from a Common Information Model application, and wherein the at least one device independent class is specified by a Common Information Model schema.

19. The computer readable storage medium of claim 12, wherein the request comprises a command that is part of an object oriented management schema for managing non-homogeneous devices in a network environment.

20. The computer readable storage medium of claim 19, wherein the management schema comprises the Common Information Model.

21. The computer readable storage medium of claim 12, wherein the managed device is coupled to a proxy, wherein the proxy is a computational device, and wherein the receiving, the traversing, the modifying and the generating are performed by the proxy.

22. The computer readable storage medium of claim 21,

wherein the request is received at the proxy from a Common Information Model (CIM) application, and wherein the request is implemented via CIM classes;

and

wherein the traversing of the class hierarchy database is performed by a traversal application in a CIM Object Manager (CIMOM) of the proxy to determine all specific subclasses of a CIM superclass that has a specific class corresponding to the managed device.

23. A system for managing devices, the system comprising:

a memory;

a processor coupled to the memory, wherein the processor performs operations, the operations comprising;

receiving a request implemented via at least one device independent class;

traversing a class hierarchy database to determine at least one device specific class that corresponds to the at least one device independent class, wherein the class hierarchy database stores a class hierarchy and associations between classes;

modifying the received request, wherein in the modified request the least one device independent class has been translated to the at least one device specific class;

generating a device specific request in a device specific language; and

sending the device specific request in the device specific language to a managed device, wherein

(i) in the class hierarchy database, a first base class at a higher level in the class hierarchy is connected to a second base class and a third base class that are at a lower level in the class hierarchy, wherein the second and third base classes are connected via a base association;

(ii) in the class hierarchy database, the second base class is connected to a first specific class that corresponds to the first base class, the third base class is connected to a second specific class that corresponds to the second base class, wherein the first specific class and the second specific class are connected by a specific association;

(iii) in response to a request for specific association instances based on providing a source class corresponding to the second base class and a requested class corresponding to the third base class, deriving one class supported by the managed device via the specific association.

24. The system of claim 23, the operations further comprising:

mapping at least one device independent class attribute to at least one device specific class attribute in the modified request;

mapping at least one device independent property to at least one device specific property in the modified request;

generating the device specific request from the modified request, in response to mapping the at least one device independent class attribute and the at least one device independent property; and

sending the device specific request to the managed device, wherein a proxy couples a plurality of hosts to a plurality of managed devices that includes the managed device.

25. The system of claim 23, the operations further comprising:

further modifying the received request to include at least one association between device specific classes in the class hierarchy.

26. The system of claim 23, wherein the received request indicates the source class and the requested class, the operations further comprising:

determining one specific association between a first device specific class that corresponds to the source class and a second device specific class that corresponds to the specific class, wherein the one specific association corresponds to the managed device.

27. The system of claim 23, wherein the source class represents storage pools and the requested class represents storage volumes corresponding to a storage pool.

28. The system of claim 23, wherein the received request indicates the source class and the base association, the operations further comprising:

determining a first device specific class from the class hierarchy database, wherein the first device specific class has one specific association with a second device specific class that corresponds to the indicated source class, and wherein the one specific association corresponds to the base association.

29. The system of claim 23, wherein the request is received from a Common Information Model application, and wherein the at least one device independent class is specified by a Common Information Model schema.

30. The system of claim 23, wherein the request comprises a command that is part of an object oriented management schema for managing non-homogeneous devices in a network environment.

31. The system of claim 30, wherein the management schema comprises the Common Information Model.

32. The system of claim 23, wherein the managed device is coupled to a proxy, wherein the proxy is a computational device, and wherein the receiving, the traversing, the modifying and the generating are performed by the proxy.

33. The system of claim 32,

wherein the request is received at the proxy from a Common Information Model (CIM) application, and wherein the request is implemented via CIM classes;

and

wherein the traversing of the class hierarchy database is performed by a traversal application in a CIM Object Manager (CIMOM) of the proxy to determine all specific subclasses of a CIM superclass that has a specific class corresponding to the managed device.