|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris WBEM Developer's Guide Oracle Solaris 11 Express 11/10|
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:
Management services – These services are in the form of a CIMOM. The CIMOM checks the semantics and syntax of CIM data and distributes data between applications, the CIM Object Manager Repository, and managed resources.
Security services – Specify these services for WBEM through the Solaris Management Console User tool. These services are described inSystem Administration Guide: Security Services.
Sun WBEM User Manager – Use this tool to establish an access control list (ACL) for a specific name space on the WBEM server. Sun WBEM User Manager enables you to add and delete authorized users, set access privileges for authorized users, and manage user authentication and access to CIM objects on a WBEM-enabled system. ACL-based security is uniquely provided by Solaris WBEM Services.
Logging services – Consist of classes that developers can use to create applications that dynamically record and retrieve event data. Administrators use this data to track and determine the cause of events. Logging services are described in more detail in Chapter 9, Troubleshooting.
XML services – Convert XML data into CIM classes, enabling XML/HTTP-based WBEM clients to communicate with the CIM Object Manager.
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.
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
Application layer – WBEM clients process and display data from managed resources. Solaris WBEM Services include the following applications.
Sun WBEM User Manager and Solaris Management Console User tool – Applications that enable system administrators to add and delete authorized users and to set these users' access privileges to managed resources.
Solaris Management Console Log Viewer – An application that displays log files. A user can view details of a log record, including the name of the user who issued a logged command and the client computer on which a logged event occurred.
Managed Object Format (MOF) compiler – A program that parses a file containing MOF statements, converts the classes and instances defined in the file to Java classes, and then adds the Java classes to the CIM Object Manager Repository, a central storage area for management data.
MOF is a language for defining CIM classes and instances. MOF files are ASCII text files that use the MOF language to describe CIM objects. A CIM object is a representation, or model, of a managed resource, such as a printer, disk drive, or CPU. MOF files are located in /usr/sadm/mof.
Many sites store information about managed resources in MOF files. Because MOF can be converted to Java, applications that can run on any system with a Java virtual machine can interpret and exchange this information. You can also use the mofcomp command to compile MOF files at any time after installation. MOF is described on the DMTF web page at dmtf.org.
Management layer – Components at this layer provide services to connected WBEM clients.
Common Information Model (CIM) Object Manager – Software that manages CIM objects on a WBEM system. CIM objects are stored internally as Java classes. The CIM Object Manager transfers information between WBEM clients, the CIM Object Manager Repository, and managed resources.
Client and CIM application programming interfaces (APIs) – WBEM client applications use these Java interfaces to request operations, such as creating or viewing classes or instances of managed resources, from the CIM Object Manager.
Provider interfaces – Providers use these interfaces to transfer information about managed resources to the CIM Object Manager. The CIM Object Manager uses the provider interfaces to transfer information to locally installed providers.
Provider layer – Providers act as intermediaries between the CIM Object Manager and one or more managed resources. When the CIMOM receives a request from a WBEM client for data that is not available from the CIM Object Manager Repository, the CIMOM forwards the request to the appropriate provider.
Solaris providers – Provide the CIM Object Manager with instances of managed resources in the Solaris operating environment. Providers get and set information on managed devices. A native provider is a machine-specific program that is written to run on a managed device. For example, a provider that accesses data on a system running the Solaris operating environment probably includes C functions to query that system. The Java Native Interface is part of the JDK software. By writing programs using the Java Native Interface, you ensure that your code is portable across all platforms. The Java Native Interface enables Java code that runs within a Java virtual machine to operate with applications and libraries that are written in other languages, such as C, C++, and assembly.
Solaris Schema – A collection of classes that describes managed objects in the Solaris operating environment. The CIM Schema and Solaris Schema classes are stored in the CIM Object Manager Repository. The CIM Schema is a collection of class definitions used to represent managed objects that occur in every management environment.
The Solaris Schema is a collection of class definitions that extend the CIM Schema and represent managed objects in a typical Solaris operating environment. Users can also use the MOF compiler (mofcomp) to add CIM Schema, Solaris Schema, or other classes to the CIM Object Manager Repository.
Operating system layer – The Solaris providers enable management applications to access information about managed resources such as devices and software, in the Solaris operating environment.
Hardware layer – A management client can access management data on any supported Solaris platform.
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.
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 JavaBeans 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 dmtf.org/education.
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.
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 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