Relation of *.baroc files and *.map files

All the OMEGAMON products use the *.baroc files. The ks3.baroc file is the only *.baroc file in OMEGAMON® for Storage. With the related ks3.map file, however, you can customize the event data IBM Tivoli Monitoring forwards to a listening event integration facility (EIF), such as the Tivoli Enterprise Console server.

*.baroc file

The *.baroc file is required for event forwarding from IBM® Tivoli® Enterprise Monitoring Agent to IBM Tivoli Enterprise Console. It is not required for event forwarding to Tivoli Netcool/OMNIbus. You must install the file into the IBM Tivoli Enterprise Console rulebase before the server receives the monitored events.

*.map file

The *.map file controls the event data from IBM Tivoli Enterprise Monitoring Agent forwarded to a listening event integration facility (EIF). You can use it to control event forwarding to both Tivoli Netcool/OMNIbus servers and Tivoli Enterprise Console servers, because both are EIFs. You must synchronize it with a corresponding *.baroc file whenever event handling for IBM Tivoli Enterprise Console is modified.

You can also modify the *.map file to decrease the event data volume forwarded to the listening EIF servers. This capability to decrease the volume is useful for IBM Tivoli Enterprise Console in the following scenarios:

• When an event attribute table of a situation in IBM Tivoli Enterprise Monitoring Agent contains large numbers of attributes.
• When you are monitoring an event, which can produce multiple sub-objects, and you want to reduce the number of attributes that are forwarded for the event.

You can adjust the *.map file to prevent hidden event attributes from passing when the event is triggered. As a result, less data is forwarded to an IBM Tivoli Enterprise Console server.

You must apply the corresponding changes to the *. baroc file, so that event data handling by both the files remains synchronized.