Chapter 4. Installation 71
Figure 4-1 Installing OMEGAMON Tivoli Enterprise Console Adapter
2. Click OK. This opens Tivoli Enterprise Console Server: Location and Port
Number window. Here, you need to provide the IBM Tivoli Enterprise Console
server host name and port number, where events will be forwarded.
4.5.2 Installing Tivoli Enterprise Console Event Synchronization
The Tivoli Enterprise Console Event Synchronization component must be
installed on the IBM Tivoli Enterprise Console server. There are three methods
for installing the event synchronization:
From a wizard
From the command line
From the command line using a silent install
Note: The event forwarding uses the non-Tivoli-based transport mechanism.
72 Certification Guide Series: IBM Tivoli Monitoring V6.1
Installing from a wizard
Use the following steps to install event synchronization from the installation
1. On the event server, launch the event synchronization installation:
– On Windows, double-click the setupwin32.exe file in the \TEC
subdirectory on the IBM Tivoli Monitoring installation media.
– On Linux or UNIX, change to the /<os_type>/tec subdirectory of the IBM
Tivoli Monitoring installation media, and run the following command:
Where <operating_system> is the operating system on which you are
2. Click Next in the Welcome window.
3. Select I accept the terms in the license agreement and click Next.
4. Complete the fields in Table 4-3 and click Next.
Table 4-3 Tivoli Enterprise Console event synchronization configuration fields
5. Complete the information shown in Table 4-4 on page 73 about the files
where events will be written and click Next.
Name of configuration file The name of the file where event synchronization
configuration information is stored. The default name is
Number of seconds to sleep when no new
The polling interval, in 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.
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
Tivoli Enterprise Console sends event information.
Rate for sending SOAP requests to CMS
from TEC via web services
Rate for sending SOAP requests to CMS from Tivoli
Enterprise Console through Web services.
Level of debug detail for log The level of information for event synchronization that will be
Chapter 4. Installation 73
Table 4-4 Tivoli Enterprise Console event synchronization configuration fields
6. Enter the following information for each monitoring server to synchronize
events and click Add. You must specify information for at least one monitoring
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
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.
7. After providing information about all the monitoring servers, click Next.
8. Specify the rule base to use to synchronize events. You have two choices:
– Create a new rulebase
– Use existing rulebase
9. If you are using an existing rule base, enter the name of the rule base.
10.If you want to import an existing rule base into a new rule base, enter the
name of the existing rule base in the Existing rulebase to import field.
12.Click Next on the preinstallation summary window.
13.When the installation and configuration steps are finished, a message telling
to stop and restart the event server is displayed. Click OK.
14.Click Finish in the Summary Information window.
Maximum size of any single cache file, in
The maximum permitted size, in bytes, for any one event
cache file. The minimum (and default) value is 50000.
Maximum number of caches files The maximum number of event caches files at any given
time. The minimum value is 2, and 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 of event cache files.
Note: This step is only available if you are creating a new rule base.