Solaris WBEM Services Administrator's Guide

Upgrading the CIM Object Manager Repository

If you are upgrading from Solaris 8 10/00 (WBEM Services 2.2) or earlier to Solaris 8 1/01 (WBEM Services 2.3) , you must upgrade the CIM Object Manager Repository datastore format.

Datastore Format forSolaris 8 10/00 (WBEM Services 2.2) or earlier 

Datastore Format forSolaris 8 1/01 (WBEM Services 2.3) 

JavaSpacesTM

Reliable Log 

To upgrade a JavaSpaces datastore to the newer Reliable Log repository format, you use the wbemconfig convert command. This command successfully converts any proprietary custom MOF data, but not any CIM or Solaris MOF data you have modified--these will be destroyed. To recompile any modified CIM or Solaris MOF data into the new repository, run the mofcomp compiler on the MOF files containing the class definitions.

The wbemconfig convert command creates a directory named /var/sadm/wbem/logr/ that contains the converted data.


Caution - Caution -

To prevent corruption of your data, only use the wbemconfig convert command after stopping the CIM Object Manager with the init.wbem stop command.



Note -

Because the wbemconfig convert command invokes the JVM (Java Virtual Machine) to perform conversion of the repository, you must be running the same version of the JVM as was used to create the original JavaSpaces datastore. After the wbemconfig convert command is completed, you can change to any version of the JVM you want.


Upgrading the CIM Repository datastore format is a two-part process:

Before Installing Your New Version of Solaris
  1. Log in as superuser (root) and save the JavaSpaces software. Type the following command:

    # cp /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.tmp

  2. Check and record the version of the JDK installed on your machine. For example:

    # /usr/bin/java -version java version "1.2.1" Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit)

    You must be running the same version of the JDK as was used when the original JavaSpaces datastore was created.

After Installing Your New Version of Solaris
  1. Log in as superuser and stop the CIM Object Manager:

    # /etc/init.d/init.wbem stop

  2. Restore the JavaSpace software that you saved in Step 1 of "Before Installing Your New Version of Solaris".

    # mv /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.2# mv /usr/sadm/lib/wbem/outrigger.jar.tmp /usr/sadm/lib/wbem/outrigger.jar

  3. Install the old version of the JDK that was on your machine previously, in a separate location from the current (newly installed) JDK. You can download a JDK from http://java.sun.com/products/.

  4. Change the symbolic link /usr/java to point to the location of the old version of the JDK. For example, if you installed Solaris_JDK_1.2.1_04c in /old_sdk:

    # rm /usr/java# ln -s /old_sdk/Solaris_JDK_1.2.1_04c /usr/java

  5. Convert the JavaSpaces datastore to Reliable Log format.

    # /usr/sadm/lib/wbem/wbemconfig convert

  6. Restore the outrigger.jar file included in the new version of Solaris.

    # mv /usr/sadm/lib/wbem/outrigger.jar.2 /usr/sadm/lib/wbem/outrigger.jar

  7. Change the symbolic link /usr/java to point to the location of the new JDK that came in the new version of Solaris:

    # rm /usr/java# ln -s /usr/java1.2 /usr/java

  8. Restart the CIM Object Manager.

    # /etc/init.d/init.wbem start