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 the command-line using a silent installation

This installation method runs silently, so you do not see status messages during the actual installation.

Install the event synchronization using a silent installation from the command-line on your event server.

  1. Change to the tec directory on the IBM Tivoli Monitoring Tools DVD or DVD image.

  2. Run the following command to generate the configuration file:

      Sync3000Win32.exe -options-template filename

    ...where filename is the name of the configuration file to create, for example, es_silentinstall.conf.

      Sync3000operating_system.bin -options-template filename

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

      Sync3000Aix.bin -options-template filename

  3. Edit the output file to specify the values described in Table 1.

    1. Remove the number signs (###) from the beginning of any value that you want to specify.

    2. You must specify the following values: 

        ### -P installLocation="value"
### -W configInfoPanel3.fileLocn="value"

      ...and the following information for at least one monitoring server:

        cmdSvrsPnlNotGuiMode.hostname1,
        cmdSvrsPnlNotGuiMode.userID1
        cmdSvrsPnlNotGuiMode.pswd1
        cmdSvrsPnlNotGuiMode.retypePswd1

      If you do not specify any of the other values, the default values are used. If you specify values, ensure that the values you specify meets the minimum required values. Otherwise, the installation stops and an error is written to the log file.

    Value Description
    installLocation The directory where you want to install the product. If the directory path contains spaces, enclose it in double quotation marks (" "). For example, to install the product to C:\Program Files\My Product, use

      -P installLocation="C:\Program Files\My Product"

    On Windows systems, the default installation directory is:

      C:\Program Files\IBM\SitForwarder

    On Linux/UNIX systems, the default installation directory is:

      /opt/IBM/SitForwarder

    configInfoPanel.filename For bidirectional architecture only: The name of the file where IBM Tivoli Monitoring Situation Update Forwarder configuration information is stored. The default file name is situpdate.conf.
    configInfoPanel.pollingInt 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 there are no situation events, the IBM Tivoli Monitoring Situation Update Forwarder rests for 3 seconds.
    configInfoPanel.crcByteCnt 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.
    configInfoPanel.cmsSoapURL 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.
    configInfoPanel.bufFlushRate For bidirectional architecture only: The maximum number of event updates to be 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.
    configInfoPanel.logLevel For bidirectional architecture only: The level of debug information for the IBM Tivoli Monitoring Situation Update Forwarder that is logged. You have the following choices:

    • Low (default)
    • Medium
    • Verbose

    configInfoPanel3.filesize 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 (50,000 instead of 50000).
    configInfoPanel3.fileNumber 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.
    configInfoPanel3.fileLocn For bidirectional architecture only: The location where IBM Tivoli Monitoring Situation Update Forwarder event cache files are located. The default locations are as follows:

    • On Windows: C:\Program Files\IBM\SitForwarder\persistence.
    • On UNIX: /opt/IBM/SitForwarder/persistence

    cmsSvrsPnlNotGuiMode.hostname#

    The pound sign (#) stands for a number 1 - 10. For example, "hostname1".

    		For bidirectional architecture only: The host name of each hub monitoring server that sends events to the event server. For each hub monitoring server, specify one property with the monitoring server's fully qualified hostname and specify another property with the monitoring server's short hostname. Specify up to 10 monitoring server host names. If you have configured the Hot Standby feature, you must configure the host name information for both the primary and secondary hub monitoring servers.
    cmsSvrsPnlNotGuiMode.userID# For bidirectional architecture only: The user ID for the hub monitoring server, identified in host name#, to use to access the computer where the monitoring server is running.
    cmsSvrsPnlNotGuiMode.pswd# For bidirectional architecture only: The password for the user ID used to access the computer where the hub monitoring server is running.
    cmsSvrsPnlNotGuiMode.retypePswd# For bidirectional architecture only: The password confirmation for the user ID.

  4. Save the file.

  5. Run the following command:

      ESync3000Win32.exe -options filename -silent

    ...where filename is the name of your configuration file.

      ESync3000operating_system.bin -options filename -silent

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

      ESync3000Aix.bin -options filename -silent


Results

When installation is complete, the results are written to the itm_tec_event_sync_install.log file. On UNIX systems, this log file is always created in the /tmpdirectory. For Windows systems, this file is created in the directory defined by the %TEMP% environment variable. To determine where this directory is defined for the current command-line window, run:

If you specified the monitoring servers in the silent installation configuration file, you might consider deleting that file after installation, for security reasons. The passwords specified in the files are not encrypted.

If you want to define additional monitoring servers (in addition to the one required monitoring server), run the sitconfuser.sh command. Repeat this command for each monitoring server.

If you specified your monitoring servers after the installation, stop and restart the Situation Update Forwarder process manually.


Parent topic:

Installation and configuration

+

Search Tips   |   Advanced Search