The installer for the event synchronization component is
located in the /tec directory of the IBM® Tivoli® Monitoring
Tools DVD.
There are three methods for installing the component:
When you install the event synchronization component
on your event server, the following changes are made:
- If you select to use an existing rule base, the
event synchronization .baroc class files (omegamon.baroc and Sentry.baroc
[if not present]) and the omegamon.rls rule set file are imported
into your existing rule base. If you do not want to modify your existing
rule base during the installation, you can choose to manually perform
rule base modifications after installation is complete. See Manually importing the event synchronization class files and rule set for more information.
- For all rule bases that have Sentry.baroc imported,
the Sentry2_0_Base class is updated to define additional integration
attributes for the situation events received from IBM Tivoli Monitoring.
- A new process, Situation Update Forwarder, is installed along
with its supporting binary and configuration files. This process is
used to forward updates to the situation events back to the monitoring
server. On Windows, a Tivoli Situation Update Forwarder
service is also created.
Note: - If your IBM Tivoli Enterprise Console® event
server is running on Windows 2003
and you are planning to install the event synchronization remotely
(using a program such as Terminal Services to connect to that Windows 2003 computer), you need
to run the change user /install command before you run the
installation. This puts the computer into the required "install" mode.
After the installation, run the change user /execute command
to return the computer to its previous mode.
- If you have a monitoring server on an operating
system like UNIX or Linux, you must configure your TCP/IP network
services in the /etc/hosts file to return the fully
qualified host name. See for more information.
- For a Windows event
server, any existing rule base that you use must indicate a relative
drive letter (such as C:\) as part of its associated path. To verify
that your existing rule base contains a relative drive letter, run
the following command from a bash environment on your event server:
wrb -lsrb -path
If
the returned path includes something like hostname:\rulebase_directory,
with no drive letter (such as C:\), copy the ESync3000Win32.exe file
from the \TEC subdirectory of the IBM Tivoli Monitoring installation
image to the drive where the rule base exists and run the installation
from that file.
- If you are using a Windows event
server, if you have any rule base with an associated path that does
not contain a relative drive letter and that has the Sentry2_0_Base
class imported, copy the ESync3000Win32.exe file from the
\TEC subdirectory of the IBM Tivoli Monitoring installation
image to the drive where the rule base exists and run the installation
from that file.
To verify if you have any rule bases that have
an associated path containing no relative drive letter, run the wrb
-lsrb -path command as described in the previous note.
To
determine if your rule bases have the Sentry2_0_Base class imported,
run the following command against all of your rule bases:
wrb -lsrbclass rule_base
where
rule_base is
the name of the rule base.