TBSM Event Mapping

Event Mapping

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:

• The BSM_Identity field maps to a value that identifies which service the event affects. The below table shows the default mappings for the supported event sources. One can use this field’s value to help identify service-affecting events in one’s TBSM incoming status rules.
• The BSM_ClassName field is reserved for future use. For TBSM 4.1, the BSM_ClassName field is set to null.

Event Source Default Mappings:

Event correlation

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:

• TEMS – The Tivoli Enterprise Monitoring Server identifies situations from criteria predefined by the ITCAM for Applications Agent. 

• EIF Emitter – The EIF Emitter sends a message in the “Event Integration Facility” protocol to the EIF Probe.

• EIF Event Transmission – The EIF Event Transmission sent by the EIF Emitter carries information in a set of standard fields.

• EIF Probe – The EIF Probe receives EIF Event Transmissions with standard fields and, with the help of “.rules” files, sends an Enanced EIF Event Transmission to the OMNIBUS / Netcool Object Server.

• tivoli_eif.rules – The tivoli_eif.rules file is referenced by the EIF Probe when enhancing EIF Event Transmissions. One common task of the file is to remove single quotes from strings. The file also makes reference to the kub.rules file.

• kub.rules – The kub.rules file is generated from the kub.baroc file with the help of omnibusUpdater.sh. The kub.rules file defines mappings from the EIF Event Transmission fields to the Enhanced EIF Event Transmission fields.

• omnibusUpdater.sh – The omnibusUpdater.sh script takes the kub.baroc file as a parameter and produces the kub.rules file. It also edits the tivoli_eif.rules file to include the kub.rules file.

• Enhanced EIF Event Transmission – The Enanced EIF Event Transmission sent by the EIF Probe to the OMNIBUS / Netcool Object Server carries information in a set of custom fields defined by “.rules” files.

• OMNIBUS / Netcool Object Server – The OMNIBUS / Netcool Object Server receives the Enhanced EIF Event Transmission and adds it to the Object Server database. This information is represented by a BSM Field List which can be read by TBSM.

• BSM Field List – The BSM Field List is created by the OMNIBUS / Netcool Object Server and read by TBSM. It includes a “BSM_Identity” field.

• TBSM – The TBSM reads the BSM Field List provided by the OMNIBUS / Netcool Object Server and the BSM_Identity provided by XMLToolkit. The value of the “BSM_Identity” field in the BSM Field List must match that of an existing TBSM “Service Component” (provided by XMLToolkit) in order for the situation it represents to be mapped correctly.

• BSM_Identity – The BSM_Identity of each TBSM Service Component is provided by the XMLToolkit. Its value must be referenced by each situation that applies to it in order for correct mapping to occur.

• XMLToolkit – The XMLToolkit parses the IdML Book with the help of the EventIdentifierRules.xml file and provides a description of each Service Component to TBSM.

• LabelingRules.xml – The LabelingRules.xml is an XMLToolkit configuration file used by TBSM to give each Service Component a label.

• EventIdentifierRules.xml – The EventIdentifierRules.xml file defines a BSM_Identity mapping for each TBSM Service Component described by the IdML Book.

• IdML Book – The IdML Book describes the TBSM Service Components monitored by the ITCAM for Applications Agent. It is created from the TMSDLA with the help of the tmsdla.sh script and is read by the XMLToolkit.

• tmsdla.sh – The tmsdla.sh script uses the TMSDLA to create the IdML Book which describes the TBSM Service Components monitored by the ITCAM for Applications Agent.

• ITCAM for Applications Agent – The ITCAM for Applications Agent includes the TMSDLA, the kub.baroc file, defines the Custom Situation, and monitors TBSM Service Components.
• TMSDLA – The TMSDLA contains standards regarding how the TBSM Service Components monitored by the ITCAM for Applications Agent should be represented in the IdML Book.

• Custom Situation – The Custom Situation is described by the ITCAM for Applications Agent and defines the values of the fields sent by the EIF Emitter.

• kub.baroc – The kub.baroc file is included in the ITCAM for Applications Agent. It is used by the omnibusUpdater.sh script to generate the kub.rules file.

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://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamt.doc_7.2/rt/User%20Guide/TBSM/tbsm_ref_omnibus.html

http://www.redbooks.ibm.com/abstracts/sg247878.html?Open

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.tivoli.itbsm.doc_4.1/bsma_evtc_itm.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.tivoli.itbsm.doc_4.1/bsma_evtc_tivolieifprobe.htm