|
These three functions provide component communication with the DMI through the Component Interface (CI).
Component instrumentation code may register with the Service Provider to override its current mechanism for the registered attributes. Instead of manipulating the data in the MIF database or invoking
programs, the Service Provider calls the entry points provided in the registration call. Once the component unregisters, the Service Provider returns to a normal method of processing requests for the
data as defined in the MIF. Component instrumentation can temporarily interrupt normal processing to perform special functions.
Registering attributes through the direct interface overrides atttributes that are already being served through the direct interface. RPC is used for communication from the Service Provider to the
component instrumentation.
For all three functions, argin is the parameter passed to initiate an RPC call, result is the result of the RPC call, and dmi_rpc_handle
is an open session RPC handle.
The DmiRegisterCi() function registers a callable interface for components that have resident instrumentation code and/or to get the version of the Service Provider.
The DmiUnRegisterCi() function communicates to the Service Provider to remove a direct component instrumentation interface from the Service Provider table of registered interfaces.
The DmiOriginateEvent() function originates an event for filtering and delivery. Any necessary indication filtering is performed by this function (or by subsequent processing)
before the event is forwarded to the management applications.
A component ID value of zero (0) specifies the event was generated by something that has not been installed as a component, and has no component ID.
|
