Chapter 5. Integrating event management systems 311
5.1.1 Installing Event Synchronization on event server
The installer for the Event Synchronization component is located in the /tec
directory of the IBM Tivoli Monitoring V6.2.0 Tools DVD.
There are three methods for installing the component:
򐂰 Installing from a wizard
򐂰 Installing from the command line
򐂰 Installing from the command line using a silent install
In our test example, we used the Installation wizard as follows:
1. Log on to the host of the event server in an X Window System session, and
launch the Event Synchronization installer from the IBM Tivoli Monitoring
V6.2.0 Tools DVD media.
2. Change to the \tec subdirectory of the IBM Tivoli Monitoring V6.2.0 Tools DVD
and run the following command:
ESync2000Aix.bin
3. Click Next on the Welcome window.
4. Select I accept the terms in the license agreement and click Next.
312 Deployment Guide Series: IBM Tivoli Monitoring V6.2
5. Complete the fields in Figure 5-2and click Next.
Figure 5-2 Tivoli Event Synchronization installation
Use Table 5-1 as a reference.
Table 5-1 The IBM Tivoli Enterprise Console Event Synchronization configuration fields
Field Description
Name of configuration file The name of the file where the Event
Synchronization configuration information is
stored. The default name is situpdate.conf.
Number of seconds to sleep when no
new situation updates
The polling interval in seconds. The minimum
value is 1, while the default value is 3. If there
are no situation events, the Situation Update
Forwarder rests for three seconds.
Number of bytes to use to save last
event.
Number of bytes that the long running process
will use when it saves the location of the last
event it processes. This value must be an
integer. The minimum (and default) is 50.
Chapter 5. Integrating event management systems 313
6. Complete the information about the files where events will be written
(Figure 5-3) and click Next.
Figure 5-3 Tivoli Event Synchronization installation
URL of the CMS SOAP Server The URL for the SOAP Server configured on
the computer where the monitoring server is
running. The default value is cms/soap. This
value is used to create the URL to which IBM
Tivoli Enterprise Console sends event
information. For example,
http://hostname:port///cms/soap, where
hostname is the host name of the monitoring
server and port is the port.
Rate for sending SOAP requests to
CMS from Tivoli Enterprise Console
via Web Services
The maximum number of event updates sent
to the monitoring server at one time. The
minimum (and default) value is 10 events.
Level of debug detail for log The level of information for Event
Synchronization that will be logged. You have
the following choices:
򐂰 Low (default)
򐂰 Medium
򐂰 Verbose
Field Description
314 Deployment Guide Series: IBM Tivoli Monitoring V6.2
Use Table 5-2 as a reference.
Table 5-2 The IBM Tivoli Enterprise Console Event Synchronization configuration fields
7. Use the information from Figure 5-4 on page 315 for each monitoring server
with which you want to synchronize events and click Add. You must specify
information for at least one monitoring server.
Field Description
Maximum size of any single cache
file, in bytes
The maximum permitted size, in bytes, for any
one event cache file. 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 The maximum number of event caches files at
any given time. 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 reside The location where event cache files are
located. The default locations are as follows:
򐂰 On Windows:
C:\tmp\TME\TEC\OM_TEC\persistence
򐂰 On UNIX:
/var/TME/TEC/OM_TEC/persistence
Chapter 5. Integrating event management systems 315
Figure 5-4 Tivoli Monitoring Server Information
Use Table 5-3 as a reference.
Table 5-3 Tivoli Monitoring Server Information
8. When you have provided information about all of the monitoring servers, click
Next.
Field Description
Host name The fully qualified host name for the computer where the
monitoring server is running. This should match the
information that will be in events coming from this
monitoring server.
User ID The user ID to access the computer where the monitoring
server is running.
Password The password to access the computer.
Confirmation The password again.

Get Deployment Guide Series: IBM Tivoli Monitoring V6.2 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.