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


Edit the Event Integration Facility configuration

Edit the Tivoli Event Integration Facility EIF file to customize the configuration such as to specify up to five failover EIF servers or to adjust the size of the event cache.

After the Tivoli Event Integration Facility (EIF) has been enabled on the hub monitoring server and the default EIF server (Tivoli Enterprise Console event server or Netcool/OMNIbus EIF probe), and port number have been specified, the EIF configuration file is updated with the information. This configuration file specifies the default EIF receiver of forwarded situation events.

See the Tivoli Event Integration Facility Reference for more details on the parameters and values.

If you are enabling EIF after your environment has been installed and configured, you must enable EIF through Manage Tivoli Enterprise Monitoring Services or with the CLI itmcmd config -S and then recycle the monitoring server and portal server.

See the IBM Tivoli Monitoring Installation and Setup Guide for instructions on configuring the monitoring server to enable the Tivoli Event Integration Facility.


Take these steps to edit the EIF configuration file:


Procedure

  1. Open the om_tec.config file:

    • In the Manage Tivoli Monitoring Services window, right-click Tivoli Enterprise Monitoring Server and click Advanced → Edit EIF Configuration.

    • Open install_dir/tables/host name/TECLIB/om_tec.config in a text editor.

  2. Edit any of the event server configuration parameters for the event integration facility.

    Option Description
    ServerLocation= This is the host name or ip address of the event server. To provide event failover, you can indicate up to five default event servers, separating each with a comma. When the default event server is unavailable, the situation event goes to the next server in the list.
    Value: tec_server_addr
    ServerPort= The event server listening port, which is 5529 by default. Specify 0 if the event server uses the port mapper. If you specified multiple server locations, add the corresponding port numbers here, separating each with a comma.
    Value: [port:0]
    EventMaxSize= Maximum number of characters allowed in the event. This number is disabled by default. To enable it, remove the # (pound symbol) at the beginning of the line.
    Value: 4096
    RetryInterval= Number of times to retry connection with the event server before returning an error.
    Value: 5
    getport_total_timeout_usec= Number of seconds to continue attempting to connect to the event server port before timing out. The default is 14 hours.
    Value: 50500
    NO_UTF8_CONVERSION= Events are already in UTF8 format; no conversion is needed. This parameter must be set to YES.
    Value: YES
    ConnectionMode= The connection mode.
    Value: co
    BufferEvents= Whether the EIF buffers the event. This must be set to YES.
    Value: YES
    BufEvtMaxSize= Maximum size of the event cache. The default is initially 4096 KB and you can change it here.
    Value: 4096
    BufEvtPath= Path of the event cache file. The default is ./TECLIB/om_tec.cache.
    Value: ./TECLIB/om_tec.cache
    FilterMode= Enable event filtering. This is set to OUT by default.
    Value: OUT
    TcpTimeout= Use this parameter for connection-oriented mode that allows the agent to timeout the connect call with the primary server if it is not available, and then failover to the secondary server. For example, use this parameter when a firewall blocks ICMP Ping calls. The value is in seconds.
    Value: 75

    Restriction: This cannot be used with parameters PingTimeout and NumberOfPingCalls.

    PingTimeout= The maximum timeout for the ping call to try to access the destination server. If the PingTimeout is not specified, a ping call is not executed by the EIF before calling the socket connect call. This parameter can be used with connection-less or connection-oriented connection types. This parameter must be used with NumberOfPingCalls. The value is in seconds.
    Value: 75

    Restriction: This cannot be used with parameter TcpTimeout.

    NumberOfPingCalls= Number of times the ping function should be invoked before determining the destination server is available. Due to some TCP/IP configurations, the very first ping call after the destination server is unplugged can return successfully. This parameter can be used with connection-less or connection-oriented connection types. This parameter must be used with PingTimeout.

    Restriction: This cannot be used with parameter TcpTimeout.

    Filter: To filter out specific classes, use this keyword. By default, situation events of the class ITM_Generic and those that send no master reset flag are not forwarded.
    Value: Class=ITM_Generic; master_reset_flag='';

  3. When you are finished editing om_tec.config, save the file.

  4. You must restart the monitoring server or, alternatively, you can use the refreshTECinfo command to complete the updates without having to restart the monitoring server. To use this command, log into the command-line interface with tacmd login , then run tacmd refreshTECinfo -t eif to complete the EIF configuration.


Results

The monitoring server uses the edited EIF configuration to forward event to the receiver.


What to do next

If this is the first time that you have configured the EIF forwarding after a Tivoli Management Services upgrade, you also must recycle the Tivoli Enterprise Portal Server and users must restart the Tivoli Enterprise Portal. Otherwise, the EIF tab will be missing from the Situation editor.

An alternative method for editing the EIF configuration is provided through the Command Line Interface tacmd createEventDest. See the IBM Tivoli Monitoring Command Reference for a description.


Parent topic:

Situation event integration with Tivoli Enterprise Console

Related reference:

Tivoli Event Integration Facility Reference
Tivoli Monitoring Installation and Setup Guide
Tivoli Monitoring Command Reference


+

Search Tips   |   Advanced Search