 |
» |
|
|
|
Figure 1-1 illustrates the
architecture of SFM installed on a client system. The client system
is managed by the CMS. The following list describes the sequence of events when a request
is made for information: The CIMOM receives requests from the CMS for information about
devices. The CIMOM directs the requests to the appropriate
SFM provider, for example, the CPU Instance Provider. The SFM provider queries the associated hardware device
for property information. The SFM provider returns the query information to
the CIMOM. The CIMOM conveys the responses from the provider
to the CMS. You can view the information using HP SIM
on the remote system and HP SMH on the local system.
The following list describes the sequence of events when an
event is generated from an EMS monitor: EVWEB and CMS subscriptions are created. The EMS Wrapper Provider receives events generated
by the EMS monitors through the EMS framework. The provider converts these events into WBEM indications
and reports these indications to the CIMOM. CIMOM directs these indications to the CMS that has
created subscriptions for indications. EVWEB retrieves the errors
that occurred on the local system and stores the indications either
in the Event Archive or in your E-mail box, or both, depending on
your configuration. You can view indications using HP
SIM on the remote system and HP SMH on the local system.
The sequence of events if you choose to use the
SFMIndicationProvider instead of the EMS monitors it substitutes,
is as follows: EVWEB and CMS subscriptions are created. The SFMIndicationProvider generates WBEM indications
that are triggered by errors on devices that it monitors. The provider reports these WBEM indications to the
CIMOM. The CIMOM directs these indications to EVWEB and to
the CMS that has created subscriptions for indications. EVWEB then
stores the indications either in the Event Archive, in syslog, or
in your E-mail box, or all, depending on your configuration. Indications can be viewed using HP SIM on the remote system
and HP SMH on the local system. The indications generated by the SFMIndicationProvider,
and reported to the CIMOM, can also be directed to the EMS framework
through the WBEM Wrapper Monitor. The WBEM Wrapper Monitor converts
the WBEM indications into EMS events and directs them to the EMS framework. EMS clients can receive these events, along with the other events
generated by the EMS monitors, through the EMS framework.
The following list describes the sequence of events when an
event is generated by EVM: EVWEB and CMS subscriptions are created. The EVM CIM Provider receives events posted by the
posting clients through the EVM Daemon. The provider converts these events into WBEM indications
and reports these indications to the CIMOM. CIMOM directs these indications to EMT and the CMS
that has created subscriptions for indications. EVWEB retrieves the
errors that occurred on the local system and stores the indications
either in the Event Archive, in syslog, or in your E-mail box, or
all, depending on your configuration. You can view indications
using HP SIM on the remote system and HP SMH on the local system.
|
Printable version
