mofcomp(1M) System Administration Commands mofcomp(1M)NAMEmofcomp - compile MOF files into CIM classes
SYNOPSIS
/usr/sadm/bin/mofcomp [-c cimom_hostname ] [-h] [-j filename] [-n
namespace] [-o dirname] [-p password ] [-CIQ] [-u username] [-v ]
[-version] [-x] file
DESCRIPTION
The mofcomp utility is executed during installation to compile managed
object format (MOF) files that describe the Common Information Model
(CIM) and Solaris Schemas into the CIM Object Manager Repository, a
central storage area for management data. The CIM Schema is a collec‐
tion of class definitions used to represent managed objects that occur
in every management environment. The Solaris Schema is a collection of
class definitions that extend the CIM Schema and represent managed
objects in a typical Solaris operating environment.
The mofcomp utility must be run as root or as a user with write access
to the namespace in which you are compiling.
MOF is a language for defining CIM classes and instances. MOF files are
ASCII text files that use the MOF language to describe CIM objects. A
CIM object is a computer representation or model of a managed resource,
such as a printer, disk drive, or CPU.
Many sites store information about managed resources in MOF files.
Because MOF can be converted to Java, Java applications that can run on
any system with a Java Virtual Machine can interpret and exchange this
information. You can also use the mofcomp utility to compile MOF files
at any time after installation.
OPTIONS
The following options are supported:
-c cimom_hostname Specify a remote system running the CIM Object
Manager.
-C Run the compiler set with the class option,
which updates a class if it exists, and returns
an error if the class does not exist. If you do
not specify this option, the compiler adds a
CIM class to the connected namespace, and
returns an error if the class already exists.
-h List the arguments to the mofcomp utility.
-I Run the compiler set with the instance option,
which updates an instance if it exists, and
returns an error if the instance does not
exist. If you do not specify this option, the
compiler adds a CIM instance to the connected
namespace, and returns an error if the instance
already exists.
-j filename Generate Java Beans and Java Interfaces to man‐
age the CIM instances related to the CIM
classes in the MOF being compiled.
The contents of filename are:
PACKAGE=Java package name
IMPORTS=import1:...:importN
<EXCEPTIONS=exception1:...:exceptionN
PACKAGE is a valid Java package name to include
in all generated Java source. IMPORTS is an
optional colon separated list of valid Java
classes to be imported in all generated Java
source. EXCEPTIONS is an optional colon sepa‐
rated list of valid Java exceptions to be
thrown by the methods in all generated Java
source.
-n namespace Requests that the compiler load the MOF file
into the namespace specified as namespace. The
default namespace (rootthis switch is used or a
#pragma namespace ("namespace") statement
appears in the MOF file. If both the -n names‐
pace switch and the #pragma namespace construct
are used, all namespaces are created, but the
objects are created only in the #pragma names‐
paces.
-o dirname Run compiler in standalone mode, without the
CIM Object Manager. Specify dirname as the
directory in which the compiler output is to be
stored. In this mode, the CIM Object Manager
need not be running.
-p password Specify a password for connecting to the CIM
Object Manager. Use this option for compila‐
tions that require privileged access to the CIM
Object Manager. If you specify both -p and -u,
you must type the password on the command line,
which can pose a security risk. A more secure
way to specify a password is to specify -u but
not -p, so that the compiler will prompt for
the password.
-Q Run the compiler set with the qualifier types
option, which updates a qualifier type if it
exists, and returns an error if the qualifier
type does not exist. If you do not specify this
option, the compiler adds a CIM qualifier type
to the connected namespace, and returns an
error if the qualifier type already exists.
-u username Specify user name for connecting to the CIM
Object Manager. Use this option for compila‐
tions that require privileged access to the CIM
Object Manager. If you specify both -p and -u,
you must type the password on the command line,
which can pose a security risk. A more secure
way to specify a password is to specify -u but
not -p, so that the compiler will prompt for
the password.
-v Run the compiler in verbose mode, which dis‐
plays compiler messages.
-version Display the version of the MOF compiler.
-x Generate XML documents for the CIM classes
defined in the input MOF file.
OPERANDS
The following operands are supported:
file The pathname of the file to be compiled.
EXIT STATUS
The mofcomp utility exits with 0 upon success and a positive integer
upon failure.
FILES
MOF files are installed in /usr/sadm/mof.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
┌─────────────────────────────┬─────────────────────────────┐
│ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
├─────────────────────────────┼─────────────────────────────┤
│Availability │SUNWwbcor │
└─────────────────────────────┴─────────────────────────────┘
SEE ALSOinit.wbem(1M), mofreg(1M), wbemadmin(1M), wbemlogviewer(1M),
attributes(5), wbem(5),
SunOS 5.10 28 Jan 2002 mofcomp(1M)
