Chapter 10 Installing Solaris WBEM Services

This section describes Solaris WBEM Services and explains how to install and remove it from your system. Topics covered include the following:

• About Solaris WBEM Services

• Installation Prerequisites

• Shared Packages

• Installing Solaris WBEM Services

• Configuring After Installing on Solaris 7

• Removing Solaris WBEM Services

About Solaris WBEM Services

Solaris WBEM Services includes the following components:

• CIM Object Manager

• Sun WBEM User Manager

• Solaris Provider

CIM Object Manager

The Common Information Model (CIM) Object Manager manages CIM objects and routes object data. CIM Object Manager is a standard executable Java class file that is started automatically as part of the post-installation process. CIM objects are represented internally as Java classes. When an application uses the client API to request or update information about a managed object, the CIM Object Manager contacts either the appropriate provider for that object or the CIM Repository, the persistent storage mechanism.

Classes, properties, and methods handled by a provider have a Provider qualifier that identifies the provider to contact for the class. When the CIM Object Manager receives a request for a class that has a Provider qualifier, it routes the request to the specified provider. If no provider is specified, it routes the request to the persistent data storage, using the Java Naming and Directory Interface (JNDI).

The CIM Object Manager can be installed and run on one or more Solaris hosts. When a WBEM-enabled client connects to a CIM Object Manager, it gets a reference to the CIM Object Manager. The client can then perform WBEM operations using this reference.

Semantic and Syntactic Checking

CIM Object Manager performs syntactical and semantic checking. Syntactical checking refers to the ability to detect an error, such as a misplaced semicolon or a forgotten brace, in a line of code. Semantic checking refers to the ability to detect an error in the rules or logic of the program. The CIM Object Manager follows rules provided by the Common Information Model, and detects deviations from CIM rules in a WBEM application.

For example, CIM rules designate that only a key property can override another key property. Class A, which is assigned a key, cannot be overwritten by Class B because Class B is not assigned a key. In this case, CIM Object Manager returns a semantic error.

