Solaris WBEM Developer's Guide

Chapter 1 Overview of Solaris Web-Based Enterprise Management

This chapter provides an overview of Solaris Web-Based Enterprise Management, and includes the following topics:

Note –

This chapter provides a general overview of Web-Based Enterprise Management (WBEM) and the Common Information Model (CIM). For more in-depth information about WBEM and CIM, refer to the Distributed Management Task Force's (DMTF) Web site at

About Web-Based Enterprise Management

Web-Based Enterprise Management (WBEM) is a set of management and Internet technologies. WBEM unifies the management of enterprise computing environments. With WBEM, you can deliver an integrated set of standardized management tools that leverage emerging web technologies. By developing management applications according to WBEM principles, you can create compatible products at a low development cost.

The Distributed Management Task Force (DMTF) is an industry group that represents corporations in the computer and telecommunications industries. The DMTF is leading the effort to develop and disseminate standards for the management of desktop environments, enterprise-wide systems, and the Internet. The goal of the DMTF is to develop an integrated approach to managing computers and networks across platforms and protocols. The approach is intended to result in cost-effective products that interoperate as flawlessly as possible.

About the Common Information Model

The Common Information Model (CIM), developed by the DMTF, is an industry standard used to manage systems and networks. This standard provides a common conceptual framework that classifies and defines the parts of a networked environment, and depicts how these various parts interact. The CIM captures notions that are applicable to all areas of management, independent of technology implementation.

CIM consists of the following components:

About Solaris WBEM Services

The Solaris WBEM Services software is the Solaris implementation of WBEM and CIM standards. The following components are included with Solaris WBEM Services:

Solaris WBEM Services software provides WBEM services in the Solaris operating environment, including secure access and manipulation of management data. The product includes a Solaris provider that enables management applications to access information about managed resources such as devices and software in the Solaris operating environment.

The CIMOM accepts connections from management applications that use either the Remote Method Invocation (RMI) protocol or the XML over HTTP protocol. The CIMOM provides the following services to connected clients:

Once connected to a WBEM-enabled system, WBEM clients can request WBEM operations such as creating, viewing, and deleting CIM classes and instances, querying for properties that have a specified value, and enumerating instances or classes in a specified class hierarchy.

Software Components

Solaris WBEM Services software consists of three software components: Application, Management, and Provider. These components interact with the operating system and with hardware. The following figure shows the software components and how these components interact.

Figure 1–1 Solaris WBEM Services Architecture

Diagram shows the interaction between components of the Application, Management, and Provider layers of the WBEM services architecture.

CIM Object Manager

The CIM Object Manager manages CIM objects on a WBEM-enabled system. When a WBEM client application accesses information about a CIM object, the CIMOM contacts either the appropriate provider for that object, or the CIM Object Manager Repository. When a WBEM client application requests data from a managed resource that is not available for the Repository, the CIMOM forwards the request to the provider for that managed resource. The provider dynamically retrieves the information.

WBEM client applications contact the CIM Object Manager to establish a connection. This connection is used to perform WBEM operations, such as creating a CIM class or updating a CIM instance. When a WBEM client application connects to the CIM Object Manager, the WBEM client gets a reference to the CIM Object Manager. The client can use that reference to request services and perform operations.

Managed Object Format Compiler

You use the Managed Object Format (MOF) language to specify CIM schema. You define classes and instances using ASCII text, and place those classes in a file that you submit to the MOF compiler, mofcomp(1M). The MOF compiler parses the file and adds the classes and instances defined in the file to the CIM Object Manager repository. See Chapter 7, Creating JavaBeans Components Using the MOF Compiler for information on how to use the MOF compiler to automatically generate JavaBeansTM components from MOF files.

Because you can convert MOF to Java, applications developed in MOF can run on any system or in any environment that supports the Java platform.

Note –

For more in-depth information about the MOF language, files, and syntax, see

Solaris Schema

The Solaris Schema is an extension schema of the Common Model. The Solaris Schema specifically describes managed objects running in the Solaris operating environment.

When you install Solaris WBEM Services, the CIM Schema and the Solaris Schema MOF files populate the /usr/sadm/mof directory. These files are automatically compiled when the CIMOM starts. The CIM Schema files, denoted by the CIM_ prefix, form standard CIM objects. The Solaris Schema extends the standard CIM Schema by describing Solaris objects. The MOF files that make up the Solaris Schema have the Solaris_ prefix.

Note –

The CIM Schema and Solaris Schema are installed at file:/usr/sadm/lib/wbem/doc/mofhtml/index.html.

Solaris WBEM SDK

The Solaris WBEM SDK is a set of APIs that contain the components necessary to write management applications. These applications communicate with WBEM-enabled management devices using XML and HTTP communication standards.

Solaris WBEM applications request information or services from the Common Information Model (CIM) Object Manager through the WBEM APIs. These APIs represent CIM objects as Java classes. You use the APIs to describe managed objects and to retrieve information about managed objects in a system environment. The advantage of modeling managed resources by using CIM is that those objects can be shared across any system that is CIM-compliant.

Note –

The Solaris WBEM application programming interface (API) documentation is in JavadocTM format and is installed at file:/usr/sadm/lib/wbem/doc/index.html during a Solaris installation.

The Solaris WBEM APIs are described in the following table.

Table 1–1 Solaris WBEM APIs


Package Name 




Includes common classes and methods that represent the basic CIM elements. The CIM APIs create objects on the local system. 



Applications use the CIMClient class to connect to the CIM Object Manager. Applications use the other classes and methods to transfer data to and from the CIM Object Manager.

The Batching APIs, a subset of the Client APIs, enable clients to batch multiple requests in one remote call. This capability reduces the delay introduced by multiple remote message exchanges. 



The CIM Object Manager uses these APIs to pass application requests for dynamic data to providers.  



Contains classes and methods that you use to formulate and manipulate queries by using the WBEM Query Language (WQL). 

Using CIM Workshop to Develop WBEM Applications

You can develop WBEM applications that use CIM Workshop, a GUI-based development tool included with the Solaris WBEM SDK. You use CIM Workshop to do the following:

Note –

CIM guidelines prevent you from modifying the properties, methods, and qualifiers of CIM Schema and Solaris Schema classes. You also cannot change the values of inherited properties, methods, and qualifiers.

CIM Workshop Documentation

CIM Workshop has context-sensitive online help for every dialog box except for the main window. When you click the interface components, the appropriate help text displays in the Information pane on the left side of the dialog box.

Tip –

To close and reopen the Information pane, click the question mark button on the upper left corner of the dialog box.

Running CIM Workshop

By default, CIM Workshop connects to a CIMOM running on the local host in the root/cimv2 default name space using the Remote Method Invocation (RMI) protocol. You can also point to a remote host that is running the CIM Object Manager.

How to Start CIM Workshop
  1. At the system prompt, type:

    % /usr/sadm/bin/cimworkshop

    The CIM Workshop Login dialog box displays.

  2. Follow the instructions in the context-sensitive help to fill in the fields in the Login dialog box. Then click OK.

    The CIM Workshop main window displays.

How to Exit CIM Workshop
  1. From the CIM Workshop main window, choose Workshop->Exit.

    CIM Workshop exits.

About the Main Window

The main window in CIM Workshop is divided into three panes: