Deployment Guide Series: IBM Tivoli Monitoring V6.2

338 Deployment Guide Series: IBM Tivoli Monitoring V6.2

5.5 Integrating the Netcool and OMNIbus events to the

Common Event Console example

This section describes an example of IBM Tivoli Monitoring V6.2 event

integration.

First, we configure the Common Event Console to concentrate events from IBM

Tivoli Monitoring itself, Tivoli Enterprise Console, and Netcool/OMNIbus in the

same workspace. To achieve this target, some customization has been made.

TEMS has a default ITM connector configuration, as you can see in Figure 5-7.

Figure 5-7 ITM Connector configuration

Chapter 5. Integrating event management systems 339

To configure TEC Connector, select the respective folder, click New, and

complete the parameters, as shown in Figure 5-8.

Figure 5-8 Tec Connector Tab

340 Deployment Guide Series: IBM Tivoli Monitoring V6.2

To configure the OMNIbus Connector, select the respective folder, click New, and

complete the parameters, as shown in Figure 5-9.

Figure 5-9 OMNIbus connector tab

In Figure 5-10 on page 341, there is a sample of the Common Enterprise

Console with three connectors: ITM, TEC, and Netcool/OMNIbus.

Note: The other parameters that are not shown above were left with the

default values.

Chapter 5. Integrating event management systems 341

Figure 5-10 Common Event Console

For example, one situation was created to reconfigure disk space when Space

Available Percent was less than 90. Figure 5-11 shows the basic configuration.

Figure 5-11 Situation configuration

342 Deployment Guide Series: IBM Tivoli Monitoring V6.2

In the situation configuration, click the EIF folder to select the EIF Receiver for

the situation alert, as shown in Figure 5-12.

Figure 5-12 EIF receivers

This example of a situation was used to generate an event to Netcool/OMNIbus.

An alert where Alert Group has the value of ITM_Linux_Disk was received by

Netcool/OMNIbus. Figure 5-13 shows the native Netcool/OMNIbus console.

Figure 5-13 Netcool/OMNIbus event list

The user can acknowledge the event on the TEP workspace, as shown in

Figure 5-14 on page 343.