JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris WBEM Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Overview of Solaris Web-Based Enterprise Management

2.  Using the CIM Object Manager

3.  Using the Sample Programs

4.  Writing a Client Program

5.  Writing WBEM Queries

6.  Writing a Provider Program

About Providers

Provider Data Sources

Types of Providers

Provider Naming Conventions

Implementing the Provider Interfaces

Writing an Instance Provider

Writing a Method Provider

Writing an Associator Provider

Writing an Indication Provider

How To Generate an Event Indication

Event Provider Methods

Creating and Delivering Indications

About Authorizations

Writing a Native Provider

Creating a Provider

How to Set the Provider CLASSPATH

How to Register a Provider

7.  Creating JavaBeans Components Using the MOF Compiler

8.  Administering Security

9.  Troubleshooting

A.  Solaris Schema


About Providers

Providers are special classes that communicate with managed resources, such as disk drives and CPUs, to access data. The providers then forward the data to the CIM Object Manager (CIMOM), the primary WBEM agent that coordinates Solaris WBEM Services, for integration and interpretation. These providers can relieve the CIMOM by assuming the task of managing distinct subsets of WBEM resources. Providers use the javax.wbem.provider API to transfer this data. When the CIMOM receives a request from an application for data that is not available in the CIM Object Manager Repository, the CIMOM forwards the request, using the provider interfaces, to the appropriate provider.

Solaris software providers exist for a variety of areas: users, groups, aliases, roles, file systems, disks, processes, cron tool, network configuration, product registry, and device and system performance monitoring.

Providers create, modify, and delete instances rather than classes, which serve as templates for the instances. Instances can exist in persistent storage or be used dynamically.

Although providers have their own process and memory, providers perform work delegated by the CIMOM. The CIMOM must know the location of each provider in order to coordinate WBEM. You inform the CIMOM about new or modified providers by including those providers in a MOF file. A MOF file defines the classes and instances that a provider supports. You register a MOF file using the mofcomp(1M) command.

Providers perform the following tasks:

Note - Providers must reside on the same machine as the CIMOM.

Provider Data Sources

Providers can retrieve data from the following sources:

Types of Providers

Providers are categorized according to the types of requests the providers handle. Client programs communicate with the CIMOM and access WBEM data through the client API. The CIMOM maps the provider methods to the corresponding client methods in the client API. However, the argument lists and return values of corresponding methods might differ. See file:/usr/sadm/lib/wbem/doc/index.html.

Ensure that your argument list and return type are correct for the method and class used.

The Solaris WBEM SDK provider types are shown in the following table.

Table 6-1 Provider Types

Class Name
Supply dynamic instances of a given class, and support instance retrieval, enumeration, modification, and deletion
Supply methods of one or more classes
Supply instances of dynamic association classes
Handle indications of CIM events
A marker interface that indicates to the CIMOM that the provider does its own authorization check

A single provider can act as one or more of the provider types by registering and implementing the relevant methods.

Provider Naming Conventions

You can include providers in a single Java class file or store each provider in a separate class. The provider name identifies the Java class that serves as the provider for the class. Currently, the CIMOM supports only providers that are written in the Java language.

Provider and class names must follow these rules:

Note - You must prepend “java:” to every provider qualifier to notify the CIMOM that the provider is written in the Java language.

Follow standard Java class and package naming conventions to create your provider names. The prefix of a package name is written in lowercase ASCII letters and must be one of the top-level domain names (com, edu, gov, mil, net, org), or one of the English two-letter country codes specified in ISO Standards 3166, 1981.

Subsequent components of the package name can vary according to your organization's internal naming conventions. Such conventions might specify that certain directory name components are division, department, project, machine, or login names. For example, the provider name java:com.sun.wbem.cimom indicates the following information: