[an error occurred while processing this directive]
[an error occurred while processing this directive] [an error occurred while processing this directive]

Pegasus CIM Object Broker Documentation
[an error occurred while processing this directive]


[an error occurred while processing this directive]

 

Contents

o Introduction
o Objectives
o Overview
o Credits
o Pegasus Architecture
   o Design Goals
   o The Broker
   o Pegasus Providers.
   o Extension Services
   o Pegasus Clients.
   o Functional Flow
o Pegasus Components
   o Component Descriptions
   o Pegasus Directory Structure
o Pegasus Utilization
   o Pegasus Availability
   o Pegasus Installation
   o Pegasus Operation
   o Pegasus CIM Clients
   o Pegasus Providers
   o Pegasus MOF Compiler
o Programming Pegasus
   o CIM Objects in Pegasus
   o CIM Object Table
   o Class Definitions
o Pegasus Interfaces
   o CIM Operations over HTTP
   o Pegasus Client Interfaces
   o Pegasus Provider Interfaces
   o Pegasus Service Extension Interfaces
   o Repository Interfaces
o Writing Providers.
o Glossary
o Pegasus Code Examples
   o Client Examples
   o Client Coding Examples
   o Provider Coding Examples
o Document References
o Pegausus FAQ
o

CIM Operations over HTTP

The core of the Pegasus external interface is the WBEM Operations (Formally known as CIM Operations over HTTP in the DMTF specificaion). Pegasus uses the basic WBEM operations as the basis for all of the interfaces.

Pegasus defines these interfaces in exactly the same manner as they are defined in the DMTF specification (CIM Operations over HTTP)

Thus, Pegasus implements a Class named CIMOperations. Within that class, each of the WBEM HTTP operations is implemented as a method.

For example, the WBEM operation GetClass has its direct equivalent in Pegasus CIMOperations, the getClass method. Further, Pegasus maintains the same parameters as are defined in the DMTF document.

The CIMOperations class is the heart of all of the CIM interfaces including the Client interface, the Provider interface, the repository interface, and the services interface. Each of these interfaces derives from CIMOperations adding methods as required to complete that particular interface.

This section defines these interfaces in the reference CIMOperations below:

Alphabetic index Hierarchy of classes
[an error occurred while processing this directive]