| 跳过导航链接 | |
| 退出打印视图 | |
|
手册页第 1M 部分：系统管理命令 Oracle Solaris 11.1 Information Library (简体中文) |
| 跳过导航链接 | |
| 退出打印视图 | |
|
|
手册页第 1M 部分：系统管理命令 Oracle Solaris 11.1 Information Library (简体中文) |
- compile MOF files into CIM classes
/usr/sadm/bin/mofcomp [-c cimom_hostname ] [-h]
[-j filename] [-n namespace] [-o dirname]
[-p password ] [-CIQ] [-u username] [-v ] [-version]
[-x] fileThe 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 collection 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 equivalent privileges, or as a user with write access to the namespace in which you are compiling. When performing a privileged operation, you must enter the -u or -u and -p options, which are described below.
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.
The following options are supported:
Specify a remote system running the CIM Object Manager.
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.
List the arguments to the mofcomp utility.
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.
Generate Java Beans and Java Interfaces to manage 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 separated list of valid Java exceptions to be thrown by the methods in all generated Java source.
Requests that the compiler load the MOF file into the namespace specified as namespace. The default namespace (root\cimv2) is used unless this switch is used or a #pragma namespace (namespace) statement appears in the MOF file. If both the -n namespace switch and the #pragma namespace construct are used, all namespaces are created, but the objects are created only in the #pragma namespaces.
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.
Specify a password for connecting to the CIM Object Manager. Use this option for compilations 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.
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.
Specify user name for connecting to the CIM Object Manager. Use this option for compilations 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.
Run the compiler in verbose mode, which displays compiler messages.
Display the version of the MOF compiler.
Generate XML documents for the CIM classes defined in the input MOF file.
The following operands are supported:
The pathname of the file to be compiled.
The mofcomp utility exits with 0 upon success and a positive integer upon failure.
MOF files are installed in /usr/sadm/mof.
See attributes(5) for descriptions of the following attributes:
|
init.wbem(1M), mofreg(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5), wbem(5)
|