Class A        
\\Define Class A 
{     
[Key]     int a;   
}    
Class B:A     
 \\Class B extends A  
{  
[overrides ("a", key (false)]   int b;   
}   

Sun WBEM User Manager

Sun WBEM User Manager is a software application in which you can set user privileges to specific areas, called namespaces, where classes are stored. You can also delete namespaces and create new namespaces in Sun WBEM User Manager. For information about how to use Sun WBEM User Manager, see Chapter 12, Administering Security.

Solaris Provider

Solaris WBEM Services includes the Solaris Provider, a program that enables the CIM Object Manager to communicate with the Solaris operating environment. The Solaris Provider is defined in a set of files created in Managed Object Format (MOF). Collectively, these files are referred to as the Solaris Schema. They extend CIM classes for the Solaris environment by providing definitions of the classes that the CIM Object Manager and the Solaris environment use to communicate.

The MOF files that make up the Solaris Schema are located in /opt/SUNWconn/wbem/schema. You can view these files in a text editor of your choice. Solaris_Schema1.0.mof is the principal schema file. It contains pointers to the other files that make up the Solaris Schema in the order in which the files are compiled at installation.

During the installation of Solaris WBEM Services, the MOF compiler compiles standard CIM 2.1 MOF files into the CIM Object Manager. After installation, these compiled classes represent the resources on your system, such as processes, application software, CPU resources, and memory. Applications can then use the API to get, set, and otherwise manipulate the managed resources on any WBEM-enabled system.

In addition, Solaris WBEM Services includes the Solaris Schema, MOF files that further describe Solaris-specific resources, such as Solaris patches and installed software packages. The Solaris Schema extends the standard CIM Schema classes.

Other vendors who extend the standard CIM Schema also build on the base classes. The benefit of using this information model to manage systems is that an application can get and set the properties for any system resource (for example, process) on any CIM system. You can use the same API to get and set properties about a process or device on a Microsoft Windows 32 system, a Solaris system, a UNIX platform, or any other CIM-compliant platform.

Installation Prerequisites

Prior to installing the Solaris WBEM Services, ensure that Sun Directory Services (SDS) version 3.1 or a compatible version is installed. SDS is used for the CIM Repository.

Shared Packages

You can install Solaris WBEM Services as a product that runs on its own, or you can install both Solaris WBEM Services and the Sun WBEM SDK to be used interactively. Installing either product involves installing the product packages. The packages are compilations of the files, interfaces, and components of each product.

Solaris WBEM Services and the Sun WBEM SDK share some of the same packages. For example, both applications require the package named SUNWwbapi, that contains the Client APIs.

For information about Solaris WBEM Services packages and installation instructions, see the following section, "Installing Solaris WBEM Services". For information about Sun WBEM SDK packages and installation instructions, see Chapter 2, Installing the Sun WBEM SDK.

Installing Solaris WBEM Services

The following table describes the packages you need to install Solaris WBEM Services.

How to Install Solaris WBEM Services

1. Become root on your system by typing the following command:

   % su

2. Type the root password when you are prompted.

3. Change directories to the location of the packages in your work environment.

4. At the system prompt, type the following command to obtain a list of packages:

   # pkgadd -d .

   The list of packages is displayed. You are prompted to select one or all packages.

5. Type the number of the package you want to install.

   • Type 1 to install the SUNWwbapi package. It is important to install this package first because the other packages rely on the Sun WBEM APIs.

   • Type 2 to install the SUNWwbcor package, which installs Solaris WBEM Services.

     When the SUNWwbcor package installs, the installation routine prompts you to provide the Sun Directory Services (SDS) administration password. If you have already installed SDS prior to installing Solaris WBEM Services, type the SDS password at the prompt. If you have not previously installed SDS, type a password of your choice at the prompt to set the SDS password. When you are prompted to re-enter the password, type the password again at the prompt.

   • Type 7 to install the SUNWwbxml package, which installs the XML Libraries.

   • (Optional): Type 3 to install the SUNWwbdoc package, which installs this guide.

   As each package installs, its contents are listed for you to view. When the installation is complete, you are notified with the message: Installation of package_name was successful.

6. When you have finished installing the packages, type q to exit the package installation routine.

7. Type exit at the system prompt to exit root.

Configuring After Installing in Solaris 7

When you install Solaris WBEM Services as part of a Solaris Easy Access Server 3.0 installation in Solaris 7, you may not be prompted to enter a password for the Sun Directory Services (SDS) administrative account. If you did not enter this password during the installation, run the wbemconfig script as described in the following procedure to start SDS and configure Solaris WBEM Services. The wbemconfig script completes the following tasks:

• Configures and starts SDS

• Sets Java environment variables

• Starts the CIM Object Manager

• Starts the MOF Compiler and compiles two MOF files:

  • CIM_Schema21.mof - provides the classes that make up the CIM Schema

  • Solaris_Schema1.0.mof - provides the classes that make up the Solaris Schema

How to Configure Your Environment After Installation

1. Become root on your system by typing the following command:

   % su

2. Type the root password when you are prompted.

3. Run the wbemconfig script using the following command:

   # /opt/SUNWconn/wbem/bin/wbemconfig

4. When prompted, type a password of your choice to be set as the SDS administrative account password.

   The wbemconfig script runs. SDS starts followed by the CIM Object Manager. The MOF Compiler starts and compiles the CIM and Solaris Schema files.

Uninstalling Solaris WBEM Services

When you want to uninstall Solaris WBEM Services from your computer, you remove the packages. When you remove the Solaris WBEM Services packages, not all files that make up your WBEM installation are removed. If Sun WBEM SDK is installed, none of its associated packages are removed. For information about removing Sun WBEM SDK, see "Uninstalling the Sun WBEM SDK" in Chapter 2, Installing the Sun WBEM SDK.

If you uninstall both the Sun WBEM SDK and Solaris WBEM Services, the LDAP schema and data files remain installed. You can remove these files, and the subdirectories that contain them, from the path /opt/SUNWconn/ldap. However, if you remove the LDAP data, you may encounter errors in other applications that require the data. Also, if you remove the LDAP data, you will need to re-install it if you decide to re-install the Sun WBEM SDK or Solaris WBEM Services at a later date.

How to Uninstall Solaris WBEM Services

1. Become root on your system by typing the following command:

   % su

2. Type the root password at the Password prompt.

3. Type the following command at the system prompt to remove a package:

   # pkgrm package_name

   where package_name is replaced by the name of the package that you want to remove.

4. Type y when you are prompted with the question: "Do you want to remove this package?"

   You can remove the following packages in any order:

   • SUNWwbcor

   • SUNWwbxml

     SUNWwbdoc

   Be sure to remove the SUNWwbapi package last because all other packages rely on it.

   When a package has been removed successfully, the following message is displayed.

   Removal of package_name was successful

5. Type the pkgrm command at the system prompt for each package you want to remove.

6. Type exit to exit root and return to your system prompt when you have finished removing packages.