Browse Prior Art Database

Method and Appratus to use Hierarchial CIM repository for improving efficiency and reducing memory footprint. Disclosure Number: IPCOM000235879D
Publication Date: 2014-Mar-28
Document File: 4 page(s) / 57K

Publishing Venue

The Prior Art Database


Disclosed is a mechanism for reducing the memory footprint by leveraging the CIM Repository Inheritance for hierarchical namespace

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 4

Method and Appratus to use Hierarchial CIM repository for improving efficiency and reducing memory footprint.

Common Information Model(CIM) is an open standard that defines different managed elements in an IT infrastructure. It provides a object oriented representation of those managed elements and allows relationships between them irrespective of it's vendor or manufacturer. This helps IT administrators to manage multiple IT environments using the same set of CIM based applications.

Common Information Model(CIM) is designed to be object oriented, where Object Oriented Programming System (OOPS) concepts like encapsulation, inheritance, association are used widely. Just as, any object oriented Class contains properties and methods, CIM class also contains it's properties and methods. OOPs concept of namespace is also present in CIM specification, although with slightly different attributes. In OOPs there is a concept of nested namespace, where a child namespace can access all the public members present in parent namespace. But in CIM namespace, right now there is no concept of nested namespace where child can access parent properties, which is basis of this idea.

This idea will enable a child CIM namespace to access all the members present inside parent namespace. In a CIM namespace, all the information is present in the form of XML files, that gets loaded at the time of initialization of CIM server. If a CIM class wants to access any information, then that information should be present inside the namespace where the class is compiled. And if multiple CIM classes(present in different namespaces) wants to access that same information, then it has to be present in all those namespaces which multiplies the amount of space consumed, and the time to compile and load that information. But if the child namespace can access the information of parent namespace, then common information can be put inside parent namespace.

Figure 1.

Proposed solution is to have a CIM repository mechanism where child namespace can


Page 02 of 4

access members present in parent namespace i.e. to inherit information present in upper level of namespace by it's lower levels as shown in figure 1. Child namespace abc and xyz can access properties and classes of root namespace.

If we have level 0, level 1, level 2 .. level N, starting the top parent from level 0, then level 1 namespace can access level 0 namespace information and similarly, level 2 namespace can access level 1 namespace and level 0 information. And also allow the access based on level ordering, where if same class is present in level 0 and level 1 namespace, then precedence should be given to level 1 namespace so that the flow of class information is from generic upper level(level 0) to specific lower level(level 1,2 ..

The extension to this solution is to have a configurable property inside CIM server a.k.a. CIMOM(CIM object manager) that will control the namespace inheritance behavior. If certa...