This section describes the Sun WBEM SDK and explains how to install and remove it from your system. Topics covered include the following:
Sun WBEM SDK is a software developer's tool kit you can use to develop applications that can run in WBEM environments. You can also develop providers, programs that communicate between WBEM components and the CIM Object Manager, to run on the Java platform in any WBEM-enabled environment.
Providers must be started on a computer running the CIM Object Manager. For Sun WBEM SDK version 1.0, the CIM Object Manager is not supported in the Windows environment. Consequently, the Sun WBEM SDK is not recommended for the development of providers for the Microsoft Windows 32-bit operating system.
Sun WBEM SDK includes the following components:
CIM WorkShop
Client API
Provider API
MOF Compiler
Sample client programs
Sample provider programs
This guide
Javadoc for Client and Provider API
CIM WorkShop is a software application in which you can view CIM classes and instances, create new CIM subclasses and instances, and add or delete new properties, methods, and qualifiers of subclasses. For information about how to use CIM WorkShop, see Chapter 4, CIM WorkShop.
The Client Application Programming Interface (API) is a public API that Java applications use to request operations from the CIM Object Manager. For a complete list and description of the Client API, see Chapter 5, Application Programming Interfaces.
Provider APIs are interfaces that the CIM Object Manager and object providers use to communicate with each other. Providers can use these interfaces to provide the CIM Object Manager a particular kind of dynamic data. When an application requests dynamic data from the CIM Object Manager, the CIM Object Manager uses these interfaces to pass the request to the provider that registered to be the provider. For a description of the Provider API, see Chapter 5, Application Programming Interfaces.
The Managed Object Format (MOF) is a standard text format for representing CIM data. Products developed according to the CIM specification must be able to exchange information in MOF format.
The Sun WBEM SDK software uses a MOF Compiler (mofc) to convert a MOF text file to Java classes. Internally, Sun WBEM SDK uses Java classes to represent CIM data.
The MOF language defines a syntax for defining CIM classes and instances. MOF provides developers and administrators with a simple and fast technique for modifying the CIM Object Manager Repository.
The Sun WBEM SDK provides sample Java programs that use the Client APIs. These programs are installed in /opt/SUNWconn/wbem/demo. You can run the sample client programs and use them to build your own applications. For information about the sample client programs, see "Using Client Examples" in the chapter, "Using Sun WBEM SDK Examples."
Sample provider programs use the Provider APIs. You can use these programs to develop providers that extend CIM capabilities into your specific technology. For example, you can develop a provider that enables your technology to communicate with the CIM Object Manager. For information about the sample provider programs, see "Using the Provider Examples" in the chapter, "Using Sun WBEM SDK Examples."
This guide and the Javadoc reference pages are provided as part of Sun WBEM SDK.
Prior to installing the Sun WBEM SDK kits, the Java Development Kit (JDK) version 1.1.7_05 or a compatible version must be installed on the server designated to run the CIM Object Manager.
You can install Sun WBEM SDK as a product that runs on its own, or you can install both Sun WBEM SDK and Solaris WBEM Services 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.
Sun WBEM SDK and Solaris WBEM Services share some of the same packages. For example, both applications require the package named SUNWwbapi, that contains the Client APIs.
For information about Sun WBEM SDK packages and installation instructions, see the following section, "Installing the Sun WBEM SDK". For information about Solaris WBEM Services packages and installation instructions, see the following section, "Installing Solaris WBEM Services" in Chapter 10, Installing Solaris WBEM Services.
The following table describes the packages you need to install Sun WBEM SDK.
Table 2-1 Sun WBEM SDK Packages
Required Packages |
||
Package Name |
Title |
Description |
SUNWwbapi |
Sun WBEM SDK - APIs |
Contains the client and provider APIs and additional functionality required to run the Sun WBEM SDK and Solaris WBEM Services. This package is provided with the Sun WBEM SDK. It is required by both products. |
SUNWwbdev |
Sun WBEM Software Development Kit (SDK) |
Contains the MOF Compiler, CIM Workshop, context help used in CIM Workshop, and graphics files that make up the Sun WBEM SDK. |
Optional Packages |
||
Package Name |
Title |
Description |
SUNWwbdoc |
Solaris WBEM Services - Documentation |
Contains this guide, which supports both the Sun WBEM SDK and Solaris WBEM Services. Although this package is provided with Solaris WBEM Services, it can be installed optionally to support either product. |
Localized Packages |
||
Package Name |
Title |
Description |
SUNWxxwbd |
Sun WBEM SDK - Localization |
Contains the localized version of the Solaris WBEM Services. The xx is replaced by the character code that represents the particular language in which the application is localized. For example, the French version of the Sun WBEM SDK is packaged in SUNWfrwbd. |
Become root on your system by typing the following command:
% su |
Type the root password when you are prompted.
Change directories to the location of the packages in your work environment.
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.
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 5 to install the SUNWwbdev package, which installs the Sun WBEM SDK.
(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.
When you have finished installing the packages, type q to exit the package installation routine.
Type exit at the system prompt to exit root.
After you finish installing the Sun WBEM SDK, you can use the product components. Getting started entails completing tasks that you will use on a daily basis, including the following:
When you want to uninstall the Sun WBEM SDK from your computer, you remove the packages. When you remove the Sun WBEM SDK packages, not all files that make up your total installation are removed. If Solaris WBEM Services is installed, none of its associated packages are removed. For information about removing Solaris WBEM Services, see Chapter 10, Installing Solaris WBEM Services.
After you remove 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.
Become root on your system by typing the following command:
% su |
Type the root password at the Password prompt.
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.
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:
SUNWwbdev
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 |
Type the pkgrm command at the system prompt for each package you want to remove.
Type exit to exit root and return to your system prompt when you have finished removing packages.