|
Softpanorama |
May the source be with you, but remember the KISS principle ;-)
|
| News | See also | Recommended Links | Selected Docs | Event Groups |
| Humor | Etc |
Note: This write-up is based in IBM Tivoli Enterprise Console User's Guide/ Event console
An event console is Java application that can be viewed in any Web browser (as applet) or used as an installable desktop application. In the latter case you need to install it on the desktop.
Those two versions are incorrectly called a Java version and a Web version, but they both are Java-based. Only installable version (Java version) permits to perform configuration tasks. Administrators or operators must also use the Java version to start Tivoli NetView functions and to run local automated tasks. Either Java version or the Web version can be used to manage events.
Even console is very primitive and provides for only very basic viewing and responding to events. It is so unsophisticated that lacks even basic capabilities typical for mail viewers. For example capability of copying event into buffer to paste it into some opther application is absent. you can copy it only slot by slot. In short it sucks.
A couple of more or less advanced features provided are views ( Event Groups) and response scripts.
An event console displays a window for monitoring event groups, which operators can use to monitor and respond to incoming events. An event group is a set of events that meet certain filter criteria. An administrator defines the event groups and assigns them to event consoles for each operator. Operators can have independent or shared views of events. The UI server prevents multiple event consoles from updating the same event and updates event status on all event consoles. Therefore, only one operator responds to and works on solving a problem. For more information about the UI server, see User interface server.
For more information about event consoles, see Managing events.
An event group is a configured logical area of responsibility that is used to notify users that an event matching a specified set of criteria has occurred. An administrator configures event groups using the Java version of the event console.
For example, if your network contains a group of computers that are used for critical work, you might want to create an event group that receives events for these critical computers. This logical grouping of events is an event group.
For more information about event groups and attributes, see Managing events.
To define an event group, you must specify the selection criteria for the events in the group. This data constitutes an event group filter. An event group filter can include any event attribute except for extended or customer-defined attributes. The following table lists some of the more commonly used attributes for event group filtering.
You can use SQL wildcard characters for any of the attributes to simplify event group filtering options. Entering specific values for each attribute narrows the types of events reported in an event group. Using wildcard characters expands the types and number of events reported in an event group.
Event group filters enable you to include specific, and possibly very different, events in an event group. Event group filters also help reduce the number of event groups that an operator must manage. For example, an administrator can create an event group composed of three filters to monitor the events on hosts 9.27.136.1, 9.27.136.2, and 9.27.136.4, but not 9.27.136.3. Without using event group filters, you would need three event groups to manage events from these hosts.
The Tivoli Enterprise Console product requires both Tivoli authorization roles and Tivoli Enterprise Console event group roles. Tivoli authorization roles are roles defined for the tasks that Tivoli Enterprise Console administrators and operators perform in a Tivoli management environment and are set in the Tivoli Management Framework product. For information about assigning Tivoli authorization roles, refer to the Tivoli Management Framework User's Guide.
Tivoli Enterprise Console event group roles are the roles defined for managing events in an event console. For information about event group roles, see Planning for event group roles.
The following table lists the Tivoli authorization roles required for the Tivoli Enterprise Console product.
| Activity | Context | Tivoli Authorization Role |
|---|---|---|
| Assigning administrative roles for the event server | Event server | senior |
| Configuring | super | |
| Starting and stopping | senior | |
| Assigning an operator to an event console | Event console | senior |
| Configuring your own event viewer preferences | user | |
| Assigning event group roles | Event groups | senior |
| Creating, modifying, or deleting event groups | senior | |
| Assigning event groups | senior | |
| Deleting events | Events | senior |
| Acknowledging and closing events | admin, RIM_view, and RIM_update | |
| Viewing events | user and RIM_view | |
| Sending events | user, if using the wpostemsg command, otherwise none | |
| Creating, modifying, or loading rule bases | Rule base | senior |
| Installing the Tivoli Enterprise Console product | Tivoli region | super |
|
Notes:
|
||
To start the event console from the command line in a bash shell, follow these steps:
tec_console.cmd
tec_console
The TEC dialog is displayed.
host_computer_name:port_number
The environment variable DISPLAY is of
particular importance in X windows because it tells the computer on which
machine the graphics is to be displayed. You should look at the current setting
of DISPLAY while you are logged in:
echo $DISPLAY
:0.0
This means that your machine is displaying on its own screen. The command will respond with the address of the machine on which da is displaying the graphics, in this case localhost. The string 0.0 identifies a server number and an optional screen number. In all cases of interest, both of these are zero.
If you have problems the first thing to do is to see the value of the variable $DISPLAY. If it is not set at all or is radically different try to reset it using:
export DISPLAY=:0.0
There are just two main reasons why you cannot display on an X
server:
1) Cannot resolve hostname (or some other network related issue)
2) no connect permission to the server (server corresponds to the machine were you
export display).
To resolve try to use "xhost +"
as a TEST mode, set DISPLAY and
try again.
NOTE: xhost + allows anyone to connect to
this Xserver, and
is not recommended for security reasons...notice I said "TEST mode ".
You can run a user-defined local command on selected events by running a user-defined script. The attributes of the event are passed to the script as environment variables. The name of the attribute environment variables can be referenced by using the non-formatted attribute name. The full list of non-formatted attribute names is contained in the SLOTS environment variable, which is passed to the script.
To run a local command, follow these steps:
You can start a Tivoli NetView console from the event viewer in the context of an event and drill down with Tivoli NetView tools to troubleshoot a network problem. You can open the Tivoli NetView Submap Explorer, Object Properties, or Diagnosis windows to view information about a problem node and take action if necessary.
To successfully use Tivoli NetView functions from the event viewer, certain prerequisite Tivoli NetView software must be installed and configured. For more information, refer to the IBM Tivoli Enterprise Console Installation Guide.
To run Tivoli NetView functions, select NetView from the Selected menu in the event viewer. For information about using the Tivoli NetView functions, refer to the online help in the event console. For information about using the Tivoli NetView network management console, refer to the Tivoli NetView documentation at the following Web site:
http://www.ibm.com/software/tivoli/library/
This section describes the following topics related to customizing the event viewer:
The preferences control how events are shown in the event viewer. To change the general preferences, from the Edit menu in the event viewer, click Preferences. You can change one or more of the following general preferences:
For more information about changing general preferences, refer to the online help.
The following table lists the context and authorization role required to perform this task.
| Activity | Context | Required Role |
|---|---|---|
| Change general preferences | Java version of the event console | user |
Because the general user preferences, the name of the last managed node you logged in to, and your user ID are stored locally in the $HOME/.tmeconsole directory, your preferences are maintained between sessions. Similarly, the preferences you set are used when you log on to the Java version of the event console on another computer.
You can change the severity colors only if your administrator has made this option available to you. Each event is color-coded to indicate the severity level for that event. The following table lists each default severity level and the corresponding default color.
| Severity | Color |
|---|---|
| FATAL | Black |
| CRITICAL | Red |
| MINOR | Orange |
| WARNING | Yellow |
| HARMLESS | Green |
| UNKNOWN | Blue |
To change the severity colors, follow these steps:
The following table lists the context and authorization role required to perform this task.
| Activity | Context | Required Role |
|---|---|---|
| Change severity colors | Java version of the event console | user |
You can sort all events or only events in the Working Queue based on any event field in the event viewer. Initially events are sorted based on event severity. If multiple events have the same severity, the events are sorted based on the event date. Events with the highest severity are displayed at the bottom, and events with the lowest severity are displayed at the top.
To sort events, follow these steps:
The following table lists the context and authorization role required to perform this task.
| Activity | Context | Required Role |
|---|---|---|
| Sort events | Java version of the event console | user |
You can filter the events in the Working Queue based on severity, status, and operator ownership to help you focus on important events. When you filter events for one event group, other event groups are not affected. To filter events, follow these steps:
The following table lists the context and authorization role required to perform this task.
| Activity | Context | Required Role |
|---|---|---|
| Filter events by severity and status | Java version of the event console | user |
For information about using a command to list events based on severity and status to standard output, refer to the wlsemsg command in the IBM Tivoli Enterprise Console Command and Task Reference.
To run a task, choose one of these methods:
The task wizard guides you through the steps required to run the task. For more information about running a task, refer to the online help in the event console.
The task results are shown in a new window of your Web browser. Use the print option of your Web browser controls to print the task results.
You can also run most tasks from the command line using the wruntask command. For more information about the wruntask command, refer to the Tivoli Management Framework Reference Manual.
For information about tasks in the T/EC Tasks library, refer to the Tivoli Enterprise Console Reference.
This section describes the following topics related to customizing the event viewer:
The preferences control how events are shown in the event viewer. The changes you make, except for changes to the maximum number of events to show in the each event viewer, are reflected immediately in all open event viewers.
Because changes to the preferences are stored in cookies, ensure that the privacy settings for your Web browser are set to allow cookies if you want the changes to be persistent. If cookies are not allowed, changes to the preferences affect only the current session. The preferences you set do not affect a Web console on a different computer.
To change the preferences, click Change User Preferences in the portfolio. You can change one or more of the following user preferences:
Changes to the maximum number of events to show in each event viewer are reflected the next you time open an event viewer.
The event console uses color and icons to indicate the severity level for an event. The following table describes the color and icon that corresponds to each event severity.
| Severity | Color | Icon |
|---|---|---|
| Fatal | Black |
![]() |
| Critical | Red |
![]() |
| Minor | Orange |
![]() |
| Warning | Yellow |
![]() |
| Harmless | Green |
![]() |
| Unknown | Blue |
![]() |
By default, events are sorted in the event viewer by the date received field. You can sort events based on up to three event fields. To do this, click the Edit Sort icon on the tool bar in the event viewer.
You can filter events in the event viewer by event severity, event status, and event owner. Filtering events in this manner helps you focus on the events of interest. To filter events, use the event filter icons on the tool bar in the event viewer.
If your environment includes the Tivoli Enterprise Console product, you can add the Tivoli Enterprise Console event viewer to any workspace in the Tivoli Enterprise Portal to provide an integrated view of events.
For comprehensive event management, you can also configure one or more monitoring servers to forward situation events to the event server, and install the event synchronization component on the event server so that operator actions and updates based on Tivoli Enterprise Console rules are sent back to the monitoring server. The updated status of the events is reflected in both the situation event views and in the Tivoli Enterprise Console event viewer.
Here is a picture of the Tivoli Enterprise Console event viewer with Tivoli Enterprise Console events and situation events that were forwarded from the monitoring server. The columns in this view correspond to the base attributes of Tivoli Enterprise Console events and those of situation events.
With event synchronization configured, you can add the Tivoli Enterprise Console event viewer to a workspace and perform the same operator tasks, such as acknowledging an event and closing an event, as you can in the event console of the Tivoli Enterprise Console product. However, you must use the Java version of the event console in the Tivoli Enterprise Console product to perform configuration tasks, such as creating an event group or creating an event group filter. Also, you can run IBM Tivoli Monitoring actions on an event in the situation event views, and you can only run Tivoli Enterprise Console tasks on an event in the Tivoli Enterprise Console event viewer.
See the IBM Tivoli Monitoring Installation and Setup Guide to install and configure event synchronization.
See the IBM Tivoli Monitoring Administrator's Guide to define the characteristics and behavior of events and situation events sent to the Tivoli Enterprise Console.
AbstractThis Tivoli Support Technical Exchange web seminar will cover how to set up the Tivoli Enterprise Console (TEC) Java Console Information button
Presented by:
Ted Douglas, Staff Software Engineer
Date:
August 21, 2007Content This is the ppt presentation that will displayed on the webconference. Approximately 24 hours after the event a .avi recording will be available at the location below:
To access this recording the password
tiv0li must be used.
https://asp22.centra.com:443/GP/main/000000acbd3a000001140b21e9367f0c
If you are unable to access email ricks3@us.ibm.com for assistance.
Recommended Links
In case of broken links please try to use Google search. If you find the page please notify us about new location
IBM Tivoli Enterprise Console User's Guide/ Event console
ORB Data information (free registration required):
- How do I create a TEC User for use with TEC Console 3.7.x? (Found in Technical Documents)
How do I create a TEC User for use with TEC Console 3.7.x?
/index.php?pageId=261- How do I create an Event Console for TEC Console 3.7.x? (Found in Technical Documents)
How do I create an Event Console for TEC Console 3.7.x?
/index.php?pageId=262- How to remove the complete "Source Group" Display from TEC Console (Found in Technical Documents)
How to remove the complete "Source Group" Display from TEC Console
/index.php?pageId=268- Creating TEC Consoles in non-TEC TMRs (Found in Technical Documents)
Creating TEC Consoles in non-TEC TMRs
/index.php?pageId=317- Event Sensitive Help from the TEC Console (Found in Technical Documents)
Describes how you can how you can add event sensitive help to the Event Console, by launching a Web Browser containing help information for that event
/index.php?pageId=356- Altering the Width and Name of TEC Console Fields (Found in Technical Documents)
Describes how you can change the width and names of the various columns within an EventConsole.
/index.php?pageId=373- Changing TEC Console Display Properties (Found in Technical Documents)
Provides a method and script for changing the display properties of a TEC Console from the CLI. This will allow you to preconfigure consoles for Administrators during implementation phase of your projects.
/index.php?pageId=395
Copyright © 1996-2008 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. Submit comments This document is an industrial compilation designed and created exclusively for educational use and is placed under the copyright of the Open Content License(OPL). Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
Standard disclaimer: The statements, views and opinions presented on this web page are those of the author and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: June 02, 2008