About Solaris WBEM Services

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

• “CIM Object Manager”

• “Managed Object Format Compiler”

• “Solaris Schema”

• “Solaris WBEM SDK”

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 CIM Object Manager 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 CIM Object Manager Repository, the CIM Object Manager 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 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, which it then uses 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 them 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 2, Creating JavaBeans Using the MOF Compiler for information on how to use the MOF compiler to automatically generate JavaBeans 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 Java.

---

Note -

For more in-depth information about the MOF language, files, and syntax, see http://www.dmtf.org/education/cimtutorial/extend/spec.php.

---

Solaris Schema

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 CIM Object Manager 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 and Solaris Schema is 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 that 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 retrieve information about managed objects in a system environment. The advantage of modeling managed resources 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 Javadoc 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

API	Package Name	Description
CIM	javax.wbem.cim	Includes common classes and methods that represent the basic CIM elements. The CIM APIs create objects on the local system.
Client  See Chapter 3, Writing a Client Program.	java.wbem.client	Applications use the CIMClient class to connect to the CIM Object Manager, and use the other classes and methods to transfer data to and from the CIM Object Manager. The new Batching APIs, a subset of the Client APIs, enable clients to batch multiple requests in one remote call, reducing the delay introduced by multiple remote message exchanges.
Provider  See Chapter 4, Writing a Provider Program.	java.wbem.provider	The CIM Object Manager uses these APIs to pass application requests for dynamic data to providers.
Query  See Chapter 5, Writing WBEM Queries.	java.wbem.query	Contains classes and methods that you use to formulate and manipulate queries using the WBEM Query Language (WQL).