Tool Mentor: TEC - Close Event
TM094 - How to Use IBM Tivoli Enterprise Console to Close Event
Tool: IBM Tivoli Enterprise Console
Relationships
Main Description

Context

Tool mentors explain how a tool can perform tasks, which are part of ITUP processes and activities. The tasks are listed as Related Elements in the Relationships section.

You can see the details of how processes and activities are supported by this tool mentor, by clicking the links next to the icons:

Details

An event console provides a GUI that operators can use to view and respond to events. The IBM® Tivoli® Enterprise Console® product provides two versions of the event console, a Java™ version and a Web version. Administrators must use the Java version to perform configuration tasks. Administrators or operators must use the Java version to start Tivoli NetView® functions and to run local automated tasks. Administrators and operators can use the Java version or the Web version, or both, to manage events stored in the Tivoli Enterprise Console database.

Typically the Tivoli Enterprise Console is linked to an incident management system such that there is a one or two-way directional link between Tivoli Enterprise Console events and trouble tickets in the incident management solution. Customers who do this integration usually will have the close action (or sometimes the open action) of the trouble-ticket automatically close the Tivoli Enterprise Console event. If there is no integration, the console administrator will have to manually close the trouble ticket and the Tivoli Enterprise Console event. The Tivoli Enterprise Console GUI (Web or Java) can be used to close Tivoli Enterprise Console events.

The console operators will select the event in their view and acknowledge and (or simply choose to) close the event. The event is changed in the Tivoli Enterprise Console database with an update by the administrator who closed the event (and acknowledged it) and a change in status to closed.

In some cases it is useful to have rules that automatically close events based on certain conditions. For example, to keep control of the number of events on the console, a rule can be written to close a low severity warning event after 24-48 hours if an operator has not responded and another event has not been received for that condition. As another case, an event might trigger a rule within the Tivoli Enterprise Console server that invokes an automated corrective action. When the service is recovered, a clearing event can be sent to the Tivoli Enterprise Console server to initiate the close of the original event. A clearing event is a duplicate of the original event in a closed state that closes the original event.

For More Information

For more information about this tool, click on the link for this tool at the top of this page.