IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Situation event integration with Tivoli Enterprise Console

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Update the XML used by the MCS Attribute Service

The default XML file used by the Multiple Console Support (MCS) Attribute Service includes only the event classes defined in the BAROC files within the TECLIB branch of the hub monitoring server installation. Generate a new XML file for EIF Slot Customization whenever a new type of agent is added into the Tivoli Management Services infrastructure or when a new event class has been added into the Tivoli Enterprise Console event server.

If an event class specified for a rule is not found within the current event class definition set and you continue building the rule with the current definition set, any unrecognized event classes will be removed from the rule.

The EIF Event Customization facility uses the MCS Attribute Service to present a list of predefined event classes in the Event class name list of the EIF Slot Customization window, which is available through the EIF tab of the Tivoli Enterprise Portal Situation editor. Only the event classes belonging to the OS agents are predefined and they are in an MCS Attribute Service jar file. When a new type of agent is added into the Tivoli Management Services infrastructure or a new event class is added for an agent, you must generate a new MCS XML file and point the Tivoli Enterprise Portal Server to the new XML file before the new event classes will appear in the Event class name list.

To generate a new MCS XML file, install the Tivoli Enterprise Console Event Definition Generator (TEDGEN) utility supplied on the IBM Tivoli Monitoring Tools DVD. Install the TEDGEN utility on a distributed computer where the hub monitoring server or portal server is installed, or where the Tivoli Enterprise Console is installed. The computer on which you generate the MCS XML file must have the necessary BAROC files.

The definitions in MCS XML file supersede those defined in the shipped MCS Attribute Services jar file (they are not merged). To obtain a MCS XML file that contains both the event classes definitions of the OS agents as well as the new agent, be sure all the BAROC definitions for the OS agents and new agent are loaded at the IBM Tivoli Enterprise Console event server or are all in the same directory on the hub monitoring server or portal server before running the TEDGEN utility to generate the MCS XML file.

To install and configure the TEDGEN tool, perform these steps.

  1. Install the TEDGEN utility from the IBM Tivoli Monitoring Tools DVD on either the hub monitoring server, portal server or where the Tivoli Enterprise Console is installed. The utility is located in the tec/tedgen directory on the Tools DVD and the installation and configuration instructions are in the README.txt file in the same directory.

  2. If you installed the TEDGEN utility on a portal server on Linux or UNIX system, also perform these additional configuration steps:

    1. Create the install_dir/tables/cicatrsq/TECLIB directory if it does not exist, where install_dir is the directory where IBM Tivoli Monitoring is installed.

    2. Copy the om_tec.baroc and kib.baroc files from the install_dir/arch/cq/TECLIB directory to the install_dir/tables/cicatrsq/TECLIB directory, where arch is the architecture directory for the portal server.


These steps assume you have installed the TEDGEN utility on the computer where you want to run the tool: at the Tivoli Enterprise Console event server, the hub monitoring server or portal server.

You must also install the application support for the agents whose EIF events are customized on the hub monitoring server or portal server where you want to run the utility. To run the TEDGEN utility on the Tivoli Enterprise Console, you must also load the agent's BAROC files on the computer where the Tivoli Enterprise Console is installed.

After installing the utility and application support, then run the TEDGEN command to create a new XML file for EIF Slot Customization.


Procedure

  1. Complete one of the following steps to run the TEDGEN command:

    • On the computer where the hub monitoring server or portal server is located, issue these commands: 

        set CANDLE_HOME=install_dir     

        cd TEDGEN_Install_dir\scripts             

        tedgen -itmDir install_dir\{CMS|CNPS}
\TECLIB -id server_id -xmlPath output_xml_file_path

      where, install_dir is the directory where IBM Tivoli Monitoring is installed, and TEDGEN_Install_dir is the directory where the TEDGEN utility is installed.

        export CANDLEHOME=install_dir      

        cd TEDGEN_Install_dir/scripts 

        tedgen -itmDir 
install_dir/tables/{tems_name|cicatrsq}/
TECLIB -id server_id -xmlPath output_xml_file_path

      where, install_dir is the directory where IBM Tivoli Monitoring is installed, and TEDGEN_Install_dir is the directory where the TEDGEN utility is installed.

      Example

      In the following example, the hub monitoring server named mytems has the BAROC files in the TECLIB directory. The output file goes to the same directory and is named tems.xml. 

        tedgen -itmDir C:\IBM\ITM\CMS\TECLIB -id mytems -xmlPath tems.xml

    • On the computer where the Tivoli Enterprise Console event server is located, install the TEDGEN utility from the Tools DVD that comes with the event server installation media. Then create a new XML file:

      1. Issue the wrb -imprbclass command to import the BAROC file that is installed with a newly added agent, and OS agents if they are not already installed: 

          wrb -imprbclass class_file [ -encoding encoding ]
[-before class_file | -after class_file] [-force] rule_base

      2. Issue the wrb -loadrb command to reload the rulebase: 

          wrb -loadrb rule_base

      3. Stop and restart the event server by running these commands: 

          wstopesvr
wstartesvr

      4. Issue the TEDGEN command to generate the XML file: 

          tedgen [ -bcDir baroc_classes_directory | -rbName rule_base_name ]
-id server_id -xmlPath output_xml_file_path

      Example

      In the following example, the XML file named tec.xml is generated from the current rulebase on the Tivoli Enterprise Console event server named mytec. 

        tedgen -id mytec -xmlPath tec.xml

  2. Copy the newly generated XML file to the computer where the Tivoli Enterprise Portal Server is installed.

  3. Edit the portal server environment file to specify the path to the XML file:

    1. In the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli Enterprise Portal Server and click Advanced → Edit ENV File to open the kfwenv file in the text editor.
      Open install_dir/config/cq.ini in a text editor.

    2. Locate the KFW_MCS_XML_FILES environment variable and type = (equal sign) followed by the path to the MCS XML file.

    3. Save and close the environment file.

    4. Restart the portal server.
      Reconfigure the portal server and then restart it.


Parent topic:

Situation event integration with Tivoli Enterprise Console

+

Search Tips   |   Advanced Search