Browse Prior Art Database

CIMOM Uninformed Management via GUI and Repository.

IP.com Disclosure Number: IPCOM000019440D
Original Publication Date: 2003-Sep-12
Included in the Prior Art Database: 2003-Sep-12
Document File: 3 page(s) / 53K

Publishing Venue

IBM

Abstract

Provide a standard method for accessing Common Information Model (CIM) agents; including determination of which access parameters are needed, storage and reuse these parameters, CIM Agent accessibility verification, and use of a repository for future accesses.

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

Page 1 of 3

CIMOM Uninformed Management via GUI and Repository.

   A program is disclosed that provides a standard method for accessing CIM agents, and for managing and verifying those access parameters.

Background information

This invention pertains generally to software that provisions computer resources. The invention applies specifically to a storage resource manager (SRM) software application. SRM software facilitates management of storage resources throughout an enterprise by centrally monitoring storage assets and utilization, reporting events, and allocating storage based on predefined policies. One possible SRM function is automatic, policy-based provisioning of storage resources for host computer systems in the enterprise to satisfy criteria such as capacity or free space for each machine. Provisioning needs to create storage (LUNs) when additional spaces is needed. LUN creation and assignment have traditionally been accomplished manually using Subsystem Vendor Unique GUIs or Commands. A new interface called the Common Information Model / Object Manager (CIMOM) has been created for doing Industry Standard Programmatical Calls to a Storage Subsystem to cause LUN Creation and Assignment. There can be multiple CIMOMs in a Storage Environment. Each CIMOM can manage one or more Storage Subsystems. For security reasons, some CIMOMs may have IDs, Passwords, and possibly SSL Certificates associated with accessing them.

Problem solved

When accessing these CIMOMs, there is no standard way to determine which access parameters are needed, or any way to keep track and reuse these parameters for future accesses.

Each CIMOM has data related to accessing it, each CIMOM manages a specific device or set of devices. A considerable effort is needed to manually manage the access parameters for large numbers of CIMOMs used by a client application.

The CIM Client typically must know, prior to connecting to the CIM Agent, of the http version and authentication level to use in order to make a connection. Without the proper http version and authentication level, the first request from a client to a se...