IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Prepare for installation > Specific information to have ready
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Information to gather for event forwarding
You need the following additional information to successfully install and configure event forwarding and synchronization between a hub Tivoli Enterprise Monitoring Server and either Netcool/OMNIbus or IBM Tivoli Enterprise Console.
- Host names, user IDs, and passwords for the monitoring servers that you want to receive events from.
- The amount of free space in your temporary directory on the server where Netcool/OMNIbus ObjectServer or Tivoli Enterprise Console are installed. The event synchronization component installation requires 200 MB of temporary space.
- Simple Object Access Protocol (SOAP or Web Services) information to send events to a monitoring server (the URL, the rate to send requests to the server).
By default, all Hub monitoring servers are configured as SOAP servers. If you did not change the SOAP configuration to make it unique for your environment, you can accept the default values during the installation.
If you did change this configuration, use the SOAP information unique to your configuration.
- For Netcool/OMNIbus, the host of the EIF probe and the port on which it is listening. For TEC, the host of the event server or servers to which events are being forwarded and the port on which it is listening.
- For TEC, event rule base information (either the name of a new rule base to create or the name of an existing rule base to use)
- 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 from a bash environment on your event server:
wrb -lsrb -pathIf 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 against all of your rule bases:
wrb -lsrbclass rule_basewhere rule_base is the name of the rule base.
Parent topic:
Specific information to have ready