test

Solaris WBEM Services Administration Guide

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 JavaSpacesTM 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

  1. Become superuser.

  2. 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

  3. 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

  1. Upgrade your system to the Solaris 9 operating environment.

  2. Become superuser.

  3. Stop the CIM Object Manager.


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

    Caution – Caution –

    Failure to stop the CIM Object Manager before running wbemconfig convert might corrupt your data.

  4. 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.

  5. 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.

  6. 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

  7. 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.

  8. 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

  9. Stop the CIM Object Manager.


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

  10. 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

  1. Upgrade your system to the Solaris 9 operating environment.

  2. Become superuser.

  3. Stop the CIM Object Manager.


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

    Caution – Caution –

    Failure to stop the CIM Object Manager before you run wbemconfig convert might corrupt your data.

  4. 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.