IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Installation and configuration

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Install from a wizard

This section outlines the steps for installing event synchronization from a wizard.

  1. On the computer where the ObjectServer is installed, launch the event synchronization installation:

    • Double-click the ESync3000Win32.exe file in the tec subdirectory on the IBM Tivoli Monitoring Tools DVD or DVD image.

    • Change to the tec subdirectory on the IBM Tivoli Monitoring Tools DVD or DVD image and run the following command:

        ESync3000operating_system.bin

      where operating_system is the operating system you are installing on (Aix, HP11, Linux, linux390, or Solaris). For example, run on an AIX computer:

        ESync3000Aix.bin

      If the installer cannot locate OMNIbus in its usual place, the following window is displayed. Click Next to continue installing the event synchronization:

      Figure 1. Installation of IBM Tivoli Monitoring and Tivoli Event Synchronization

  2. Click Next on the Welcome window.

  3. Review the license agreement, select I accept the terms in the license agreement and click Next.

  4. Click Next to install the synchronization component in the default location, or use the Browse button to select another location.

    • The default installation directory is C:\Program Files\IBM\SitForwarder.

    • The default installation directory is /opt/IBM/SitForwarder.

    Click Next to continue.

  5. Complete the fields in the installation windows using the configuration values described in Table 1 and click Next.

    Figure 2. Netcool/OMNIbus event synchronization configuration fields

    Field Description
    Name of configuration file For bidirectional architecture only: The name of the file where the IBM Tivoli Monitoring Situation Update Forwarder configuration information is stored. The default name is situpdate.conf.
    Number of seconds to sleep when no new situation updates For bidirectional architecture only: The polling interval, in seconds used by the IBM Tivoli Monitoring Situation Update Forwarder to determine if there are new event updates to send from Netcool/OMNIbus to the hub Tivoli Enterprise Monitoring Server. The minimum value is 1, while the default value is 3. If no situation events are found, the IBM Tivoli Monitoring Situation Update Forwarder rests for 3 seconds.
    Number of bytes to use to save last event For bidirectional architecture only: Number of bytes that the IBM Tivoli Monitoring Situation Update Forwarder uses when it saves the location of the last event it processes. This value must be an integer. The minimum (and default) value is 50.
    URL of the Tivoli Enterprise Monitoring Server SOAP server For bidirectional architecture only: The URL for the SOAP server configured on the computer where the hub monitoring server is running. The default value is cms/soap. Do not change this value. The actual URL for the SOAP server is dynamically constructed from the incoming event.
    Rate for sending SOAP requests to the monitoring server from the OMNIbus probe via web services For bidirectional architecture only: The maximum number of event updates sent by the IBM Tivoli Monitoring Situation Update Forwarder to the hub monitoring server at one time. The minimum (and default) value is 10 events.
    Level of debug detail for log For bidirectional architecture only: The level of information for event synchronization that is logged. The following choices are available:

    • Low (default)

    • Medium

    • Verbose

  6. Complete the fields on the installation window using the values described in Table 2 and click Next.

    Field Description
    Maximum size of any single cache file For bidirectional architecture only: The maximum permitted size, in bytes, for any one event cache file used by the IBM Tivoli Monitoring Situation Update Forwarder. The minimum (and default) value is 50000. Do not use commas when specifying this value (specify 50000 instead of 50,000).
    Maximum number of caches files For bidirectional architecture only: The maximum number of event caches files at any given time used by the IBM Tivoli Monitoring Situation Update Forwarder. The minimum value is 2, while the default value is 10. When this value is reached, the oldest file is deleted to make room for a new file.
    Directory for cache files to be located For bidirectional architecture only: The location where IBM Tivoli Monitoring Situation Update Forwarder event cache files are located. The default locations are as follows:

    • C:\Program Files\IBM\SitForwarder\persistence.

    • /opt/IBM/TEC/SitForwarder/persistence

  7. Type the following information for each hub monitoring server to use bidirectional synchronization and click Add. You must specify information for at least one hub monitoring server even if you are only using unidirectional synchronization.

    Host name

    The fully qualified host name for the computer where the hub monitoring server is running. The name must match the information that will be in events coming from this hub monitoring server.

    User ID

    The user ID to access the computer where the hub monitoring server is running.

    Password

    The password to access the computer.

    Confirmation

    The password, again.

    Repeat this step to add a short host name for the same hub monitoring server by specifying the short host name value for the Host name parameter. You can add information for up to 10 hub monitoring servers host names in this wizard. If you want to add additional monitoring servers, do so after installation using the steps outlined in Defining additional monitoring servers to the event server in Set up event forwarding to Tivoli Enterprise Console. If you have configured the Hot Standby feature, you must configure the host name information for both the primary and secondary hub monitoring servers.

  8. When you have provided information about all of the monitoring servers, click Next.

    A summary window is displayed.

  9. Click Next to proceed. The installation begins and a progress indicator is displayed. When the installation is completed, a message is displayed telling you that the installation has been successful.

  10. Click Finish to exit the wizard.


What to do next

If any configuration errors occurred during installation and configuration, you are directed to a log file that contains additional troubleshooting information.


Parent topic:

Installation and configuration

+

Search Tips   |   Advanced Search