Provider Basics

The provider development task has three components:

define the resources or system parameters to be manipulated as CIM objects (the schema)
write C++ functions as described in the Provider API specifications (built as a shared library). For API information, see HP WBEM Services Software Developers Kit documentation in /opt/wbem/html directory.
inform the CIM Server how to associate the defined CIM objects with the shared library (through provider registration)

The basic steps for writing a provider are:

Determine what information to expose:
Developers need to determine what information and/or operations this provider will provide to clients. Providers can choose to allow read and/or write access to properties. Examples of properties include system time, operating system type, serial number, and so on. Providers can also support extrinsic methods to allow clients access to operations. For example, a provider can support a method that allows users to set the system time. Tips and concerns for choosing which properties and methods to expose are discussed in Chapter 3, in the section entitled “STEP 1: Define High-Level Client-Use Models”.
Determine how to get the information:
Developers need to determine how the provider will get access to and/or write the information or get the operation it is exposing to occur. This is very specific to the type of information so there is little this document can do to help with this step. Providers can use standard system calls to get information or can use private files and databases.
Define the schema to use and the properties and methods that will be supported
Determine which namespaces the provider will use to support the specified objects
Write two MOF files: one defines the schema to be instrumented, and the other is used to register the provider
Design the provider and make implementation decisions
Implement the provider
Build the provider
Test and debug the provider
Document, package, and release the provider

We recommend that developers start by writing the Provider Data Sheet (PDS). The provider data sheet (see the example in Appendix D) supplies information on what properties and operations are exposed by this provider, what interfaces are used, how to install this provider, and what platforms and operating systems are covered. Starting with the PDS requires that the first three tasks in the list above be addressed, and so helps the developer focus on the most important decisions about the provider and what it will do before implementation is started.

The following sections give details on each of these steps along with examples, guidelines, issues and concerns.

Developers can refer to Appendix E, Factors for Estimating Provider Effort, for guidelines in determining the effort required for provider development.

Provider Basics

Technical documentation

» Table of Contents