Browse Prior Art Database

Technique for providing a single CIMOM Image

IP.com Disclosure Number: IPCOM000022538D
Original Publication Date: 2004-Mar-19
Included in the Prior Art Database: 2004-Mar-19
Document File: 2 page(s) / 26K

Publishing Venue

IBM

Abstract

Use of the Common Information Model (CIM) can be costly in the context of systems or storage management if there are multiple, remote CIM Object Managers (CIMOMs) present, each containing many objects of interest. It can be advantageous to allow CIM client management applications the ability to access and modify the contents of any or all of these CIMOMs through any one CIMOM. Also, the repeated surveying of a CIMOM's contents in a given session, let alone across sessions, should be avoided. This describes a technique which could be used to address these issues.

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

Page 1 of 2

Technique for providing a single CIMOM Image

Disclosed is a technique for providing a single "image" of multiple CIMOMs. While other implementations exist which provide a focal point for CIM client operations, it is not known if they support CIM write operations and otherwise act completely as a CIMOM. This uses an existing open source CIMOM which is modified and which can act as a master CIMOM. In such a case, it contains the contents of the other CIMOMs and provides a central, single point of contact for CIM client read operations. CIM client write operations are redirected from the master to the target CIMOMs and subsequently reflected in the master upon completion. It is also possible to use said modified CIMOM in a scenario where all of the CIMOMs are instances of the modified CIMOM in which case any of them will allow access to the contents of all.

It is felt that use of J2EE* provides a convenient, flexible and powerful base for a proof of concept of this scheme. It is implemented using the open source CIMOM provided by the Storage Networking Industry Association (SNIA). This CIMOM has been modified to use Enterprise JavaBeans*(EJB*s) within Websphere**. Entity beans are used to encapsulate CIM objects, object paths (names) and instances. Session beans are used to manipulate the entities. The modified CIMOM uses these beans instead of reading and writing serialized Java objects to the filesystem.

The simplest case would have all the CIMOMs be the modified one described here. In this scenario the Managed Object Format (MOFs), representing both CIM classes and instances (if any) would be compiled on any one (or each) of the CIMOMs. The class definitions and any static instances (non-provider produced) would be seen by all the modified CIMOMs. If the same CIM providers are loaded in each modified CIMOM instance (assuming the provider can contact the endpoint device(s) from each CIMOM), then a CIM client needs to contact only one of the modified CIMOMs. If the provider is loaded proximate to the EJB container, then further mods to the CIMOM would be needed, since invocation of remote providers is not currently supported.

The case where the modified CIMOM acts as a master is intended for situations where pre-existing CIMOMs are already in place, and there is no desire to change them. CIM Schema MOFs are compiled using the MOF compiler into the master. Additional code surveys and extracts CIM classes, object paths and instances from each remote CIMOM and creates entity beans for the master. As these beans are created, the originating CIMOM's information, e.g. IP address, por...