All the event mapping necessary to map Tivoli Enterprise Console, Tivoli NETVIEW, and Tivoli Monitoring event fields to ObjectServer fields is pre-configured in the tivoli_eif.rules file, the default rule file used by the EIF probe. The events forwarded from these sources contain the following special fields:
Event Source Default Mappings:
Tivoli Enterprise Console |
@BSM_Identity = $origin |
Tivoli Monitoring |
@BSM_Identity = $situation_origin |
Tivoli NETVIEW |
@BSM_Identity = $origin |
Each TBSM Service Component in one’s service model can have one of more unique service identifiers. These service identifier values are assigned the BSM_Identity attribute of a Service Component. In TBSM incoming status rules, one can use the event’s BSM_Identity field value to match a Service Component’s BSM_Identity value to determine the events that affect a service. For more information on incoming status rules, see the IBM Tivoli Business Service Manager Service Configuration Guide and IBM Tivoli Business Service Manager Scenarios Guide. The mechanism by which events are mapped to TBSM Service Components is represented in the below image.
Element details are as follows:
references: http://www.ibm.com/developerworks/wikis/display/tivolibsm/Enriching+IBM+Tivoli+Monitoring+%28ITM%29+Events+For+IBM+Tivoli+Business+Service+Manager+%28TBSM%29 http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.tivoli.itbsm.doc/common/tbsm_c_product_architecture.html,
http://www.redbooks.ibm.com/abstracts/sg247878.html?Open