JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris WBEM Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

Preface

1.  Overview of Solaris Web-Based Enterprise Management

2.  Using the CIM Object Manager

About the CIM Object Manager

init.wbem Command

Solaris Management Console Server

System Booting

Stopping and Restarting the CIM Object Manager

How to Stop the CIM Object Manager

How to Restart the CIM Object Manager

Upgrading the CIM Object Manager Repository

How to Recompile Your MOF Files

How to Merge WBEM Data

Exception Messages

3.  Using the Sample Programs

4.  Writing a Client Program

5.  Writing WBEM Queries

6.  Writing a Provider Program

7.  Creating JavaBeans Components Using the MOF Compiler

8.  Administering Security

9.  Troubleshooting

A.  Solaris Schema

Index

Upgrading the CIM Object Manager Repository

If you have upgraded to the Solaris 9 platform from a previous version of the Solaris software, you must update any proprietary custom Managed Object Format (MOF) data to the new repository format that is used in the Solaris 9 software. Any CIM and Solaris MOF data that you modified prior to the upgrade is destroyed by the upgrade. As a result, you will either need to recompile your MOF files or merge the WBEM data after you upgrade.


Caution

Caution - Failure to recompile or merge the modified data results in data loss.


Use the following table to determine whether to recompile or merge the WBEM data after you upgrade to the Solaris 9 operating environment.

Table 2-1 Determining Whether to Recompile or Merge WBEM Data

Environment Before Upgrade
Recompile Proprietary Managed Object Format (MOF) Files?
Solaris 8 (Solaris WBEM Services 2.0)

Solaris 8 6/00 (WBEM Services 2.0)

Solaris 8 10/00 (WBEM Services 2.2)

Yes
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 5/02 (WBEM Services 2.5)

Solaris 9 9/02 (WBEM Services 2.5)

Solaris 9 12/02 (WBEM Services 2.5)

No. However, you need to merge the data into an upgraded repository.

How to Recompile Your MOF Files

  1. Upgrade your system to the Solaris 9 operating environment.
  2. Become superuser.
  3. Change directory to the location of your proprietary MOF files.
  4. Use the mofcomp command to compile each of your proprietary MOF files.
    # /usr/sadm/bin/mofcomp root root-passwd MOF-filename

    Note - For more information on the MOF compiler, see mofcomp(1M).


  5. Stop the CIM Object Manager.
    # /etc/init.d/init.wbem stop
  6. Start the CIM Object Manager.
    # /etc/init.d/init.wbem start

    The CIMOM adds repository files that contain the converted data to the directory /var/sadm/wbem/logr/. This directory was created when you upgraded your system to the Solaris 9 operating environment.

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.