IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Understanding and Customizing the Event Contents > Generic mapping for agent-specific slots

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Customize the list of OMNIbus attributes that are cached

Perform the procedure in this section to customize the list of OMNIbus attributes that are cached when a sampled event is cleared or deleted after the new attribute has been added to the ObjectServer alerts.status table.

  1. Open the itm_event_cache.sql file using a text editor. This file is available in the event_sync_install_dir/omnibus where event_sync_install_dir is the directory where the IBM Tivoli Monitoring event synchronization component is installed.

  2. Find "--NewAttributeGoesHere type(size)". Copy the line, insert a new line immediately below, and paste the copied line. In the newly added line delete the characters "--", replace "NewAttributeGoesHere type(size)" with the new OMNIbus attribute name, type, and size.

  3. Find "--statusr.NewAttributeGoesHere,". Copy the line, insert a new line immediately below, and paste the copied line. In the newly added line delete the characters "--", replace "NewAttributeGoesHere" with the appropriate OMNIbus attribute name. Do not delete the comma (,) at the end of the line.

  4. Find "--set new.NewAttributeGoesHere = cachedevent.NewAttributeGoesHere ;". Copy the line, insert a new line immediately below, and paste the copied line. In the newly added line delete the characters "--", replace "NewAttributeGoesHere" with the appropriate OMNIbus attribute name. Do not delete the semicolon (;) at the end of the line.

  5. Execute the itm_event_cache.sql file to update the OMNIbus database schema using the instructions in Update the OMNIbus database schema on single-tier or aggregation tier ObjectServers. For complex situations, the situation definition can involve more than one attribute group. In this case, the EIF event class used is derived from the first attribute group encountered in the situation event data of the triggering situation. For example, if a situation is written for the NT_Process and Local Time attribute groups, NT_Process being the first attribute group, the EIF event class ITM_NT_Process is used. Additional event slots are generated based on the attributes of the first attribute group only.


    Special characters for attribute groups and names in EIF events generated from forwarded situation events.

    Character: Converts to:
    <uppercase> (applies only to attribute name) <lowercase> (applies only to attribute name)
    % percent sign pct_
    I/O io
    / forward slash _per_
    \ backward slash _ (underscore)
    <space> _ (underscore)

    ( open parenthesis

    ) close parenthesis

    		_ (underscore)

    < open pointed bracket

    > close pointed bracket

    		_ (underscore)

    All strings and time stamp types are mapped to STRING types, and all integer types are mapped to INTEGER in the event class definition. No default values are assigned to the attribute slots. Attributes that have a specified non-zero scale/precision value are mapped to the string type of REAL.

    If you are mapping from an attribute to a slot and the resulting slot name has a trailing underscore, the trailing underscore is removed in the final slot name. Final slot names never have a trailing underscore.


Parent topic:

Generic mapping for agent-specific slots

+

Search Tips   |   Advanced Search