Administrator's and User's Guide for SFM HP-UX 11i v3 March 2012

4. 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.
5. 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.
NOTE:
a. Only those indications that are generated by the SFMIndicationProvider in the SFM
monitoring mode, can be directed to the EMS framework through the WBEM Wrapper
Monitor. Indications generated by the EMS Wrapper provider in the EMS monitoring
mode, cannot be directed to the EMS framework.
b. You can continue to receive all events from EMS Hardware Monitors through the EMS
framework along with the indications on EVWEB and CMS.
The following list describes the sequence of events when an event is generated by EVM:
1. EVWEB and CMS subscriptions are created.
2. The EVM CIM provider receives events posted by the posting clients through the EVM Daemon.
3. The provider converts these events into WBEM indications and reports these indications to the
CIMOM.
4. 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.
Architecture 17