Published 30 October 2002, last updated November-11-2002, Rating:
(based on 1 review)|
Softpanorama |
May the source be with you, but remember the KISS principle ;-)
|
While some technical solutions used in TEC were brilliant at the time when it was written, you will never discover this from the documentation. TEC Guides are written in "Greenspan-speak" (complex sentences with huge mass terms mostly devoid of any useful meaning that was a hall mark of former Fed chairman; the secret of his success is his ability to match content-free arcane jargon of the alchemist to the gullibility of the customers)
Despite large number of pages TEC guides contain very little useful information (the joke "the next 300 pages were intentionally left blank" has more subtle meaning them it looks if we are talking about TEC documentation ;-). Moreover if relevant information exists finding it is extremely difficult as those guides are not well referenced by Google. The following documents are available in the IBM TEC Documentation Page (see also Information Centers page)
In addition there are a dozen of Redbooks of various quality. Most are dated and information, as valuable as it is, is far from being current. Among the most useful are
This IBM Redbook presents a deep and broad understanding about event management with a focus on best practices. It examines event filtering, duplicate detection, correlation, notification, escalation, and synchronization. Plus it discusses trouble-ticket integration, maintenance modes, and automation in regard to event management. Throughout this book, you learn to apply and use these concepts with IBM Tivoli Enterprise Console 3.9.
Tivoli Enterprise Console can be rightly called the flagship of the Tivoli product line because it is the focal point of events from all Tivoli products. The new version of TEC will bring very important usability and performance enhancements such as Java-based TEC Console and Availability Intermediate Manager (AIM). This redbook introduces the new Tivoli Enterprise Console V3.7, covering the installation, tailoring, and configuration of the console itself
2003-10-24 This IBM Redbook is an update of the existing Tivoli Enterprise Internals and Problem Determination, SG24-2034 redbook. The material is revised and updated for Tivoli Management Framework and applications post Version 3.6. Some of the applications that are covered from the troubleshooting point of view in this redbook are: Tivoli Management Framework and related concepts Tivoli Enterprise Console IBM Tivoli Monitoring Tivoli Business Systems Manager Tivoli Enterprise Data Warehouse Tivoli Workload Schedule
(based on 1 review)This redbook is an update of a previous redbook called Introduction to Tivoli’s TME 10, SG24-4948, which remains one of the most widely-read Tivoli Redbooks having sold over 5,000 hardcopies in its life. This update reflects what has changed in Tivoli Management Software since Version 3.2 and covers the Tivoli Framework and the core applications of Version 3.6.1 (Tivoli Inventory, Tivoli Software Distribution, Tivoli Distributed Monitoring, Tivoli Enterprise Console, Tivoli User Administration, and Tivoli Security Management). This book also covers the full suite of Tivoli Enterprise products including Tivoli NetView, Tivoli NetView Performance Monitor, Tivoli Performance Reporter, Tivoli Remote Control, Tivoli Workload Scheduler, Tivoli Output Manager, Tivoli Service Desk, Tivoli Storage Manager, Tivoli Global Sign-On, some Tivoli Plus modules, and Tivoli Global Enterprise Manager (GEM).
Because Tivoli Enterprise products fit in the category of Enterprise Systems Management (ESM), in the first part of this book, we explain why ESM is essential and what it means. Then, we describe how Tivoli provides an enterprise approach to the ESM issues briefly describing all the products included in the Tivoli Enterprise suite of products.
... ... ...
This book is divided into eight parts: Introduction, Tivoli Management Framework, Deployment discipline, Availability discipline, Operations discipline, Security discipline, Tivoli modules, and Tivoli management views. The first part contains the introductory chapters on ESM and Tivoli Enterprise Software. The other parts reflect the architecture of Tivoli Enterprise Software.
Each chapter covers a product. The products that belong to the core applications contain practical hands-on examples to familiarize readers with the way the basic functions work and to deepen their understanding of the concepts. These chapters also contain tests that can help prepare technical support personnel for Tivoli certification programs.
The purpose of this field guide is to describe the functionality of the IBM Tivoli Enterprise Console state correlation engine introduced in ITEC version 3.8. It also outlines the configuration and design aspects as well as gives hints for installing and troubleshooting. Some case studies from different customers are discussed at the end.
The purpose of this white paper is to educate the concerned audience about all the different stages and paths that an event can undergo on its way to the IBM Tivoli Enterprise Console Event Server (referred to as “Event Server” from here on out). Also, this document will be of great help to someone who is trying to diagnose a problem of events not being received. The flowcharts included that show the event flow will definitely help pinpoint specific areas to analyze further.
10.2.1 Using the wizard to create a custom script Resource Model
First, you need to write a custom script on the monitored system. We create a sample script for ITSO_ProcessNum Resource Model, as shown in Example 10-1. The custom script Resource Model checks the standard output from your custom script. Therefore, the custom script must print its result to standard output.
Example 10-1 process_num.ksh
#!/bin/kshPROCESS_NAME=$1ps -A -o "args" | grep -v grep |grep -v $0 | grep "$PROCESS_NAME" | wc -l
Note: The custom script runs on the shell environment with variables defined by the lcfd_env.sh, such as LCFROOT, LCF_TEMPDIR, and so on. Instead of writing the special file name or directory name in the script, you may want to use these variables to make your custom script widely usable.
After you finish writing the script, make sure it works in a stand-alone environment, and then copy the script to your PC where you will use the Workbench.
Example 10-2 Running process_num.sh
root@pacs007[/work/itso] process_num.ksh httpd 7
Note: If you select FTP to copy a script from the UNIX machine to the Windows PC where you use Workbench, use the binary mode to keep the original new line code of a script. If you changed the script on your PC, the new line code will be changed to the CR/LF, which is used in the Windows environment. If this happens, you can convert the new line code from the CR/LF to the LF. The bash and tr commands are included in the bin directory of the Workbench. Do the following:
bash tr -d "\015" < input_filename > output_filename cp output_filename input_filename
2. Using the wizard Now you have a custom script in your PC. You can import it into your Resource Model by using the Workbench wizard.
Let us begin by clicking on the New icon in the left side of the Workbench toolbar, as shown in Figure 10-4
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 05, 2008