Impact management in the Infrastructure Management Server Cell can generate events that notify you of changes to components in the service model. These events are called notification events. The following are the types of notification events:
SIM_COMPONENT_CHANGE
SIM_COMPONENT_DELETE
SIM_COMPONENT_OVERWRITE
SIM_RELATIONSHIP_CHANGE
SIM_RELATIONSHIP_DELETE
Note
In the mc_sm_notify.baroc file in installationDirectory/pw/server/etc/cellName/kb/classes, you can view the definitions of the SIM_NOTIFICATION_EVENT
base class and the event classes SIM_COMPONENT_CHANGE
, SIM_COMPONENT_DELETE
, SIM_COMPONENT_OVERWRITE
, SIM_RELATIONSHIP_CHANGE
, and SIM_RELATIONSHIP_DELETE
.
The SIM_COMPONENT_DELETE
and SIM_RELATIONSHIP_DELETE
events are generated when you remove a configuration item or an impact relationship from the published service model. The SIM_COMPONENT_CHANGE
and SIM_RELATIONSHIP_CHANGE
events are generated when a configuration item or an impact relationship is altered by the cell because of a change in status or priority.
Impact management in the BMC TrueSight Infrastructure Management Server Cell generates these notification events on request by a client. For example, the BMC Impact Portal can register to receive notification events just as a gateway client can. Another BMC TrueSight Infrastructure Management Server Cell or even the Impact management in the BMC TrueSight Infrastructure Management Server Cell containing the impact management model can register to receive notification events.
The following slots are reported:
1 Comment
Melody Locke