Solaris WBEM Services Administration Guide

Chapter 2 Using the CIM Object Manager (Tasks)

The Common Information Model (CIM) Object Manager is software that transfers CIM data between WBEM client applications and managed resources.

Here is a list of the information in this chapter.

About the CIM Object Manager

The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a representation, or model, of a managed resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes.

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 . Providers are classes that communicate with managed objects to access data. When a WBEM client application requests data from a managed resource that is not available from 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.

At startup, the CIM Object Manager performs the following functions:

Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 5988
Sets up a connection to the CIM Object Manager Repository
Waits for incoming requests

The CIM Object Manager:

Performs security checks to authenticate user login and authorization to access namespaces
Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification
Routes requests to the appropriate provider or to the CIM Object Manager Repository
Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications

A WBEM client application contacts the CIM Object Manager to establish a connection when it needs 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 operations.

`init.wbem` Command

Solaris automatically runs init.wbem during installation and every time you reboot a system. The init.wbem command starts the CIM Object Manager and Solaris Management Console server, both of which run combined in a single process. You can also use init.wbem to stop the CIM Object Manager, to stop the Solaris Management Console server, or to retrieve status from a server. You can find additional information about this command in the init.wbem(1M) man page.

Generally, you do not need to stop the CIM Object Manager. However, if you change an existing provider, you must stop and restart the CIM Object Manager before using the updated provider.

You can specify three options with init.wbem:

start – Starts the CIM Object Manager or Solaris Management Console server on the local host.
stop – Stops the CIM Object Manager and Solaris Management Console server on the local host.
status – Gets status for the CIM Object Manager and Solaris Management Console server on the local host.

Solaris Management Console Server

The Solaris Management Console software provides Solaris management applications such as User Manager, Disk Manager, and Log Viewer. The Solaris Management Console server provides tools for the console to download and performs common services for the console and its tools, such as authentication, authorization, logging, messaging, and persistence.

The Solaris Management Console is described in other chapters in this document, and is also described in System Administration Guide: Basic Administration.

System Booting

The init.wbem command is located in the /etc/init.d directory. The file /etc/rc2.d/S90wbem runs with the start option when initialization state 2 is entered, normally at boot time. The files /etc/rc0.d/K36wbem, /etc/rc1.d/K36wbem, and /etc/rcS.d/K36wbem are run with the stop option when initialization states 0, 1, and S are entered, normally when the system halts, or when the system enters either system administrator mode or single-user mode.

Stopping and Restarting the CIM Object Manager

If you change a provider, you must stop and restart the CIM Object Manager before using the updated provider.

How to Stop the CIM Object Manager

Become superuser.

Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop

How to Restart the CIM Object Manager

Become superuser.

Restart the CIM Object Manager.
# /etc/init.d/init.wbem start

Upgrading the CIM Object Manager Repository (Task Map)

The following table identifies the procedures to upgrade the CIM Object Manager Repository. Whether you save the JavaSpaces datastore and convert or merge WBEM data depends on the version of the Solaris operating environment that you are using before you upgrade to the Solaris 9 operating environment. Table 2–1 describes how to determine the procedures you follow to upgrade the CIM Object Manager Repository.

Task	Description	For Instructions
Save the JavaSpaces datastore.	Save the JavaSpaces datastore by downloading or copying files and determining the version of the JDK that is currently installed on your system.	How to Save the JavaSpaces Datastore
Convert WBEM data.	Convert WBEM data by using the `wbemconfig convert` command.	How to Convert WBEM Data
Merge WBEM data.	Merge WBEM data by using the `wbemconfig convert` command.	How to Merge WBEM Data

Upgrading the CIM Object Manager Repository

You must update any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format that is used with WBEM Services 2.5 in Solaris 9.

Before you upgrade to the Solaris 9 operating environment, you might need to save the JavaSpaces^TM datastore. After you upgrade, you must convert or merge data, depending on the version of the Solaris environment that you were running before you upgraded to the Solaris 9 environment.

Failure to convert or merge the data results in data loss.

Use the following table to determine whether or not to save the JavaSpaces software before you upgrade and whether to convert or merge the WBEM data after you upgrade to the Solaris 9 operating environment.

Table 2–1 Determining Whether to Convert or Merge WBEM Data


Operating Environment Before Upgrading to Solaris 9	Save JavaSpaces Datastore Before You Upgrade?	Convert or merge?
Solaris 8 (Solaris WBEM Services 2.0) Solaris 8 6/00 (WBEM Services 2.0) Solaris 8 10/00 (WBEM Services 2.2)	Yes	Convert
Solaris 8 1/01 (WBEM Services 2.3) Solaris 8 4/01 (WBEM Services 2.4) Solaris 8 7/01 (WBEM Services 2.4) Solaris 8 10/01 (WBEM Services 2.4) Solaris 9 (Beta) (WBEM Services 2.5)	No	Merge

