init.wbem(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | NOTES | EXAMPLES | ATTRIBUTES | SEE ALSO

NAME

init.wbem– start and stop the CIM Boot Manager

SYNOPSIS

/etc/init.d/init.wbem start | stop | status

DESCRIPTION

The init.wbem utility is run automatically during installation and each time the system is rebooted. This utility manipulates the CIM Object Manager (CIMOM) and the Solaris Management Console server, both of which run combined in a single process. init.wbem can be used to start, stop, or retrieve status from the server.

CIM Object Manager

The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a computer representation, or model, of a managed resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes.

When a WBEM client application accesses information about a CIM object, the CIM Object Manager contacts either the appropriate provider for that object or the CIM Object Manager Repository. Providers are classes that communicate with managed objects to access data.

When a WBEM client application requests data from a managed resource that is not available from the CIM Object Manager Repository, the CIM Object Manager forwards the request to the provider for that managed resource. The provider dynamically retrieves the information.

At startup, the CIM Object Manager performs the following functions:

• Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 80.

• Sets up a connection to the CIM Object Manager Repository.

• Waits for incoming requests.

During normal operations, the CIM Object Manager performs the following functions:

• Performs security checks to authenticate user login and authorization to access namespaces.

• Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification.

• Routes requests to the appropriate provider or to the CIM Object Manager Repository.

• Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications.

A WBEM client application contacts the CIM Object Manager to establish a connection when it needs to perform WBEM operations, such as creating a CIM class or updating a CIM instance. When a WBEM client application connects to a CIM Object Manager, it gets a reference to the CIM Object Manager, which it then uses to request services and operations.

Solaris Management Console Server

The Solaris Management Console server is the back end to the front end console, smc(1M). It provides tools for the console to download and performs common services for the console and its tools to use, such as authentication, authorization, logging, messaging, and persistence.

System Booting

The init.wbem script is installed in the /etc/init.d directory. A link to it exists in /etc/rc2.d/S90wbem, which is run with the start option when init state 2 is entered (normally at boot time). Other links to it exist in /etc/rc0.d/K36wbem, /etc/rc1.d/K36wbem, and /etc/rcS.d/K36wbem, which are run with the stop option when init states 0, 1, and S are entered (normally at system halt, or when entering “system administrator mode” or single user mode).

OPTIONS

The following options are supported:

start

Starts the CIMOM and Solaris Management Console server on the local host.

stop

Stops the CIMOM and Solaris Management Console server on the local host.

status

Gets the status of the CIMOM and Solaris Management Console server on the local host.

NOTES

When the init.wbem script is run, it does not run the CIMOM and Solaris Management Console server directly. The server process is in Java and is too heavyweight to be run immediately at system boot time. Instead, a lightweight process is run which listens on the ports the CIMOM and the Solaris Management Console server normally use, running the two servers the first time it gets a connection on either port, thus acting similarly to inetd(1M).

Because Java programs cannot inherit file descriptors as other programs can, there is a small time period from when the first connection is made until the server is fully operational where client connections may be dropped. WBEM clients are immune to this, as they will retry until the server comes online. Solaris Management Console clients are not immune, and it may be necessary to manually reconnect, though this should not happen in the common case.

EXAMPLES

---

Example 1 Restarting the Solaris Management Console server after enabling users on untrusted clients to assume a role




The start and stop options can be used to restart the SMC server, as is necessary when enabling users on untrusted clients to assume a role via the SMC login dialog.

1. Assume the secadmin role.

2. Edit the file /usr/sadm/lib/smc/bin/smcwbemserver and change

   com.sun.management.viperimpl.server.ViperWbemServer “$@” |&

   to

   com.sun.management.viperimpl.server.ViperWbemServer “$@” -u |&

3. Restart the Solaris Management Console server.

   $ /etc/init.d/init.wbem stop $ /etc/init.d/init.wbem start

See the Trusted Solaris Administrator's Procedures for details of this procedure.

---

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWwbcor

SEE ALSO

Trusted Solaris 8 HW 12/02 Reference Manual

inetd(1M), smc(1M)

SunOS 5.8 Reference Manual

mofcomp(1M), smcconf(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | NOTES | EXAMPLES | ATTRIBUTES | SEE ALSO