How to Save the JavaSpaces Datastore

Become superuser.

Do you want to download the files that you will need, or do you want to save your current JavaSpaces datastore?

Note –

The safer method is to save your JavaSpaces datastore rather than to download files.

If you want to download the files, go to How to Convert WBEM Data.

If you want to save your JavaSpaces datastore, enter the following commands:

# cd /usr/sadm/lib/wbem
# cp outrigger.jar outrigger.jar.tmp
# cp outrigger-dl.jar outrigger-dl.jar.tmp
# cp transient-outrigger.jar transient-outrigger.jar.tmp
# cp jini-core.jar jini-core.jar.tmp
# cp jini-ext.jar jini-ext.jar.tmp
# cp tools.jar tools.jar.tmp
# cp pro.zip pro.zip.tmp

Determine and record the version of the JDK that is currently installed on your system.
# /usr/bin/java -version java version "1.2.1" Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit)
Note –
You must be running the same version of the JDK as you used when you created the original JavaSpaces datastore to convert WBEM data.

How to Convert WBEM Data

Upgrade your system to the Solaris 9 operating environment.

Become superuser.

Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop
Caution –
Failure to stop the CIM Object Manager before running wbemconfig convert might corrupt your data.

Did you save your current JavaSpaces datastore in How to Save the JavaSpaces Datastore?

If yes, restore your JavaSpaces datastore.

# cd /usr/sadm/lib/wbem
# cp outrigger.jar.tmp outrigger.jar
# cp outrigger-dl.jar.tmp outrigger-dl.jar
# cp transient-outrigger.jar.tmp transient-outrigger.jar
# cp jini-core.jar.tmp jini-core.jar
# cp jini-ext.jar.tmp jini-ext.jar
# cp tools.jar.tmp tools.jar
# cp pro.zip.tmp pro.zip

If no, download and unzip the file UpgradeRepository.zip from http://www.sun.com/solaris/wbem.

UpgradeRepository.zip contains the .jar files that you need to later convert the WBEM data.

In a directory other than the one in which the JDK you are currently using is installed, obtain and install the JDK that you recorded in How to Save the JavaSpaces Datastore.

Change the symbolic link from the currently installed JDK in /usr/java to the JDK you recorded in How to Save the JavaSpaces Datastore.

For example, to change the currently installed JDK to Solaris_JDK_1.2.1_04c in /old_sdk, type:
# rm /usr/java # ln -s /old_sdk/Solaris_JDK_1.2.1_04c /usr/java

Convert the data in the JavaSpaces datastore to Reliable Log format.
# /usr/sadm/lib/wbem/wbemconfig convert
The wbemconfig convert command successfully converts any proprietary custom MOF data, but not any CIM or Solaris MOF data that you have modified. CIM and Solaris MOF data that you have modified is destroyed.

Note –
To recompile any modified CIM or Solaris MOF data in the new repository, use the mofcomp command to compile the MOF files that contain the class definitions.

Change the symbolic link from /usr/java to the location of the JDK software that ships with the Solaris 9 operating environment.

For example, to change the symbolic link from /usr/java1.4, type:
# rm /usr/java # ln -s /usr/java1.4 /usr/java

Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop

Start the CIM Object Manager.
# /etc/init.d/init.wbem start
The CIM Object Manager adds repository files that contain the converted data to the directory /var/sadm/wbem/logr/, which the Solaris installer created when you upgraded your system to Solaris 9.

How to Merge WBEM Data

Upgrade your system to the Solaris 9 operating environment.

Become superuser.

Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop
Caution –
Failure to stop the CIM Object Manager before you run wbemconfig convert might corrupt your data.

Merge the original data in the previous Reliable Log with the data in the Solaris 9 Reliable Log.
# /usr/sadm/lib/wbem/wbemconfig convert
Note –
The wbemconfig convert command successfully converts any proprietary custom MOF data, but not any CIM or Solaris MOF data that you have modified. CIM and Solaris MOF data that you have modified is destroyed. To recompile any modified CIM or Solaris MOF data in the new repository, use the mofcomp command to compile the MOF files that contain the class definitions.

Exception Messages

The CIM Object Manager generates exception messages to indicate incorrect MOF syntax and semantics. The Solaris WBEM SDK Developer's Guide contains information about exception messages.